[OAK-4080] Fulltext queries: compatibility for "contains" with special characters

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: query
• Assignee: Thomas Mueller
• Reporter: Thomas Mueller
• Created: 01/Mar/16 13:39
• Updated: 09/Mar/18 14:38

Description

Currently, "jcr:contains" with special characters don't work the same when using a Lucene fulltext index compatVersion 2 compared to using compatVersion 1 or Jackrabbit 2.x.

This needs to be documented. Also, it might make sense to provide a compatibility flag, so that behavior is the same as with the old versions, at least as much as possible, even thought new features would not be supported.

The one example I know is using "*" as in:

SELECT * FROM [nt:base] AS c WHERE CONTAINS(c.[test], 'athxv:!*') 

With compatVersion 2, the "*" needs to be escape as follows, in order to match properties with exactly this text:

SELECT * FROM [nt:base] AS c WHERE CONTAINS(c.[test], 'athxv:!\*') 

Issue Links

• is related to: OAK-3769 QueryParse exception when fulltext search performed with term having '/'
• is related to: OAK-3879 Lucene index / compatVersion 2: search for 'abc!' does not work