[jira] [Commented] (SOLR-3823) Parentheses in a boost query cause errors
[
https://issues.apache.org/jira/browse/SOLR-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13610875#comment-13610875
]
Commit Tag Bot commented on SOLR-3823:
--
[branch_4x commit] Chris M. Hostetter
http://svn.apache.org/viewvc?view=revision&revision=1383716
SOLR-3823: Fix 'bq' parsing in edismax. Please note that this required
reverting the negative boost support added by SOLR-3278 (merge r1383708)
> Parentheses in a boost query cause errors
> -
>
> Key: SOLR-3823
> URL: https://issues.apache.org/jira/browse/SOLR-3823
> Project: Solr
> Issue Type: Bug
> Components: query parsers
>Affects Versions: 4.0-BETA
> Environment: Mac, jdk 1.6, Chrome
>Reporter: Mathos Marcer
>Assignee: Hoss Man
> Fix For: 4.0, 5.0
>
>
> When using a boost query (bq) that contains a parentheses (like this example
> from the Relevancy Cookbook section of the wiki):
> {noformat}
> ? defType = dismax
> & q = foo bar
> & bq = (*:* -xxx)^999
> {noformat}
> You get the following error:
> org.apache.lucene.queryparser.classic.ParseException: Cannot parse '-xxx)':
> Encountered " ")" ") "" at line 1, column 12. Was expecting one of:
> ... ... ... "+" ... "-" ... ... "(" ... "*" ...
> "^" ... ... ... ... ...
> ... ... "[" ... "{" ... ...
--
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] [Commented] (SOLR-3823) Parentheses in a boost query cause errors
[
https://issues.apache.org/jira/browse/SOLR-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13458013#comment-13458013
]
Erik Hatcher commented on SOLR-3823:
bq. I see no evidence that "bq" is incorrectly using the defType parser in
either dismax or edismax
Ok, sorry I misinterpreted the nature of this issue apparently.
> Parentheses in a boost query cause errors
> -
>
> Key: SOLR-3823
> URL: https://issues.apache.org/jira/browse/SOLR-3823
> Project: Solr
> Issue Type: Bug
> Components: query parsers
>Affects Versions: 4.0-BETA
> Environment: Mac, jdk 1.6, Chrome
>Reporter: Mathos Marcer
>Assignee: Hoss Man
> Fix For: 4.0, 5.0
>
>
> When using a boost query (bq) that contains a parentheses (like this example
> from the Relevancy Cookbook section of the wiki):
> {noformat}
> ? defType = dismax
> & q = foo bar
> & bq = (*:* -xxx)^999
> {noformat}
> You get the following error:
> org.apache.lucene.queryparser.classic.ParseException: Cannot parse '-xxx)':
> Encountered " ")" ") "" at line 1, column 12. Was expecting one of:
> ... ... ... "+" ... "-" ... ... "(" ... "*" ...
> "^" ... ... ... ... ...
> ... ... "[" ... "{" ... ...
--
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] [Commented] (SOLR-3823) Parentheses in a boost query cause errors
[
https://issues.apache.org/jira/browse/SOLR-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13457513#comment-13457513
]
Jack Krupansky commented on SOLR-3823:
--
bq. ...this is how subqueries have always worked with QParsers
Is there any wiki/Javadoc that documents this behavior?
I would also note that both the dismax and edismax wiki pages for "bq" say:
bq. A raw query string (in the SolrQuerySyntax)
which is not right. We know it uses defType, but we clearly need the precise
language as it is supposed to be (noting the comments by hossman.)
See:
http://wiki.apache.org/solr/DisMaxQParserPlugin#bq_.28Boost_Query.29
http://wiki.apache.org/solr/ExtendedDisMax#bq_.28Boost_Query.29
> Parentheses in a boost query cause errors
> -
>
> Key: SOLR-3823
> URL: https://issues.apache.org/jira/browse/SOLR-3823
> Project: Solr
> Issue Type: Bug
> Components: query parsers
>Affects Versions: 4.0-BETA
> Environment: Mac, jdk 1.6, Chrome
>Reporter: Mathos Marcer
>Assignee: Hoss Man
> Fix For: 4.0, 5.0
>
>
> When using a boost query (bq) that contains a parentheses (like this example
> from the Relevancy Cookbook section of the wiki):
> {noformat}
> ? defType = dismax
> & q = foo bar
> & bq = (*:* -xxx)^999
> {noformat}
> You get the following error:
> org.apache.lucene.queryparser.classic.ParseException: Cannot parse '-xxx)':
> Encountered " ")" ") "" at line 1, column 12. Was expecting one of:
> ... ... ... "+" ... "-" ... ... "(" ... "*" ...
> "^" ... ... ... ... ...
> ... ... "[" ... "{" ... ...
--
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] [Commented] (SOLR-3823) Parentheses in a boost query cause errors
[
https://issues.apache.org/jira/browse/SOLR-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13457472#comment-13457472
]
Hoss Man commented on SOLR-3823:
bq. Sorry to chime in after this issue has been marked as resolved, but it
doesn't seem right to me that bq is parsed with the defType specified parser.
I don't understand this comment -- I see no evidence that "bq" is incorrectly
using the defType parser in either dismax or edismax.
In both cases null is passed to the subQuery() call for bq allowing it inherit
the defTYpe from the _localparams_ of the main "q" string (which is appropriate
since the bq is an implicit subquery added to the main query) but not a global
defType. ie, in the first example below, the "lucene" parser would be used to
parse the bq, while in the second example the "yyy" parser would be used
because of the explicit defType localparam...
{noformat}
/select?qf=name+text&defType=xxx&q={!edismax}mainquery&bq=myboost
/select?qf=name+text&defType=xxx&q={!edismax defType=yyy}mainquery&bq=myboost
{noformat}
...this is how subqueries have always worked with QParsers. if you think this
should be reconsidered, please open a specific issue.
(NOTE: fq's are not subqueries of the main query, so they don't look at the "q"
at all)
> Parentheses in a boost query cause errors
> -
>
> Key: SOLR-3823
> URL: https://issues.apache.org/jira/browse/SOLR-3823
> Project: Solr
> Issue Type: Bug
> Components: query parsers
>Affects Versions: 4.0-BETA
> Environment: Mac, jdk 1.6, Chrome
>Reporter: Mathos Marcer
>Assignee: Hoss Man
> Fix For: 4.0, 5.0
>
>
> When using a boost query (bq) that contains a parentheses (like this example
> from the Relevancy Cookbook section of the wiki):
> {noformat}
> ? defType = dismax
> & q = foo bar
> & bq = (*:* -xxx)^999
> {noformat}
> You get the following error:
> org.apache.lucene.queryparser.classic.ParseException: Cannot parse '-xxx)':
> Encountered " ")" ") "" at line 1, column 12. Was expecting one of:
> ... ... ... "+" ... "-" ... ... "(" ... "*" ...
> "^" ... ... ... ... ...
> ... ... "[" ... "{" ... ...
--
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] [Commented] (SOLR-3823) Parentheses in a boost query cause errors
[
https://issues.apache.org/jira/browse/SOLR-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455831#comment-13455831
]
Jack Krupansky commented on SOLR-3823:
--
bq. bq is parsed with the defType specified parser. Rather it should, like
fq's, default to the "lucene" query parser.
Sounds reasonable for fq and bq to be parsed the same way, but it seems
unrelated to this specific Jira.
> Parentheses in a boost query cause errors
> -
>
> Key: SOLR-3823
> URL: https://issues.apache.org/jira/browse/SOLR-3823
> Project: Solr
> Issue Type: Bug
> Components: query parsers
>Affects Versions: 4.0-BETA
> Environment: Mac, jdk 1.6, Chrome
>Reporter: Mathos Marcer
>Assignee: Hoss Man
> Fix For: 4.0, 5.0
>
>
> When using a boost query (bq) that contains a parentheses (like this example
> from the Relevancy Cookbook section of the wiki):
> {noformat}
> ? defType = dismax
> & q = foo bar
> & bq = (*:* -xxx)^999
> {noformat}
> You get the following error:
> org.apache.lucene.queryparser.classic.ParseException: Cannot parse '-xxx)':
> Encountered " ")" ") "" at line 1, column 12. Was expecting one of:
> ... ... ... "+" ... "-" ... ... "(" ... "*" ...
> "^" ... ... ... ... ...
> ... ... "[" ... "{" ... ...
--
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] [Commented] (SOLR-3823) Parentheses in a boost query cause errors
[
https://issues.apache.org/jira/browse/SOLR-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455792#comment-13455792
]
Erik Hatcher commented on SOLR-3823:
Sorry to chime in after this issue has been marked as resolved, but it
doesn't seem right to me that bq is parsed with the defType specified parser.
Rather it should, like fq's, default to the "lucene" query parser. No?
> Parentheses in a boost query cause errors
> -
>
> Key: SOLR-3823
> URL: https://issues.apache.org/jira/browse/SOLR-3823
> Project: Solr
> Issue Type: Bug
> Components: query parsers
>Affects Versions: 4.0-BETA
> Environment: Mac, jdk 1.6, Chrome
>Reporter: Mathos Marcer
>Assignee: Hoss Man
> Fix For: 4.0, 5.0
>
>
> When using a boost query (bq) that contains a parentheses (like this example
> from the Relevancy Cookbook section of the wiki):
> {noformat}
> ? defType = dismax
> & q = foo bar
> & bq = (*:* -xxx)^999
> {noformat}
> You get the following error:
> org.apache.lucene.queryparser.classic.ParseException: Cannot parse '-xxx)':
> Encountered " ")" ") "" at line 1, column 12. Was expecting one of:
> ... ... ... "+" ... "-" ... ... "(" ... "*" ...
> "^" ... ... ... ... ...
> ... ... "[" ... "{" ... ...
--
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] [Commented] (SOLR-3823) Parentheses in a boost query cause errors
[
https://issues.apache.org/jira/browse/SOLR-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454126#comment-13454126
]
James Dyer commented on SOLR-3823:
--
Hoss, Thank you for working through this and opening Lucene-4378 to at least
investigate changing the parser grammar. I understand the issue with what I
had done initially and appreciate your help on this.
> Parentheses in a boost query cause errors
> -
>
> Key: SOLR-3823
> URL: https://issues.apache.org/jira/browse/SOLR-3823
> Project: Solr
> Issue Type: Bug
> Components: query parsers
>Affects Versions: 4.0-BETA
> Environment: Mac, jdk 1.6, Chrome
>Reporter: Mathos Marcer
>Assignee: Hoss Man
> Fix For: 4.0, 5.0
>
>
> When using a boost query (bq) that contains a parentheses (like this example
> from the Relevancy Cookbook section of the wiki):
> {noformat}
> ? defType = dismax
> & q = foo bar
> & bq = (*:* -xxx)^999
> {noformat}
> You get the following error:
> org.apache.lucene.queryparser.classic.ParseException: Cannot parse '-xxx)':
> Encountered " ")" ") "" at line 1, column 12. Was expecting one of:
> ... ... ... "+" ... "-" ... ... "(" ... "*" ...
> "^" ... ... ... ... ...
> ... ... "[" ... "{" ... ...
--
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] [Commented] (SOLR-3823) Parentheses in a boost query cause errors
[
https://issues.apache.org/jira/browse/SOLR-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454104#comment-13454104
]
Hoss Man commented on SOLR-3823:
bq. I couldn't tell that this issue was an actual problem or a case of users
putting whitespace where it doesn't belong and prior versions being more
forgiving.
James: the core of the bug was your use of SolrPluginUtils.parseFieldBoosts to
try and parse the bq params.
This is not safe -- if you look at the method it is an extremely trivial
utility that is specific for parsing qf/pf style strings containing a list of
field names and boosts. it's _not_ a safe way to parse an arbitrary query
string, and any non trivial query string can cause problems with it.
AS you noted in SOLR-3278, parseFieldBoosts is used for parsing the "bf" param
and that's actually a long standing unsafe bug as well (SOLR-2014) but since
functions tend to be much simpler, it's historically been less problematic.
when people run into problems with it, the workarround is to use
"bq={!func}..." instead.
bq. I would rather get a fix that preserves the negative boost support
Since SOLR-3278 had not been released publicly outside of the ALPHA/BETA, my
first priority was to fix the regression compared to 3.x where non-trivial bq
queries worked fine.
The documented method of dealing with "negative boosting" in solr is actually
the type of query that was the crux of this bug report, and i updated the tests
you added in SOLR-3278 to use that pattern...
https://wiki.apache.org/solr/SolrRelevancyFAQ#How_do_I_give_a_negative_.28or_very_low.29_boost_to_documents_that_match_a_query.3F
I have no objections to supporting "true" negative boosts, but i think the
right way to do it is in the query parsers / QParsers themselves (so that the
boosts can be on any clause) and not just as a special hack for bq/bf (the fact
that it works in bf is actualy just a fluke of it's buggy implementation) but
as you can see in LUCENE-4378 this is a contentious idea.
> Parentheses in a boost query cause errors
> -
>
> Key: SOLR-3823
> URL: https://issues.apache.org/jira/browse/SOLR-3823
> Project: Solr
> Issue Type: Bug
> Components: query parsers
>Affects Versions: 4.0-BETA
> Environment: Mac, jdk 1.6, Chrome
>Reporter: Mathos Marcer
>Assignee: Hoss Man
> Fix For: 4.0, 5.0
>
>
> When using a boost query (bq) that contains a parentheses (like this example
> from the Relevancy Cookbook section of the wiki):
> {noformat}
> ? defType = dismax
> & q = foo bar
> & bq = (*:* -xxx)^999
> {noformat}
> You get the following error:
> org.apache.lucene.queryparser.classic.ParseException: Cannot parse '-xxx)':
> Encountered " ")" ") "" at line 1, column 12. Was expecting one of:
> ... ... ... "+" ... "-" ... ... "(" ... "*" ...
> "^" ... ... ... ... ...
> ... ... "[" ... "{" ... ...
--
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] [Commented] (SOLR-3823) Parentheses in a boost query cause errors
[
https://issues.apache.org/jira/browse/SOLR-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454059#comment-13454059
]
Erick Erickson commented on SOLR-3823:
--
James:
The problem was quite the opposite. When there was NO space in the bq clause
it'd fail like this, i.e.
bq=(stuff). And when there was space, I don't think it worked at all
But yeah, it'd be good to have both parens and negative boosts...
> Parentheses in a boost query cause errors
> -
>
> Key: SOLR-3823
> URL: https://issues.apache.org/jira/browse/SOLR-3823
> Project: Solr
> Issue Type: Bug
> Components: query parsers
>Affects Versions: 4.0-BETA
> Environment: Mac, jdk 1.6, Chrome
>Reporter: Mathos Marcer
>Assignee: Hoss Man
> Fix For: 4.0, 5.0
>
>
> When using a boost query (bq) that contains a parentheses (like this example
> from the Relevancy Cookbook section of the wiki):
> {noformat}
> ? defType = dismax
> & q = foo bar
> & bq = (*:* -xxx)^999
> {noformat}
> You get the following error:
> org.apache.lucene.queryparser.classic.ParseException: Cannot parse '-xxx)':
> Encountered " ")" ") "" at line 1, column 12. Was expecting one of:
> ... ... ... "+" ... "-" ... ... "(" ... "*" ...
> "^" ... ... ... ... ...
> ... ... "[" ... "{" ... ...
--
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] [Commented] (SOLR-3823) Parentheses in a boost query cause errors
[
https://issues.apache.org/jira/browse/SOLR-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454028#comment-13454028
]
James Dyer commented on SOLR-3823:
--
Hoss,
I appreciate you fixing this, but I would rather get a fix that preserves the
negative boost support (SOLR-3278). I guess I don't understand the bug this
issue was addressing. Is it simply that "bq" would fail if extra whitespace
was in the query? Could we write a failing testcase for that? Do you see a
reason why it would be difficult to fix this and retain the negative boosts?
The discussion of LUCENE-4378 is pertinent: we have products in our index that
we either do not sell or we know most of our customer do not want. Yet they
often score very high. The only way I can reliably prevent these from becoming
top hits is to use a negative boost. I would imagine this is a frequent
requirement.
I'm more than willing to contribute for this, but I couldn't tell that this
issue was an actual problem or a case of users putting whitespace where it
doesn't belong and prior versions being more forgiving.
> Parentheses in a boost query cause errors
> -
>
> Key: SOLR-3823
> URL: https://issues.apache.org/jira/browse/SOLR-3823
> Project: Solr
> Issue Type: Bug
> Components: query parsers
>Affects Versions: 4.0-BETA
> Environment: Mac, jdk 1.6, Chrome
>Reporter: Mathos Marcer
>Assignee: Hoss Man
> Fix For: 4.0, 5.0
>
>
> When using a boost query (bq) that contains a parentheses (like this example
> from the Relevancy Cookbook section of the wiki):
> {noformat}
> ? defType = dismax
> & q = foo bar
> & bq = (*:* -xxx)^999
> {noformat}
> You get the following error:
> org.apache.lucene.queryparser.classic.ParseException: Cannot parse '-xxx)':
> Encountered " ")" ") "" at line 1, column 12. Was expecting one of:
> ... ... ... "+" ... "-" ... ... "(" ... "*" ...
> "^" ... ... ... ... ...
> ... ... "[" ... "{" ... ...
--
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] [Commented] (SOLR-3823) Parentheses in a boost query cause errors
[
https://issues.apache.org/jira/browse/SOLR-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453421#comment-13453421
]
Jack Krupansky commented on SOLR-3823:
--
It turns out that it is the white space that causes the problem.
Looking at the code, I see that edismax calls SolrPluginUtils.parseFieldBoosts
to "parse" the "bq" value, which is absurd since it simply breaks up the param
value based on whitespace, even in the middle of the query. Then the code calls
QParser.subQuery to parse the portions of the query, which of course makes no
sense unless the original query contained no whitespace or was a sequence of
non-white space queries separated with whitespace.
Dismax, OTOH, treats "bq" as an array of query strings (multiple "bq" params)
and parses each as a separate sub-query.
Edismax in 3.6/3.6.1 has the old dismax code.
The culprit? SOLR-3278: "edismax support for negative boost with "bq"
parameter" introduced the error, back in March.
> Parentheses in a boost query cause errors
> -
>
> Key: SOLR-3823
> URL: https://issues.apache.org/jira/browse/SOLR-3823
> Project: Solr
> Issue Type: Bug
> Components: query parsers
>Affects Versions: 4.0-BETA
> Environment: Mac, jdk 1.6, Chrome
>Reporter: Mathos Marcer
>
> When using a boost query (bq) that contains a parentheses (like this example
> from the Relevancy Cookbook section of the wiki):
> {noformat}
> ? defType = dismax
> & q = foo bar
> & bq = (*:* -xxx)^999
> {noformat}
> You get the following error:
> org.apache.lucene.queryparser.classic.ParseException: Cannot parse '-xxx)':
> Encountered " ")" ") "" at line 1, column 12. Was expecting one of:
> ... ... ... "+" ... "-" ... ... "(" ... "*" ...
> "^" ... ... ... ... ...
> ... ... "[" ... "{" ... ...
--
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] [Commented] (SOLR-3823) Parentheses in a boost query cause errors
[
https://issues.apache.org/jira/browse/SOLR-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453356#comment-13453356
]
Erick Erickson commented on SOLR-3823:
--
FWIW, I'm on a Mac (Lion) too, although I doubt that matters.
> Parentheses in a boost query cause errors
> -
>
> Key: SOLR-3823
> URL: https://issues.apache.org/jira/browse/SOLR-3823
> Project: Solr
> Issue Type: Bug
> Components: query parsers
>Affects Versions: 4.0-BETA
> Environment: Mac, jdk 1.6, Chrome
>Reporter: Mathos Marcer
>
> When using a boost query (bq) that contains a parentheses (like this example
> from the Relevancy Cookbook section of the wiki):
> {noformat}
> ? defType = dismax
> & q = foo bar
> & bq = (*:* -xxx)^999
> {noformat}
> You get the following error:
> org.apache.lucene.queryparser.classic.ParseException: Cannot parse '-xxx)':
> Encountered " ")" ") "" at line 1, column 12. Was expecting one of:
> ... ... ... "+" ... "-" ... ... "(" ... "*" ...
> "^" ... ... ... ... ...
> ... ... "[" ... "{" ... ...
--
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] [Commented] (SOLR-3823) Parentheses in a boost query cause errors
[
https://issues.apache.org/jira/browse/SOLR-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453350#comment-13453350
]
Mathos Marcer commented on SOLR-3823:
-
Actually looking at it closer, it is probably because with adding the space
after bq is it doesn't register it as "bq" but as "bq " looking at the params
section of the query:
(*:* -replacement)^9950
> Parentheses in a boost query cause errors
> -
>
> Key: SOLR-3823
> URL: https://issues.apache.org/jira/browse/SOLR-3823
> Project: Solr
> Issue Type: Bug
> Components: query parsers
>Affects Versions: 4.0-BETA
> Environment: Mac, jdk 1.6, Chrome
>Reporter: Mathos Marcer
>
> When using a boost query (bq) that contains a parentheses (like this example
> from the Relevancy Cookbook section of the wiki):
> {noformat}
> ? defType = dismax
> & q = foo bar
> & bq = (*:* -xxx)^999
> {noformat}
> You get the following error:
> org.apache.lucene.queryparser.classic.ParseException: Cannot parse '-xxx)':
> Encountered " ")" ") "" at line 1, column 12. Was expecting one of:
> ... ... ... "+" ... "-" ... ... "(" ... "*" ...
> "^" ... ... ... ... ...
> ... ... "[" ... "{" ... ...
--
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] [Commented] (SOLR-3823) Parentheses in a boost query cause errors
[
https://issues.apache.org/jira/browse/SOLR-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453349#comment-13453349
]
Mathos Marcer commented on SOLR-3823:
-
I'm glad I'm not just going crazy :-)
I did notice while the space before the equal sign (ie "bq =(name:nonsense
-xxx)^999") doesn't produce a parsing error, comparing results between 3.6 and
4.0 BETA, it doesn't appear to be applying the boost. In fact I get the same
results as if I didn't have the "bq" option there at all.
> Parentheses in a boost query cause errors
> -
>
> Key: SOLR-3823
> URL: https://issues.apache.org/jira/browse/SOLR-3823
> Project: Solr
> Issue Type: Bug
> Components: query parsers
>Affects Versions: 4.0-BETA
> Environment: Mac, jdk 1.6, Chrome
>Reporter: Mathos Marcer
>
> When using a boost query (bq) that contains a parentheses (like this example
> from the Relevancy Cookbook section of the wiki):
> {noformat}
> ? defType = dismax
> & q = foo bar
> & bq = (*:* -xxx)^999
> {noformat}
> You get the following error:
> org.apache.lucene.queryparser.classic.ParseException: Cannot parse '-xxx)':
> Encountered " ")" ") "" at line 1, column 12. Was expecting one of:
> ... ... ... "+" ... "-" ... ... "(" ... "*" ...
> "^" ... ... ... ... ...
> ... ... "[" ... "{" ... ...
--
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] [Commented] (SOLR-3823) Parentheses in a boost query cause errors
[
https://issues.apache.org/jira/browse/SOLR-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453314#comment-13453314
]
Mathos Marcer commented on SOLR-3823:
-
The problem seems to be when I specify defType=edismax, under defType=dismax it
is working like a champ.
> Parentheses in a boost query cause errors
> -
>
> Key: SOLR-3823
> URL: https://issues.apache.org/jira/browse/SOLR-3823
> Project: Solr
> Issue Type: Bug
> Components: query parsers
>Affects Versions: 4.0-BETA
> Environment: Mac, jdk 1.6, Chrome
>Reporter: Mathos Marcer
>
> When using a boost query (bq) that contains a parentheses (like this example
> from the Relevancy Cookbook section of the wiki):
> {noformat}
> ? defType = dismax
> & q = foo bar
> & bq = (*:* -xxx)^999
> {noformat}
> You get the following error:
> org.apache.lucene.queryparser.classic.ParseException: Cannot parse '-xxx)':
> Encountered " ")" ") "" at line 1, column 12. Was expecting one of:
> ... ... ... "+" ... "-" ... ... "(" ... "*" ...
> "^" ... ... ... ... ...
> ... ... "[" ... "{" ... ...
--
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
