Remove duplicate hits from SearchResult #956
Open
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
Signed-off-by: xil <[email protected]>
Signed-off-by: xil <[email protected]>
lucy66hw
force-pushed
the
duplicate_hits
branch
from
8369400 to
e54fff4
Compare
Changes AnalysisCommit SHA: 4839490 API ChangesSummarySUCCESS: No changes found between specifications ReportThe full API changes report is available at: https://github.com/opensearch-project/opensearch-api-specification/actions/runs/17805693592/artifacts/4037438909 API Coverage
|
Spec Test Coverage Analysis
|
lucy66hw
requested review from
Tokesh,
VachaShah,
Xtansia,
aabeshov,
dblock,
harshavamsi,
nhtruong and
sachetalva
as code owners
karenyrx
previously approved these changes
Sep 15, 2025
Signed-off-by: Harsha Vamsi Kalluri <[email protected]>
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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
HitsMetadata schema already includes the _source field in hit items
SearchResponseSections directly serializes SearchHits without modification
No additional properties are added at the response level