[JCR-1408] Invalid query results when using jcr:like with a case transform function and a pattern not starting with a wildcard

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4, core 1.4.1
• Fix Version/s: core 1.4.2
• Component/s: jackrabbit-core, query
• Environment: Ubuntu gutsy, Sun JDK 1.5.0_08
• Assignee: Unassigned
• Reporter: Sébastien Launay
• Created: 21/Feb/08 19:54
• Updated: 28/Mar/08 09:15
• Resolved: 22/Feb/08 10:17

Description

If the repository contains nodes with the following value for the property name :
john
JOhn
joe
Joey

and we run the following query :
//element(, document)/[jcr:like(fn:lower-case(@name), 'joh%')]")
then all the previous nodes will match especially the last 2 nodes.

The reason is the use of two range scans from the lucene term index:
..._name_jOH
..................
...name_joh

and

..._name_JOH
..................
...name_Joh

The first range will contains ..._name_joe property and the second will contains ..._name_Joey.
But the pattern 'joh%' and so the regexp '.*' because of the range scan will match
the substring values of the properties ('' in the first range and 'y' in the second range).

The solution is to use the full pattern (ie 'joh.*') for matching each properties.