[JCR-2843] ConstraintSplitter.getSelectorNames doesn't support FullTextSearch constraints

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2
• Fix Version/s: 2.2.1
• Component/s: jackrabbit-core, query
• Environment: Jackrabbit 2.2-SNAPSHOT (built on Fri Dec 03 11:12:48 CET 2010) - now on 2.2.0; Jackrabbit 2.3-SNAPSHOT (build on Sat Dec 11 10:35:11 GMT+00:00 2010)
• Assignee: Jukka Zitting
• Reporter: Edouard Hue
• Created: 12/Dec/10 22:38
• Updated: 23/Sep/11 14:24
• Resolved: 05/Jan/11 16:06

Description

The constraint type FullTextSearch is missing in the tested types in org.apache.jackrabbit.core.query.lucene.join.ConstraintSplitter.getSelectorNames(Constraint) method. Submitting a QOM query with a full-text constraint throws a javax.jcr.UnsupportedRepositoryOperationException, while the repository reports supporting such queries : session.getRepository().getDescriptorValue(Repository.QUERY_FULL_TEXT_SEARCH_SUPPORTED).getBoolean() returns TRUE.

Typical stack trace :

javax.jcr.UnsupportedRepositoryOperationException: Unknown constraint type: CONTAINS(r.[jcr:title], 'REGA -APA')
org.apache.jackrabbit.core.query.lucene.join.ConstraintSplitter.getSelectorNames(ConstraintSplitter.java:177)
org.apache.jackrabbit.core.query.lucene.join.ConstraintSplitter.getSelectorNames(ConstraintSplitter.java:195)
org.apache.jackrabbit.core.query.lucene.join.ConstraintSplitter.getSelectorNames(ConstraintSplitter.java:157)
org.apache.jackrabbit.core.query.lucene.join.ConstraintSplitter.split(ConstraintSplitter.java:106)
org.apache.jackrabbit.core.query.lucene.join.ConstraintSplitter.split(ConstraintSplitter.java:104)
org.apache.jackrabbit.core.query.lucene.join.ConstraintSplitter.<init>(ConstraintSplitter.java:80)
org.apache.jackrabbit.core.query.lucene.join.QueryEngine.execute(QueryEngine.java:162)
org.apache.jackrabbit.core.query.lucene.join.QueryEngine.execute(QueryEngine.java:147)
org.apache.jackrabbit.core.query.QueryObjectModelImpl.execute(QueryObjectModelImpl.java:114)