use CallContext in MetaStoreManagerFactory.createMetaStoreManager #2833
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
XN137
force-pushed
the
use-CallContext-in-MetaStoreManagerFactory.createMetaStoreManager
branch
from
6fd87b7 to
9c749ca
Compare
XN137
force-pushed
the
use-CallContext-in-MetaStoreManagerFactory.createMetaStoreManager
branch
from
9c749ca to
aaf80d5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
1st commit is basically a squash of
https://github.com/apache/polaris/pull/2555the 2nd commit shows that we could still use
CallContextto pass "custom parameters" into the persistence layer at creation time of thePolarisMetaStoreManager(which is now "request-scoped")