[
https://issues.apache.org/jira/browse/SOLR-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243204#comment-14243204
]
Parnit commented on SOLR-6234:
------------------------------
Hi Mikhail, I tried what you are suggesting although it no longer throws an
exception I believe it is not working as intended.
Given the hypothetical situation where I add a new metric to subIndex lets say
metric2
so something like this
id metric1 metric2
1 4 7
2 5 2
testServer/solr/MC_10001_CatalogEntry_en_US/select?q={!scorejoin from=id to=id
fromIndex=subIndex}metric1:*
returns
doc1,
doc2
from the main index
That leads me to believe the scoreJoin is returning results in ascending order.
now the following
testServer/solr/MC_10001_CatalogEntry_en_US/select?q={!scorejoin from=id to=id
fromIndex=subIndex}metric2:*
also returns
doc1,
doc2
from the main index
the metric appears to have no impact on the ordering of the results returned.
Lastly ideal situation is not having to specify metric in both mainIndex and
subIndex as optional as "metric" columns are dynamic columns in subIndex, it
would be extremely inconvenient to add it to the mainIndex as well each time a
new column is added.
Thanks for the continued help.
> 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),
> also
> - 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
