Implement searchattribute.MapperProvider #3873
Merged
Conversation
This file contains 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
rodrigozhou
force-pushed
the
refactor-search-attribute-mapper
branch
2 times, most recently
from
015bd09 to
7d14be1
Compare
alexshtin
approved these changes
Jan 31, 2023
rodrigozhou
force-pushed
the
refactor-search-attribute-mapper
branch
from
7d14be1 to
d302734
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changed?
Implement
searchattribute.MapperProviderand replace passing thesearchattribute.Mapperdirectly to services/objects.Why?
For advanced visibility with SQL, we need a standard mapper, and it will be provided by the
MapperProvider. It will also handle when the user sets their own mapper in the Server options.How did you test it?
Existing tests.
Potential risks
This PR should be no-op.
Is hotfix candidate?
No.