You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Tommaso Teofili (JIRA)" <ji...@apache.org> on 2018/03/22 14:12:00 UTC
[jira] [Resolved] (OAK-7375) Wrong full text parsing in Oak Solr
index with boolean operators
[ https://issues.apache.org/jira/browse/OAK-7375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tommaso Teofili resolved OAK-7375.
----------------------------------
Resolution: Fixed
Fix Version/s: 1.8.3
fixed in trunk (r1827486), 1.8 (r1827493), 1.6 (r1827497).
> Wrong full text parsing in Oak Solr index with boolean operators
> ----------------------------------------------------------------
>
> Key: OAK-7375
> URL: https://issues.apache.org/jira/browse/OAK-7375
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: solr
> Affects Versions: 1.8.2
> Reporter: Tommaso Teofili
> Assignee: Tommaso Teofili
> Priority: Major
> Fix For: 1.9.0, 1.8.3, 1.6.11
>
>
> Parsing of JCR full text clauses in Solr index has a bug so that queries like _'foo AND bar'_ get translated into Solr queries like _'field:foo AND field:AND AND field:bar'_. The _field:AND_ clause is the problematic one because _AND_ is a protected operator in the Lucene / Solr syntax and therefore needs to be either escaped or put into quotes.
> However the right fix would be to skip including the _AND_ (and _OR_) terms in the fielded query below.
> So the JCR query _/jcr:root//*[jcr:contains(., 'foo AND bar')]_ should be converted into _'field:foo AND field:bar'_.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)