[ 
https://issues.apache.org/jira/browse/SOLR-14557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17169710#comment-17169710
 ] 

David Smiley commented on SOLR-14557:
-------------------------------------

Is there really no fix aside from using \_query_ ?  I view that as very legacy 
that ought to go away some day.  Solr doesn't need two ways to do the same 
thing... we add new better ways but not remove the old :-/

> Unable to parse local params followed by parenthesis like {!lucene}(gigabyte)
> -----------------------------------------------------------------------------
>
>                 Key: SOLR-14557
>                 URL: https://issues.apache.org/jira/browse/SOLR-14557
>             Project: Solr
>          Issue Type: Bug
>          Components: query parsers
>            Reporter: Mikhail Khludnev
>            Assignee: Mikhail Khludnev
>            Priority: Major
>              Labels: painful
>         Attachments: SOLR-14557.patch, SOLR-14557.patch, SOLR-14557.patch
>
>
> h2. Solr 4.5
> {{/select?defType=edismax&q=\{!lucene}(foo)&debugQuery=true}} 
>  
>  goes like
>  {code}
>  <str name="rawquerystring">\{!lucene}(foo)</str>
>  <str name="parsedquery_toString">content:foo</str>
>  <str name="QParser">LuceneQParser</str>
> {code}
> fine
> h2. Solr 8.2 
> with luceneMatchVersion=4.5 following SOLR-11501 I know it's a grey zone but 
> it's a question of migrating existing queries. 
> {{/select?defType=edismax&q=\{!lucene}(foo)&debugQuery=true}} 
> goes like 
> {code}
> "querystring":"\{!lucene}(foo)",
>  "parsedquery":"+DisjunctionMaxQuery(((Project.Address:lucene 
> Project.Address:foo) | (Project.OwnerType:lucene Project.OwnerType:foo) 
>  "QParser":"ExtendedDismaxQParser",
> {code}
> blah... 
> but removing braces in 8.2 works perfectly fine 
> {code}
> "querystring":"\{!lucene}foo",
>  "parsedquery":"+content:foo",
>  "parsedquery_toString":"+content:foo",
>  "QParser":"ExtendedDismaxQParser",
>  {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to