[
https://issues.apache.org/jira/browse/SOLR-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14622375#comment-14622375
]
Yonik Seeley edited comment on SOLR-6234 at 7/10/15 2:31 PM:
-------------------------------------------------------------
Related: my last few commits on heliosearch related to refactoring Solr's Join
stuff to accommodate multiple implementations:
https://github.com/Heliosearch/heliosearch/commits/helio_4_10
In the short term though, it may be easiest for JoinQParser to detect
"score=..." and delegate to this new qparser?
I haven't had a chance to look at this patch... from an API perspective, can
someone explain what the "multiVals=true|false" parameter is supposed to do?
edit: Oh, and this: "supports b=100 param to pass Query.setBoost()." - what is
the effect of this? (exactly what query is the boost applied to and why aren't
we using standard boosting mechanisms?)
was (Author: [email protected]):
Related: my last few commits on heliosearch related to refactoring Solr's Join
stuff to accommodate multiple implementations:
https://github.com/Heliosearch/heliosearch/commits/helio_4_10
In the short term though, it may be easiest for JoinQParser to detect
"score=..." and delegate to this new qparser?
I haven't had a chance to look at this patch... from an API perspective, can
someone explain what the "multiVals=true|false" parameter is supposed to do?
> Scoring modes for query time join
> ----------------------------------
>
> Key: SOLR-6234
> URL: https://issues.apache.org/jira/browse/SOLR-6234
> Project: Solr
> Issue Type: New Feature
> Components: query parsers
> Affects Versions: 5.3
> Reporter: Mikhail Khludnev
> Assignee: Timothy Potter
> Labels: features, patch, test
> Fix For: 5.3
>
> Attachments: SOLR-6234.patch, SOLR-6234.patch, SOLR-6234.patch,
> otherHandler.patch
>
>
> it adds {{scorejoin}} query parser which calls Lucene's JoinUtil underneath.
> It supports:
> - {{score=none|avg|max|total}} local param (passed as ScoreMode to JoinUtil)
> - {{score=none}} is *default*, eg if you *omit* this localparam
> - supports {{b=100}} param to pass {{Query.setBoost()}}.
> - {{multiVals=true|false}} is introduced
> - there is a test coverage for cross core join case.
> - so far it joins string and multivalue string fields (Sorted, SortedSet,
> Binary), but not Numerics DVs. follow-up LUCENE-5868
> -there was a bug in cross core join, however there is a workaround for it-
> it's fixed in Dec'14 patch.
> Note: the development of this patch was sponsored by an anonymous contributor
> and approved for release under Apache License.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
