[
https://issues.apache.org/jira/browse/SOLR-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev updated SOLR-6234:
-----------------------------------
Description:
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()}}.
So far
- -it always passes {{multipleValuesPerDocument=true}}-
{{multiVals=true|false}} is introduced
- -it doesn't cover cross core join case,- it covers cross-core join but rather
opportunistically.I just can't find the multicore testcase in Solr test, I
appreciate if you point me on one.
- -I attach standalone plugin project, let me know if somebody interested, I
convert it into the proper Solr codebase patch. Also please mention the
blockers!- done. thanks for your attitude!
- so far it joins string and multivalue string fields (Sorted, SortedSet,
Binary), but not Numerics DVs. follow-up LUCENE-5868
*Caveat:* there is a bug in cross core join, however there is a workaround for
it.
Note: the development of this patch was sponsored by an anonymous contributor
and approved for release under Apache License.
was:
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 score localparam
- supports {{b=100}} param to pass {{Query.setBoost()}}.
So far
- -it always passes {{multipleValuesPerDocument=true}}-
{{multiVals=true|false}} is introduced
- -it doesn't cover cross core join case,- it covers cross-core join but rather
opportunistically.I just can't find the multicore testcase in Solr test, I
appreciate if you point me on one.
- -I attach standalone plugin project, let me know if somebody interested, I
convert it into the proper Solr codebase patch. Also please mention the
blockers!- done. thanks for your attitude!
- so far it joins string and multivalue string fields (Sorted, SortedSet,
Binary), but not Numerics DVs. follow-up LUCENE-5868
*Caveat:* there is a bug in cross core join, however there is a workaround for
it.
Note: the development of this patch was sponsored by an anonymous contributor
and approved for release under Apache License.
> 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: 4.10.3, Trunk
> Reporter: Mikhail Khludnev
> Labels: features, patch, test
> Fix For: 5.0, Trunk
>
> Attachments: SOLR-6234.patch, lucene-join-solr-query-parser-0.0.2.zip
>
>
> 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()}}.
> So far
> - -it always passes {{multipleValuesPerDocument=true}}-
> {{multiVals=true|false}} is introduced
> - -it doesn't cover cross core join case,- it covers cross-core join but
> rather opportunistically.I just can't find the multicore testcase in Solr
> test, I appreciate if you point me on one.
> - -I attach standalone plugin project, let me know if somebody interested, I
> convert it into the proper Solr codebase patch. Also please mention the
> blockers!- done. thanks for your attitude!
> - so far it joins string and multivalue string fields (Sorted, SortedSet,
> Binary), but not Numerics DVs. follow-up LUCENE-5868
> *Caveat:* there is a bug in cross core join, however there is a workaround
> for it.
> 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]
