[2.10] MOD-7944: Support multi-byte char terms (#5391) #5646
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
Manual backport of #5391 to
2.10
.(cherry picked from commit 43701d8)
Since Version 2.10 limits the normalization buffer to 128 bytes,
#define MAX_NORMALIZE_SIZE 128
, expected results intestLongTerms()
were modified to respect that limitation.In
testMultibyteTag
, for tests using DIALECT 4, the number of results was changed to ANY, because in this version a wrong count is returned.In test_cpp_llapi.cpp,
RediSearch_CreateTagLexRangeNode()
receives only 5 arguments, in this versionconst char* fieldName
is not part of the function signature