fix(storage): fix inverted index term_id
may conflict between multiple fields
#16687
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.
I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/
Summary
We use the value corresponding to the
Term
obtained from theFST
as theterm_id
to uniquely identify aTerm
. However, since our search supports multiple fields, thisterm_id
may conflict between multiple fields, resulting in wrong results. This PR adds a newTermId
structure, including thefield_id
and theterm_ordinal
field, to uniquely identify aTerm
and avoid conflicts.Tests
Type of change
This change is