fix(mapi): add lucene index on user custom fields #7473
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
wbabyte
force-pushed
the
APIM-4771_custom_fields
branch
3 times, most recently
from
a9acaf4
to
2f4e067
Compare
wbabyte
force-pushed
the
APIM-4771_custom_fields
branch
from
2f4e067
to
ae82699
Compare
phiz71
approved these changes
May 20, 2024
wbabyte
force-pushed
the
APIM-4771_custom_fields
branch
from
ae82699
to
bf0b903
Compare
This was referenced May 21, 2024
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.
Issue
https://gravitee.atlassian.net/browse/APIM-4771
Description
add lucene index on user custom fields
Additional context