[jira] [Commented] (SOLR-7964) suggest.highlight=true does not work when using context filter query
[
https://issues.apache.org/jira/browse/SOLR-7964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16664137#comment-16664137
]
Jigar Shah commented on SOLR-7964:
--
+1
Waiting for this fix to be included from 6.5 version.
Any plans to include in 7.x version.
Many Thanks!
J
> suggest.highlight=true does not work when using context filter query
>
>
> Key: SOLR-7964
> URL: https://issues.apache.org/jira/browse/SOLR-7964
> Project: Solr
> Issue Type: Improvement
> Components: Suggester
>Affects Versions: 5.4
>Reporter: Arcadius Ahouansou
>Priority: Minor
> Labels: suggester
> Attachments: SOLR-7964.patch, SOLR_7964.patch, SOLR_7964.patch
>
>
> When using the new suggester context filtering query param
> {{suggest.contextFilterQuery}} introduced in SOLR-7888, the param
> {{suggest.highlight=true}} has no effect.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7619) Add WordDelimiterGraphFilter
[
https://issues.apache.org/jira/browse/LUCENE-7619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15892428#comment-15892428
]
Jigar Shah commented on LUCENE-7619:
I will go for snapshot for now. Thanks for suggesting direction :)
Many Thanks!
> Add WordDelimiterGraphFilter
>
>
> Key: LUCENE-7619
> URL: https://issues.apache.org/jira/browse/LUCENE-7619
> Project: Lucene - Core
> Issue Type: Improvement
>Reporter: Michael McCandless
>Assignee: Michael McCandless
> Fix For: master (7.0), 6.5
>
> Attachments: after.png, before.png, LUCENE-7619.patch,
> LUCENE-7619.patch, LUCENE-7619.patch
>
>
> Currently, {{WordDelimiterFilter}} doesn't try to set the {{posLen}}
> attribute and so it creates graphs like this:
> !before.png!
> but with this patch (still a work in progress) it creates this graph instead:
> !after.png!
> This means (today) positional queries when using WDF at search time are
> buggy, but since we fixed LUCENE-7603, with this change here you should be
> able to use positional queries with WDGF.
> I'm also trying to produce holes properly (removes logic from the current WDF
> that swallows a hole when whole token is just delimiters).
> Surprisingly, it's actually quite easy to tweak WDF to create a graph (unlike
> e.g. {{SynonymGraphFilter}}) because it's already creating the necessary new
> positions, and its output graph never has side paths, except for single
> tokens that skip nodes because they have {{posLen > 1}}. I.e. the only fix
> to make, I think, is to set {{posLen}} properly. And it really helps that it
> does its own "new token buffering + sorting" already.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7619) Add WordDelimiterGraphFilter
[
https://issues.apache.org/jira/browse/LUCENE-7619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15888747#comment-15888747
]
Jigar Shah commented on LUCENE-7619:
Hello [~mikemccand]
+1
Many thanks for fixing this!
I am using WordDelemeterFilter (which often breaks phrase queries on words with
puntuations). I am currently using Lucene 6.4.1 in production. Can you please
suggest which classes I should patch on Lucene 6.4.1 to use this feature.
Patching just WordDelimiterGraphFilter and using it in token stream instead of
WordDelemeterFilter be fine? or there are any other dependent classes which I
have to patch (please provide list if there are other classes too) ?
Once Lucene 6.5 is released i will upgrade to Lucene 6.5 so i will get better
tested fix, but for now i would like to patch Lucene 6.4.1 if patch is
compitible and simple.
> Add WordDelimiterGraphFilter
>
>
> Key: LUCENE-7619
> URL: https://issues.apache.org/jira/browse/LUCENE-7619
> Project: Lucene - Core
> Issue Type: Improvement
>Reporter: Michael McCandless
>Assignee: Michael McCandless
> Fix For: master (7.0), 6.5
>
> Attachments: after.png, before.png, LUCENE-7619.patch,
> LUCENE-7619.patch, LUCENE-7619.patch
>
>
> Currently, {{WordDelimiterFilter}} doesn't try to set the {{posLen}}
> attribute and so it creates graphs like this:
> !before.png!
> but with this patch (still a work in progress) it creates this graph instead:
> !after.png!
> This means (today) positional queries when using WDF at search time are
> buggy, but since we fixed LUCENE-7603, with this change here you should be
> able to use positional queries with WDGF.
> I'm also trying to produce holes properly (removes logic from the current WDF
> that swallows a hole when whole token is just delimiters).
> Surprisingly, it's actually quite easy to tweak WDF to create a graph (unlike
> e.g. {{SynonymGraphFilter}}) because it's already creating the necessary new
> positions, and its output graph never has side paths, except for single
> tokens that skip nodes because they have {{posLen > 1}}. I.e. the only fix
> to make, I think, is to set {{posLen}} properly. And it really helps that it
> does its own "new token buffering + sorting" already.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-7964) suggest.highlight=true does not work when using context filter query
[
https://issues.apache.org/jira/browse/SOLR-7964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1484#comment-1484
]
Jigar Shah commented on SOLR-7964:
--
Waiting on this!
Issue is reproduced also on version 6.1. Any idea in which release this will be
available ?
> suggest.highlight=true does not work when using context filter query
>
>
> Key: SOLR-7964
> URL: https://issues.apache.org/jira/browse/SOLR-7964
> Project: Solr
> Issue Type: Improvement
> Components: Suggester
>Affects Versions: 5.4
>Reporter: Arcadius Ahouansou
>Priority: Minor
> Labels: suggester
> Attachments: SOLR_7964.patch, SOLR_7964.patch
>
>
> When using the new suggester context filtering query param
> {{suggest.contextFilterQuery}} introduced in SOLR-7888, the param
> {{suggest.highlight=true}} has no effect.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-6857) Validate StandardQueryParser with NOT operator with-in parantheses.
[ https://issues.apache.org/jira/browse/LUCENE-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jigar Shah updated LUCENE-6857: --- Attachment: LUCENE-6857.patch Test cases for NOT in parentheses. > Validate StandardQueryParser with NOT operator with-in parantheses. > --- > > Key: LUCENE-6857 > URL: https://issues.apache.org/jira/browse/LUCENE-6857 > Project: Lucene - Core > Issue Type: Test > Components: core/queryparser >Affects Versions: 5.3 >Reporter: Jigar Shah >Assignee: Dawid Weiss > Fix For: Trunk > > Attachments: LUCENE-6857.patch > > > Provide test case to validate LUCENE-6249, which validates NOT in > parentheses. > e.g: > lottery (NOT ticket) > lottery (-ticket) > lottery AND (NOT ticket) > +lottery +(-ticket) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Resolved] (LUCENE-6857) Validate StandardQueryParser with NOT operator with-in parantheses.
[ https://issues.apache.org/jira/browse/LUCENE-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jigar Shah resolved LUCENE-6857. Resolution: Fixed Provide patch. Added testcases to validate LUCENE-6249 > Validate StandardQueryParser with NOT operator with-in parantheses. > --- > > Key: LUCENE-6857 > URL: https://issues.apache.org/jira/browse/LUCENE-6857 > Project: Lucene - Core > Issue Type: Test > Components: core/queryparser >Affects Versions: 5.3 >Reporter: Jigar Shah >Assignee: Dawid Weiss > Fix For: Trunk > > Attachments: LUCENE-6857.patch > > > Provide test case to validate LUCENE-6249, which validates NOT in > parentheses. > e.g: > lottery (NOT ticket) > lottery (-ticket) > lottery AND (NOT ticket) > +lottery +(-ticket) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-6857) Validate StandardQueryParser with NOT operator with-in parantheses.
[ https://issues.apache.org/jira/browse/LUCENE-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14977888#comment-14977888 ] Jigar Shah edited comment on LUCENE-6857 at 10/28/15 7:41 AM: -- Original issue description: Thanks for your reply Erick, I have gone through the document provided by you. However what I have observed is that there is difference if we parse query with Lucene 4.10.3 and Lucene 5.2.0 onwards. For example :Query String: lottery AND (NOT ticket)Lucene 4.x parsed it as: +lottery +ticket Lucene 5.1.x parsed it as: +lottery +(-ticket) And I want result as 5.1.x produces. But as I am not planning to upgrade lucene now so looking for fix for lucene 4.10.x. Please could you help on this? Thanks,Mrugesh --- Issue still remains in 4.10.3 release. because of LUCENE-6249, above mentioned issue is fixed. Provided patch for test case. Added testcases to validate LUCENE-6249 was (Author: infodroids): Provide patch. Added testcases to validate LUCENE-6249 > Validate StandardQueryParser with NOT operator with-in parantheses. > --- > > Key: LUCENE-6857 > URL: https://issues.apache.org/jira/browse/LUCENE-6857 > Project: Lucene - Core > Issue Type: Test > Components: core/queryparser >Affects Versions: 5.3 >Reporter: Jigar Shah >Assignee: Dawid Weiss > Fix For: Trunk > > Attachments: LUCENE-6857.patch > > > Provide test case to validate LUCENE-6249, which validates NOT in > parentheses. > e.g: > lottery (NOT ticket) > lottery (-ticket) > lottery AND (NOT ticket) > +lottery +(-ticket) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-6857) Validate StandardQueryParser with NOT operator with-in parantheses.
[ https://issues.apache.org/jira/browse/LUCENE-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14977888#comment-14977888 ] Jigar Shah edited comment on LUCENE-6857 at 10/28/15 7:44 AM: -- Following issue still remains in 4.10.3 release. LUCENE-6249 fixes following issue from 5.1. Original issue description: Thanks for your reply Erick, I have gone through the document provided by you. However what I have observed is that there is difference if we parse query with Lucene 4.10.3 and Lucene 5.2.0 onwards. For example :Query String: lottery AND (NOT ticket)Lucene 4.x parsed it as: +lottery +ticket Lucene 5.1.x parsed it as: +lottery +(-ticket) And I want result as 5.1.x produces. But as I am not planning to upgrade lucene now so looking for fix for lucene 4.10.x. Please could you help on this? Thanks,Mrugesh --- Provided patch for test case. Added testcases to validate LUCENE-6249 was (Author: infodroids): Original issue description: Thanks for your reply Erick, I have gone through the document provided by you. However what I have observed is that there is difference if we parse query with Lucene 4.10.3 and Lucene 5.2.0 onwards. For example :Query String: lottery AND (NOT ticket)Lucene 4.x parsed it as: +lottery +ticket Lucene 5.1.x parsed it as: +lottery +(-ticket) And I want result as 5.1.x produces. But as I am not planning to upgrade lucene now so looking for fix for lucene 4.10.x. Please could you help on this? Thanks,Mrugesh --- Issue still remains in 4.10.3 release. because of LUCENE-6249, above mentioned issue is fixed. Provided patch for test case. Added testcases to validate LUCENE-6249 > Validate StandardQueryParser with NOT operator with-in parantheses. > --- > > Key: LUCENE-6857 > URL: https://issues.apache.org/jira/browse/LUCENE-6857 > Project: Lucene - Core > Issue Type: Test > Components: core/queryparser >Affects Versions: 5.3 >Reporter: Jigar Shah >Assignee: Dawid Weiss > Fix For: Trunk > > Attachments: LUCENE-6857.patch > > > Provide test case to validate LUCENE-6249, which validates NOT in > parentheses. > e.g: > lottery (NOT ticket) > lottery (-ticket) > lottery AND (NOT ticket) > +lottery +(-ticket) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-6249) StandardQueryParser doesn't support pure negative clauses
[
https://issues.apache.org/jira/browse/LUCENE-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14977934#comment-14977934
]
Jigar Shah commented on LUCENE-6249:
Provided patch in LUCENE-6857.
I applied patch attached to the issue on 4.10.3 branch and it works!! Is it
possible to get this fix in 4.10.x version of Lucene ?
> StandardQueryParser doesn't support pure negative clauses
> -
>
> Key: LUCENE-6249
> URL: https://issues.apache.org/jira/browse/LUCENE-6249
> Project: Lucene - Core
> Issue Type: Bug
>Affects Versions: 4.10.3, 5.0
>Reporter: Dawid Weiss
>Assignee: Dawid Weiss
> Fix For: 5.1, Trunk
>
> Attachments: LUCENE-6249.patch
>
>
> At first I thought it's by design but Uwe says it's a bug. SQP emits this:
> {code}
> StandardQueryParser qp = new StandardQueryParser();
> qp.setDefaultOperator(Operator.AND);
>
> System.out.println(qp.parse("summary:foo", "deffld"));
> System.out.println(qp.parse("-summary:foo", "deffld"));
> System.out.println(qp.parse("!summary:foo", "deffld"));
> System.out.println(qp.parse("NOT summary:foo", "deffld"));
> {code}
> {code}
> summary:foo
> summary:foo
> summary:foo
> summary:foo
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-6857) Validate StandardQueryParser with NOT operator with-in parantheses.
[ https://issues.apache.org/jira/browse/LUCENE-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14977942#comment-14977942 ] Jigar Shah commented on LUCENE-6857: Sorry, for putting directly to resolved state. Will wait for your response. Thanks :) > Validate StandardQueryParser with NOT operator with-in parantheses. > --- > > Key: LUCENE-6857 > URL: https://issues.apache.org/jira/browse/LUCENE-6857 > Project: Lucene - Core > Issue Type: Test > Components: core/queryparser >Affects Versions: 5.3 >Reporter: Jigar Shah >Assignee: Dawid Weiss > Fix For: Trunk > > Attachments: LUCENE-6857.patch > > > Provide test case to validate LUCENE-6249, which validates NOT in > parentheses. > e.g: > lottery (NOT ticket) > lottery (-ticket) > lottery AND (NOT ticket) > +lottery +(-ticket) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-6249) StandardQueryParser doesn't support pure negative clauses
[
https://issues.apache.org/jira/browse/LUCENE-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14978114#comment-14978114
]
Jigar Shah commented on LUCENE-6249:
It seems this fix is very important considering the following case, it returns
hits when it should not return, to me it seems a major bug.
lottery AND (NOT ticket)
Lucene 4.10.3: +lottery +ticket [Incorrect] gives results just because its
parsed incorrectly.
Lucene 5.2.0: +lottery +(-ticket) [Correct]
And this fix seems to be safe for 4.10 version !! I am not in hurry to get
this, But it will be helpful in case some production systems are on 4.x
version, and don't want to re-index there database for 5.x just for query
parser change.
> StandardQueryParser doesn't support pure negative clauses
> -
>
> Key: LUCENE-6249
> URL: https://issues.apache.org/jira/browse/LUCENE-6249
> Project: Lucene - Core
> Issue Type: Bug
>Affects Versions: 4.10.3, 5.0
>Reporter: Dawid Weiss
>Assignee: Dawid Weiss
> Fix For: 5.1, Trunk
>
> Attachments: LUCENE-6249.patch
>
>
> At first I thought it's by design but Uwe says it's a bug. SQP emits this:
> {code}
> StandardQueryParser qp = new StandardQueryParser();
> qp.setDefaultOperator(Operator.AND);
>
> System.out.println(qp.parse("summary:foo", "deffld"));
> System.out.println(qp.parse("-summary:foo", "deffld"));
> System.out.println(qp.parse("!summary:foo", "deffld"));
> System.out.println(qp.parse("NOT summary:foo", "deffld"));
> {code}
> {code}
> summary:foo
> summary:foo
> summary:foo
> summary:foo
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-6249) StandardQueryParser doesn't support pure negative clauses
[
https://issues.apache.org/jira/browse/LUCENE-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14978653#comment-14978653
]
Jigar Shah commented on LUCENE-6249:
Thanks for this Backport :)
> StandardQueryParser doesn't support pure negative clauses
> -
>
> Key: LUCENE-6249
> URL: https://issues.apache.org/jira/browse/LUCENE-6249
> Project: Lucene - Core
> Issue Type: Bug
>Affects Versions: 4.10.3, 5.0
>Reporter: Dawid Weiss
>Assignee: Dawid Weiss
> Fix For: 4.10.5, 5.1, Trunk
>
> Attachments: LUCENE-6249.patch
>
>
> At first I thought it's by design but Uwe says it's a bug. SQP emits this:
> {code}
> StandardQueryParser qp = new StandardQueryParser();
> qp.setDefaultOperator(Operator.AND);
>
> System.out.println(qp.parse("summary:foo", "deffld"));
> System.out.println(qp.parse("-summary:foo", "deffld"));
> System.out.println(qp.parse("!summary:foo", "deffld"));
> System.out.println(qp.parse("NOT summary:foo", "deffld"));
> {code}
> {code}
> summary:foo
> summary:foo
> summary:foo
> summary:foo
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-6857) Validate StandardQueryParser with NOT operator with-in parantheses.
[ https://issues.apache.org/jira/browse/LUCENE-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14978083#comment-14978083 ] Jigar Shah commented on LUCENE-6857: Thanks for accepting patch. Will remember formatting tips, for future patches. > Validate StandardQueryParser with NOT operator with-in parantheses. > --- > > Key: LUCENE-6857 > URL: https://issues.apache.org/jira/browse/LUCENE-6857 > Project: Lucene - Core > Issue Type: Test > Components: core/queryparser >Affects Versions: 5.3 >Reporter: Jigar Shah >Assignee: Dawid Weiss > Fix For: Trunk, 5.4 > > Attachments: LUCENE-6857.patch > > > Provide test case to validate LUCENE-6249, which validates NOT in > parentheses. > e.g: > lottery (NOT ticket) > lottery (-ticket) > lottery AND (NOT ticket) > +lottery +(-ticket) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-6857) Validate StandardQueryParser with NOT operator with-in parentheses.
[ https://issues.apache.org/jira/browse/LUCENE-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jigar Shah updated LUCENE-6857: --- Summary: Validate StandardQueryParser with NOT operator with-in parentheses. (was: Validate StandardQueryParser with NOT operator with-in parantheses.) > Validate StandardQueryParser with NOT operator with-in parentheses. > --- > > Key: LUCENE-6857 > URL: https://issues.apache.org/jira/browse/LUCENE-6857 > Project: Lucene - Core > Issue Type: Test > Components: core/queryparser >Affects Versions: 5.3 >Reporter: Jigar Shah >Assignee: Dawid Weiss > Fix For: Trunk, 5.4 > > Attachments: LUCENE-6857.patch > > > Provide test case to validate LUCENE-6249, which validates NOT in > parentheses. > e.g: > lottery (NOT ticket) > lottery (-ticket) > lottery AND (NOT ticket) > +lottery +(-ticket) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-6857) Validate StandardQueryParser with NOT operator with-in parantheses.
[ https://issues.apache.org/jira/browse/LUCENE-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jigar Shah updated LUCENE-6857: --- Fix Version/s: (was: 5.4) > Validate StandardQueryParser with NOT operator with-in parantheses. > --- > > Key: LUCENE-6857 > URL: https://issues.apache.org/jira/browse/LUCENE-6857 > Project: Lucene - Core > Issue Type: Test > Components: core/queryparser >Affects Versions: 5.3 >Reporter: Jigar Shah > Fix For: Trunk > > > Provide test case to validate LUCENE-6249, which validates NOT in > parentheses. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-6249) StandardQueryParser doesn't support pure negative clauses
[
https://issues.apache.org/jira/browse/LUCENE-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14976959#comment-14976959
]
Jigar Shah commented on LUCENE-6249:
This issue was impacting queries where NOT operator is used within parenthesis
which is fixed now,
Example:
lottery AND (NOT ticket)
Lucene 4.10.3: +lottery +ticket [Incorrect]
Lucene 5.2.0: +lottery +(-ticket) [Correct]
Can we add one testcase having NOT with parenthesis?
> StandardQueryParser doesn't support pure negative clauses
> -
>
> Key: LUCENE-6249
> URL: https://issues.apache.org/jira/browse/LUCENE-6249
> Project: Lucene - Core
> Issue Type: Bug
>Affects Versions: 4.10.3, 5.0
>Reporter: Dawid Weiss
>Assignee: Dawid Weiss
> Fix For: 5.1, Trunk
>
> Attachments: LUCENE-6249.patch
>
>
> At first I thought it's by design but Uwe says it's a bug. SQP emits this:
> {code}
> StandardQueryParser qp = new StandardQueryParser();
> qp.setDefaultOperator(Operator.AND);
>
> System.out.println(qp.parse("summary:foo", "deffld"));
> System.out.println(qp.parse("-summary:foo", "deffld"));
> System.out.println(qp.parse("!summary:foo", "deffld"));
> System.out.println(qp.parse("NOT summary:foo", "deffld"));
> {code}
> {code}
> summary:foo
> summary:foo
> summary:foo
> summary:foo
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (LUCENE-6857) Validate StandardQueryParser with NOT operator with-in parantheses.
Jigar Shah created LUCENE-6857: -- Summary: Validate StandardQueryParser with NOT operator with-in parantheses. Key: LUCENE-6857 URL: https://issues.apache.org/jira/browse/LUCENE-6857 Project: Lucene - Core Issue Type: Test Components: core/queryparser Affects Versions: 5.3 Reporter: Jigar Shah Fix For: Trunk, 5.4 Provide test case to validate LUCENE-6249, which validates NOT in parentheses. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-6857) Validate StandardQueryParser with NOT operator with-in parantheses.
[ https://issues.apache.org/jira/browse/LUCENE-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jigar Shah updated LUCENE-6857: --- Description: Provide test case to validate LUCENE-6249, which validates NOT in parentheses. e.g: lottery (NOT ticket) lottery (-ticket) lottery AND (NOT ticket) +lottery +(-ticket) was:Provide test case to validate LUCENE-6249, which validates NOT in parentheses. > Validate StandardQueryParser with NOT operator with-in parantheses. > --- > > Key: LUCENE-6857 > URL: https://issues.apache.org/jira/browse/LUCENE-6857 > Project: Lucene - Core > Issue Type: Test > Components: core/queryparser >Affects Versions: 5.3 >Reporter: Jigar Shah > Fix For: Trunk > > > Provide test case to validate LUCENE-6249, which validates NOT in > parentheses. > e.g: > lottery (NOT ticket) > lottery (-ticket) > lottery AND (NOT ticket) > +lottery +(-ticket) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-6857) Validate StandardQueryParser with NOT operator with-in parantheses.
[ https://issues.apache.org/jira/browse/LUCENE-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14977113#comment-14977113 ] Jigar Shah commented on LUCENE-6857: Working on it, will provide it soon. > Validate StandardQueryParser with NOT operator with-in parantheses. > --- > > Key: LUCENE-6857 > URL: https://issues.apache.org/jira/browse/LUCENE-6857 > Project: Lucene - Core > Issue Type: Test > Components: core/queryparser >Affects Versions: 5.3 >Reporter: Jigar Shah >Assignee: Dawid Weiss > Fix For: Trunk > > > Provide test case to validate LUCENE-6249, which validates NOT in > parentheses. > e.g: > lottery (NOT ticket) > lottery (-ticket) > lottery AND (NOT ticket) > +lottery +(-ticket) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
