[
https://issues.apache.org/jira/browse/JCR-1544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1544:
-------------------------------
Affects Version/s: (was: core 1.4.2)
Fix Version/s: (was: core 1.4.3)
I think the "a NOT b" query is converted to "a not b" on purpose _not_ to
trigger the Lucene NOT behaviour. The full text query syntax in jcr:contains()
is _not_ the Lucene query syntax.
Thus the lowercasing should probably be kept unless someone comes up with a
more elegant solution. Adding the \b boundaries seems like a good idea though.
> [PATCH] fix a NOT b queries
> -----------------------------
>
> Key: JCR-1544
> URL: https://issues.apache.org/jira/browse/JCR-1544
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-core
> Reporter: Dave Brosius
> Priority: Minor
> Attachments: fix_not_queries.patch
>
>
> the query a NOT b doesn't work. Problem was LuceneQueryBuilder was lower
> casing the NOT which causes the javacc code to fail.
> In addition, code just did a blind replaceAll on the string "NOT" and "AND",
> which is wrong for things like 'BAND'.
> Patch changes code to look for "\\band\\b" -> AND and "\\bnot\\b" -> NOT
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
