[7.x.x] Correct the data problems with Fields in the Lucene Full Text Index #23
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.
Previously the PRs eXist-db/exist#4253 and eXist-db/exist#4541 introduced some serious problems with Fields in the Lucene Full Text Index. This PR fixes the following problems:
ft:query
when used on the Context Item within a predicate.xs:date
andxs:time
values into fields.xs:integer
andxs:decimal
values that exceed 32 bits.xs:integer
,xs:long
,xs:unsignedLong
,xs:int
,xs:unsignedInt
,xs:short
,xs:unsignedShort
,xs:decimal
,xs:double
,xs:float
,xs:date
,xs:time
,xs:dateTime
,xs:string
). This PR adds support for all of the 45 XDM 3.1 atomic types!Closes eXist-db/exist#5193