[2.6] MOD-7944: Support multi-byte char terms (#5391) #5648
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.6.(cherry picked from commit 43701d8)
Changes:
Since Version 2.6 limits the normalization buffer to 128 bytes,
#define MAX_NORMALIZE_SIZE 128, expected results intestLongTerms()were modified to respect that limitation.For tests with indexes with LANGUAGE different from ENGLISH, the LANGUAGE was added to FT.SEARCH commands because this version does not take the language from index specification
Since dialect 4 is not available in this version, test are only done for dialects 1 - 3.
In test_cpp_llapi.cpp,
RediSearch_CreateTagLexRangeNode()receives only 5 arguments, in this versionconst char* fieldNameis not part of the function signaturecommon.py:
config_cmd()andrun_command_on_all_shards()ftDebugCmdName()bydebug_cmd()