What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Feature
What is the current behavior? (You can also link to an open issue here)
Currently structured and unstructured indexes don't support score modifiers stored in dict fields.
And all ints are converted to floats. We lose accuracy on large ints.
What is the new behavior (if this is a feature change)?
In this feature, we implement support for dict score modifiers stored as fields. The subfields are accessed in the search api through dot notation. We support map<text, int>, map<text, long>, map<text, float>, map<text, double>.
We also separately store int values in int8 data types, and long, float, and double are converted into double.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Have unit tests been run against this PR? (Has there also been any additional testing?)
Yes
Related Python client changes (link commit/PR here)
None
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...) Feature
What is the current behavior? (You can also link to an open issue here) Currently structured and unstructured indexes don't support score modifiers stored in dict fields. And all ints are converted to floats. We lose accuracy on large ints.
What is the new behavior (if this is a feature change)? In this feature, we implement support for dict score modifiers stored as fields. The subfields are accessed in the search api through dot notation. We support
map<text, int>,map<text, long>,map<text, float>,map<text, double>. We also separately store int values in int8 data types, and long, float, and double are converted into double.Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Have unit tests been run against this PR? (Has there also been any additional testing?) Yes
Related Python client changes (link commit/PR here) None
Related documentation changes (link commit/PR here) marqodocs previews/2.9
Other information:
Please check if the PR fulfills these requirements
[x] The commit message follows our guidelines
[x] Tests for the changes have been added (for bug fixes/features)
[x] Docs have been added / updated (for bug fixes / features)