-
Type: Bug
-
Status: Resolved
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 8.10
-
Fix Version/s: 8.10
-
Component/s: Core MarkLogic
-
Tags:
-
Sprint:nxfit 9.1.1
-
Story Points:3
Due to changes on MarkLogic connector to use range element index when it is available for a property, the NOT EQ constraint didn't work anymore on array property.
This is due to the non propagation on NOT constraint on every items.
For example:
<array> <array__item xsi:type="xs:string">bob</array__item> <array__item xsi:type="xs:string">pete</array__item> </array>
This document will match the following NXQL SELECT * FROM Document where array <> 'bob'.
The produced MarkLogic query is currently (just past the array constraint part):
cts:element-query( fn:QName("", "array"), cts:element-range-query(fn:QName("", "array__item"), "!=", xs:string("bob")) )
But we expect to have for list:
cts:not-query( cts:element-query( fn:QName("", "array"), cts:element-range-query(fn:QName("", "array__item"), "=", xs:string("bob")) ) )
- is related to
-
NXP-19481 MarkLogic retrieve range element index
- Resolved