[jira] [Comment Edited] (SOLR-3377) eDismax: A fielded query wrapped by parens is not recognized
[
https://issues.apache.org/jira/browse/SOLR-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13473024#comment-13473024
]
Shawn Heisey edited comment on SOLR-3377 at 10/10/12 6:51 AM:
--
I confirmed (using the solr example) that 4.0-BETA and lucene_solr_4_0 can
parse a query similar to my test query perfectly. Query URL created by filling
out the admin query interface:
http://server:8983/solr/collection1/select?q=((cat%3Astring1)+OR+(cat%3Astring2)+OR+(cat%3Astring3)+(Kitchen+Sink))wt=xmldebugQuery=truedefType=edismaxqf=textpf=text%5E2
was (Author: elyograg):
I confirmed (using the solr example) that 4.0-BETA and lucene_solr_4_0 can
parse a query similar to my test query perfectly. Query URL created by filling
out the admin query interface:
http://server:8983/solr/collection1/select?q=((cat%3Astring1)+OR+(cat%3Astring2)+OR+(cat%3Astring3)+(Kitchen+Sink))wt=xmldebugQuery=truedefType=edismaxqf=textpf=text%5E2
Just for completeness, I also tried it in the lucene_solr_3_6 example. It
behaves just like 3.5.0 does, including working when the spaces are added.
Solr Implementation Version: 3.6.2-SNAPSHOT 1396476 - root - 2012-10-09 23:48:08
I will file a separate bug on 3.6.1 related to this one.
eDismax: A fielded query wrapped by parens is not recognized
Key: SOLR-3377
URL: https://issues.apache.org/jira/browse/SOLR-3377
Project: Solr
Issue Type: Bug
Components: query parsers
Affects Versions: 3.6
Reporter: Jan Høydahl
Assignee: Yonik Seeley
Priority: Critical
Fix For: 4.0-BETA
Attachments: SOLR-3377.patch, SOLR-3377.patch, SOLR-3377.patch,
SOLR-3377.patch
As reported by bernd on the user list, a query like this
{{q=(name:test)}}
will yield 0 hits in 3.6 while it worked in 3.5. It works without the parens.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (SOLR-3377) eDismax: A fielded query wrapped by parens is not recognized
[
https://issues.apache.org/jira/browse/SOLR-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13411542#comment-13411542
]
Yonik Seeley edited comment on SOLR-3377 at 7/12/12 5:01 AM:
-
I took a quick look at the current edismax code.
The major flaw seems to be the attempt to check user fields in
splitIntoClauses(). That method was never meant to be an exact replication of
Lucene query parsing. Is there a reason we aren't checking user fields in the
parser itself (the ExtendedSolrQueryParser.getFieldQuery)?
edit: thinking a little more about it, I guess one reason is so whitespace or
other potentially significant syntax isn't discarded?
was (Author: ysee...@gmail.com):
I took a quick look at the current edismax code.
The major flaw seems to be the attempt to check user fields in
splitIntoClauses(). That method was never meant to be an exact replication of
Lucene query parsing. Is there a reason we aren't checking user fields in the
parser itself (the ExtendedSolrQueryParser.getFieldQuery)?
eDismax: A fielded query wrapped by parens is not recognized
Key: SOLR-3377
URL: https://issues.apache.org/jira/browse/SOLR-3377
Project: Solr
Issue Type: Bug
Components: query parsers
Affects Versions: 3.6
Reporter: Jan Høydahl
Priority: Critical
Fix For: 4.0
Attachments: SOLR-3377.patch, SOLR-3377.patch, SOLR-3377.patch,
SOLR-3377.patch
As reported by bernd on the user list, a query like this
{{q=(name:test)}}
will yield 0 hits in 3.6 while it worked in 3.5. It works without the parens.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (SOLR-3377) eDismax: A fielded query wrapped by parens is not recognized
[
https://issues.apache.org/jira/browse/SOLR-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406866#comment-13406866
]
Bernd Fehling edited comment on SOLR-3377 at 7/5/12 6:10 AM:
-
I was willing to supply a final fix to this and was hoping that it will make it
to release 4.x.
But unfortunately:
- I got no enhanced unit test
- noone comitted this/my patch either
- the problem is still there
So I said was willing, thats true, I gave up on this and thinking now about
switching to ElasticSearch because they really appreciate any help.
was (Author: befehl):
I was willing to supply a final fix to this and was hoping that it will
make it to release 4.x.
But unfortunately:
- I got no enhanced unit test
- noone comitted this/my patch either
- the problem is still there
So I said was willing, thats true, I gave up on this and thinking now about
switching to ElasticSearch because they really appreciate any help.
eDismax: A fielded query wrapped by parens is not recognized
Key: SOLR-3377
URL: https://issues.apache.org/jira/browse/SOLR-3377
Project: Solr
Issue Type: Bug
Components: query parsers
Affects Versions: 3.6
Reporter: Jan Høydahl
Fix For: 4.0, 3.6.1
Attachments: SOLR-3377.patch, SOLR-3377.patch, SOLR-3377.patch,
SOLR-3377.patch
As reported by bernd on the user list, a query like this
{{q=(name:test)}}
will yield 0 hits in 3.6 while it worked in 3.5. It works without the parens.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
