Optimize query storage by storing source field as a string in local index #424
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
LilyCaroline17
requested review from
ansjcy,
jainankitk,
deshsidd and
dzane17
as code owners
|
Does this actually change the |
LilyCaroline17
force-pushed
the
optimizeExporterQueryStorage
branch
from
241dd3e to
85c9170
Compare
LilyCaroline17
force-pushed
the
optimizeExporterQueryStorage
branch
3 times, most recently
from
00fa3ca to
3a576e5
Compare
dzane17
reviewed
Sep 24, 2025
LilyCaroline17
force-pushed
the
optimizeExporterQueryStorage
branch
5 times, most recently
from
1c6e746 to
c736543
Compare
…ndex Signed-off-by: Emily Guo <35637792+LilyCaroline17@users.noreply.github.com>
LilyCaroline17
force-pushed
the
optimizeExporterQueryStorage
branch
from
c736543 to
d8d9eff
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.
Description
This PR addresses some bugs that we're having with how the source field is stored in the local index. The source field can be really long and/or really nested. The solution is to store the source field as a string within the local index so no exceptions related to field depth or number of fields is triggered.
Issues Resolved
Closes [https://github.com//issues/411]
Dashboards PR to handle source field change: opensearch-project/query-insights-dashboards#357
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.
Check that Local index properly created:
Scrolling down we can see that source is in properties in the local index.