jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edouard Hue (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-2843) ConstraintSplitter.getSelectorNames doesn't support FullTextSearch constraints
Date Tue, 14 Dec 2010 09:23:01 GMT

     [ https://issues.apache.org/jira/browse/JCR-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Edouard Hue updated JCR-2843:
-----------------------------

        Fix Version/s: 2.2.1
    Affects Version/s:     (was: 2.3.0)
                           (was: 2.2.0)
                       2.2.1
               Status: Patch Available  (was: Open)

Adding FullTextSearch to the tested constraint types

> ConstraintSplitter.getSelectorNames doesn't support FullTextSearch constraints
> ------------------------------------------------------------------------------
>
>                 Key: JCR-2843
>                 URL: https://issues.apache.org/jira/browse/JCR-2843
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core, query
>    Affects Versions: 2.2.1
>         Environment: Jackrabbit 2.2-SNAPSHOT (built on Fri Dec 03 11:12:48 CET 2010)
> Jackrabbit 2.3-SNAPSHOT (build on Sat Dec 11 10:35:11 GMT+00:00 2010)
>            Reporter: Edouard Hue
>             Fix For: 2.2.1
>
>         Attachments: JCR-2843.patch
>
>
> 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)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message