Additional index fix for PM-21 #734
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
testflyjets
approved these changes
Aug 6, 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.
Additional testing and fix for PM-21
Ok, this one was annoying. In testing this in preparation for prod, I found that the prod index is different from dev, which is the root cause of the issues noted in JIRA. I had assumed they were the same. The prod index had different sort parameters and normalizers setup that dev didn’t have (along with slightly different fields).
Now, dev matches prod, so we can revert a change made to fix dev that wouldn't work in prod with the index differences.
https://topcoder.atlassian.net/browse/PM-21?focusedCommentId=83938