fix(index): encode string type to original data to enable fst regex to work #3324
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 GreptimeDB CLA
What's changed and what's your intention?
Previously, when encoding string keys into an FST using the memcomparable format, additional prefixes and suffixes beyond the original string data were added, which could lead to inaccuracies under certain regex query conditions. This PR specifically addresses the encoding of strings: encoding is now done directly based on the original data.
Additionally, unit tests related to
SstIndexCreator
have been added. These tests link together both the construction and querying of indexes, increasing confidence in their correctness.Checklist
Refer to a related PR or issue link (optional)