-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
Current scenario
Currently, for any CQL requests that are sent to Search platform, a default "order by entityId" clause is added. This is for keeping the performance high and make sure the results being returned consistent. Due to this, in rare cases like this customer, the order of results coming back is not as expected.
Suggested solution
Suggested solution is to not default to "order by entityId" in specific scenarios - for example when JSM calls CQL - don't default to using "order by entityId". This fix requires extensive testing.
Workarounds
At this moment, there are no workarounds.