Add a mongodb index on Catalog.updatedAt #4819
Merged
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
Merged
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.
Impact: minor
Type: performance
Issue
For search we will be querying the Catalog collection sorted by the
updatedAttimestamp field when syncing via kafka-connect. MongoDB requires an index on this field to efficiently process this query.Solution
Add the index via the mongo API.
Breaking changes
N/A
Notes
Index creation will run in the background, but does require some resources to do. Most installations won't notice this until it's already done, but if you had a very large catalog data set you may notice mongodb using resources to index the data for a brief period.
Testing
db.Catalog.getIndexes()