[jira] [Updated] (LUCENE-7206) nest child query explain into ToParentBlockJoinQuery.BlockJoinScorer.explain(int)

[Jeff Evans (JIRA)]

 [ 
https://issues.apache.org/jira/browse/LUCENE-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jeff Evans updated LUCENE-7206:
---
Attachment: LUCENE-7206-test.patch

It seems as though {{org.apache.lucene.search.CheckHits#verifyExplanation}} was 
already verifying that the scores were tying out, so I just added a simple 
assertion that makes sure that explanations are present at all for the child 
doc description line.

> nest child query explain into 
> ToParentBlockJoinQuery.BlockJoinScorer.explain(int)
> -
>
> Key: LUCENE-7206
> URL: https://issues.apache.org/jira/browse/LUCENE-7206
> Project: Lucene - Core
>  Issue Type: Improvement
>  Components: core/query/scoring
>Affects Versions: 6.0
>Reporter: Mikhail Khludnev
>  Labels: newbie, newdev
> Attachments: LUCENE-7206-test.patch, LUCENE-7206.diff
>
>
> Now to parent query match is explained with {{Score based on child doc range 
> from .. to .. }} that's quite useless. 
> It's proposed to nest child query match explanation from the first matching 
> child document into parent explain. 
> WDYT?



--
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-2916) QueryParser treatment of unescaped internal operators

[Jeff Evans (JIRA)]

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

Jeff Evans commented on LUCENE-2916:


Regarding the first paragraph, it's easy enough to accomplish this by just 
adding another disjunction to the {{#_TERM_CHAR}} expansion - {{| "!"}})

I'm curious, though, what characters should be consumed as part of a term?  
Currently, {{-}} and {{+}} are included.  Is there some reason these two are 
explicitly included, while others are not?  It's easy enough to add {{!}}, or 
others, but it would be good to understand if there is a historical basis for 
what's here.

> QueryParser treatment of unescaped internal operators
> -
>
> Key: LUCENE-2916
> URL: https://issues.apache.org/jira/browse/LUCENE-2916
> Project: Lucene - Core
>  Issue Type: Bug
>  Components: core/queryparser
>Reporter: Yonik Seeley
>Priority: Minor
>  Labels: newdev
> Attachments: LUCENE-2916-unescaped-negative.patch
>
>
> myfield:foo-bar and myfield:foo+bar are treated as myfield:"foo-bar" and 
> myfield:"foo+bar"
> but myfield:foo!bar is treated as myfield:foo -defaultfield:bar
> Somewhat related, temp:70 works fine, but temp:-10 throws an exception.  Many 
> people hit this and figure out how to work around it relatively quickly, but 
> just fixing the grammar to accept it might be better?



--
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-2916) QueryParser treatment of unescaped internal operators

[Jeff Evans (JIRA)]

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

Jeff Evans commented on LUCENE-2916:


I took a stab at the second paragraph in the description.  This is my first 
contribution, so any feedback is appreciated.  I first modified QueryParser.jj, 
then ran the javacc-QueryParser target to regenerate the parser.  I added a 
method to TestQueryParser to cover the change, and ensured all the tests under 
lucene/queryparser passed.

> QueryParser treatment of unescaped internal operators
> -
>
> Key: LUCENE-2916
> URL: https://issues.apache.org/jira/browse/LUCENE-2916
> Project: Lucene - Core
>  Issue Type: Bug
>  Components: core/queryparser
>Reporter: Yonik Seeley
>Priority: Minor
>  Labels: newdev
> Attachments: LUCENE-2916-unescaped-negative.patch
>
>
> myfield:foo-bar and myfield:foo+bar are treated as myfield:"foo-bar" and 
> myfield:"foo+bar"
> but myfield:foo!bar is treated as myfield:foo -defaultfield:bar
> Somewhat related, temp:70 works fine, but temp:-10 throws an exception.  Many 
> people hit this and figure out how to work around it relatively quickly, but 
> just fixing the grammar to accept it might be better?



--
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-2916) QueryParser treatment of unescaped internal operators

[Jeff Evans (JIRA)]

 [ 
https://issues.apache.org/jira/browse/LUCENE-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jeff Evans updated LUCENE-2916:
---
Attachment: LUCENE-2916-unescaped-negative.patch

> QueryParser treatment of unescaped internal operators
> -
>
> Key: LUCENE-2916
> URL: https://issues.apache.org/jira/browse/LUCENE-2916
> Project: Lucene - Core
>  Issue Type: Bug
>  Components: core/queryparser
>Reporter: Yonik Seeley
>Priority: Minor
>  Labels: newdev
> Attachments: LUCENE-2916-unescaped-negative.patch
>
>
> myfield:foo-bar and myfield:foo+bar are treated as myfield:"foo-bar" and 
> myfield:"foo+bar"
> but myfield:foo!bar is treated as myfield:foo -defaultfield:bar
> Somewhat related, temp:70 works fine, but temp:-10 throws an exception.  Many 
> people hit this and figure out how to work around it relatively quickly, but 
> just fixing the grammar to accept it might be better?



--
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

Minor typo in javadocs for join package?

[Jeff Evans]

Hi,

In the join package summary page
,
the first sentence under "Index-time joins" starts with "The
index-time joining support joins while searching."  I believe it
should say "The index-time joining support joins while indexing,"
correct?  Just trying to verify my understanding; thanks.

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org