Details
-
Bug
-
Resolution: Fixed
-
Major
-
3.0.0-beta.4
-
None
Description
Doing a search query results in a response like:
String value: rest_index: Query, indexName: ftsIdx1, err: bleve: QueryBleve validating consistency, err: unsupported consistencyLevel: not_bounded
(Same issue if we add our own SearchOptions with ScanConsistency set to request_plus)
Note that the json that gets sent is the following:
{"ctl":{"timeout":75000,"consistency":{"level":"not_bounded"}},"query":{"match":"SampleSubvalue68","prefix_length":0,"fuzziness":0}}
Whereas other SDKs do not send consistency unless its via consistentWith for at_plus.
For example, an equivalent search query from Java SDK3 sends
{"match":"SampleValue83","query":{"match":"SampleValue83"}}
Also the only option provided by other SDKs is not_bounded, so the others should probably be removed?