[jira] [Commented] (SOLR-6234) Scoring modes for query time join
[
https://issues.apache.org/jira/browse/SOLR-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244438#comment-14244438
]
Parnit commented on SOLR-6234:
--
Thanks for the help,but currently I am away from that machine and will not be
access it for 3+ weeks as I will be away.
Perhaps when I am back I could get it to you
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6234) Scoring modes for query time join
[
https://issues.apache.org/jira/browse/SOLR-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244306#comment-14244306
]
Parnit commented on SOLR-6234:
--
I tried all 4 different scoringModes same results. Is it possible that when I
introduced the metric1 column to the mainIndex we are actually scoring on that
non existent field. I'm not sure how solr deals with null/empty column values.
Also the scoreModes do they sort based off of document score or is it something
to do with the field being passed in ie (metric1,metric2)
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (SOLR-6234) Scoring modes for query time join
[
https://issues.apache.org/jira/browse/SOLR-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244207#comment-14244207
]
Parnit edited comment on SOLR-6234 at 12/12/14 2:43 PM:
No luck unfortunately with the sorting, but now I am getting results back with
just metric1 and no need for metric1:*
using the following
testServer/solr/mainIndex/select?q={!scorejoin from=id to=id
fromIndex=subIndex}{!func}metric1&debugQuery=true
{!scorejoin from=id to=id fromIndex=subIndex}{!func}metric1
{!scorejoin from=id to=id fromIndex=subIndex}{!func}metric1
OtherCoreJoinQuery(OtherCoreJoinQuery [fromIndex=subIndex,
fromCoreOpenTime=1418333501496 extends SameCoreJoinQuery
[fromQuery=int(metric1), fromField=id, toField=id, scoreMode=None, boost=1.0]])
OtherCoreJoinQuery [fromIndex=subIndex, fromCoreOpenTime=1418333501496 extends
SameCoreJoinQuery [fromQuery=int(metric1), fromField=id, toField=id,
scoreMode=None, boost=1.0]]
so just to recap metric1,metric2 return the results in the same order
was (Author: parnit):
No luck unfortunately with the sorting, but now I am getting results back with
just metric1 and no need for metric1:*
using the following
testServer/solr/mainIndex/select?q={!scorejoin from=id to=id
fromIndex=subIndex} {!func}metric1&debugQuery=true
{!scorejoin from=id to=id fromIndex=subIndex}{!func}metric1
{!scorejoin from=id to=id fromIndex=subIndex}{!func}metric1
OtherCoreJoinQuery(OtherCoreJoinQuery [fromIndex=subIndex,
fromCoreOpenTime=1418333501496 extends SameCoreJoinQuery
[fromQuery=int(metric1), fromField=id, toField=id, scoreMode=None, boost=1.0]])
OtherCoreJoinQuery [fromIndex=subIndex, fromCoreOpenTime=1418333501496 extends
SameCoreJoinQuery [fromQuery=int(metric1), fromField=id, toField=id,
scoreMode=None, boost=1.0]]
so just to recap metric1,metric2 return the results in the same order
> 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
[jira] [Comment Edited] (SOLR-6234) Scoring modes for query time join
[
https://issues.apache.org/jira/browse/SOLR-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244207#comment-14244207
]
Parnit edited comment on SOLR-6234 at 12/12/14 2:41 PM:
No luck unfortunately with the sorting, but now I am getting results back with
just metric1 and no need for metric1:*
using the following
testServer/solr/mainIndex/select?q={!scorejoin from=id to=id
fromIndex=subIndex} {!func}metric1&debugQuery=true
{!scorejoin from=id to=id fromIndex=subIndex}{!func}metric1
{!scorejoin from=id to=id fromIndex=subIndex}{!func}metric1
OtherCoreJoinQuery(OtherCoreJoinQuery [fromIndex=subIndex,
fromCoreOpenTime=1418333501496 extends SameCoreJoinQuery
[fromQuery=int(metric1), fromField=id, toField=id, scoreMode=None, boost=1.0]])
OtherCoreJoinQuery [fromIndex=subIndex, fromCoreOpenTime=1418333501496 extends
SameCoreJoinQuery [fromQuery=int(metric1), fromField=id, toField=id,
scoreMode=None, boost=1.0]]
so just to recap metric1,metric2 return the results in the same order
was (Author: parnit):
No luck unfortunately with the sorting, but now I am getting results back with
just metric1 and no need for metric1:*
using the following
testServer/solr/mainIndex/select?q={!scorejoin from=id to=id
fromIndex=subIndex} {!func}metric1&debugQuery=true
{!scorejoin from=id to=id fromIndex=subIndex}{!func}view_rank
{!scorejoin from=id to=id fromIndex=subIndex}{!func}view_rank
OtherCoreJoinQuery(OtherCoreJoinQuery [fromIndex=subIndex,
fromCoreOpenTime=1418333501496 extends SameCoreJoinQuery
[fromQuery=int(metric1), fromField=id, toField=id, scoreMode=None, boost=1.0]])
OtherCoreJoinQuery [fromIndex=subIndex, fromCoreOpenTime=1418333501496 extends
SameCoreJoinQuery [fromQuery=int(metric1), fromField=id, toField=id,
scoreMode=None, boost=1.0]]
so just to recap metric1,metric2 return the results in the same order
> 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
[jira] [Commented] (SOLR-6234) Scoring modes for query time join
[
https://issues.apache.org/jira/browse/SOLR-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244207#comment-14244207
]
Parnit commented on SOLR-6234:
--
No luck unfortunately with the sorting, but now I am getting results back with
just metric1 and no need for metric1:*
using the following
testServer/solr/mainIndex/select?q={!scorejoin from=id to=id
fromIndex=subIndex} {!func}metric1&debugQuery=true
{!scorejoin from=id to=id fromIndex=subIndex}{!func}view_rank
{!scorejoin from=id to=id fromIndex=subIndex}{!func}view_rank
OtherCoreJoinQuery(OtherCoreJoinQuery [fromIndex=subIndex,
fromCoreOpenTime=1418333501496 extends SameCoreJoinQuery
[fromQuery=int(metric1), fromField=id, toField=id, scoreMode=None, boost=1.0]])
OtherCoreJoinQuery [fromIndex=subIndex, fromCoreOpenTime=1418333501496 extends
SameCoreJoinQuery [fromQuery=int(metric1), fromField=id, toField=id,
scoreMode=None, boost=1.0]]
so just to recap metric1,metric2 return the results in the same order
> 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
[jira] [Commented] (SOLR-6234) Scoring modes for query time join
[
https://issues.apache.org/jira/browse/SOLR-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243254#comment-14243254
]
Parnit commented on SOLR-6234:
--
ok, trying the function query field I am getting back 0 results.
testserver/solr/mainIndex/select?q={!scorejoin%20from=id to=id
fromIndex=subIndex}view_rank&debugQuery=true
metric1 is also an int type like you stated
Here is the debug
{!scorejoin from=id to=id fromIndex=subIndex}metric1
{!scorejoin from=id to=id fromIndex=subIndex}metric1
OtherCoreJoinQuery(OtherCoreJoinQuery [fromIndex=subIndex,
fromCoreOpenTime=1418333501496 extends SameCoreJoinQuery
[fromQuery=defaultSearch:"(metric1 view) rank", fromField=id , toField=id ,
scoreMode=None, boost=1.0]])
OtherCoreJoinQuery [fromIndex=subIndex, fromCoreOpenTime=1418333501496 extends
SameCoreJoinQuery [fromQuery=defaultSearch:"(metric1 view) rank", fromField=id,
toField=id, scoreMode=None, boost=1.0]]
> 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
[jira] [Commented] (SOLR-6234) Scoring modes for query time join
[
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 metric1metric2
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
[jira] [Commented] (SOLR-6234) Scoring modes for query time join
[
https://issues.apache.org/jira/browse/SOLR-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14242696#comment-14242696
]
Parnit commented on SOLR-6234:
--
I have been getting some strange behaviour using scorejoin
testServer/solr/MainIndex/select?q={!squarejoin from=id to=id
fromIndex=subIndex}metric:*
returns the following error
*undefined field metric*
If I try the same with Solr join I am able to access column metric just fine.
testServer/solr/MainIndex/select?q={!join from=id to=id
fromIndex=subIndex}metric:*
If I try using scorejoin with a column that exists in the mainIndex it seems to
be returning results.
Is this a bug?
> 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
> 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
[jira] [Commented] (SOLR-6234) Scoring modes for query time join
[
https://issues.apache.org/jira/browse/SOLR-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14242536#comment-14242536
]
Parnit commented on SOLR-6234:
--
thanks for the example, what I meant by that was when you supply the "&" you go
back to querying the main index and no longer have access to fields from the
subindex.
Also I'm assuming a negative query will give desc or asc order so I would be
able to support both orders?
> 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
> 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
[jira] [Commented] (SOLR-6234) Scoring modes for query time join
[
https://issues.apache.org/jira/browse/SOLR-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14242505#comment-14242505
]
Parnit commented on SOLR-6234:
--
Hi Mikhail,
I emailed a few mailing lists and you replied to help solve my scenario.
I am slightly confused by how this feature would help also would you be able to
provide sample usage for my scenario?
Here it is in case you had forgotten.
I have my mainIndex which looks something like this.
id description name
1 "description1 ""name1"
2 "description2 ""name2"
I also have a subIndex which looks something like this
id metric
1 4
2 5
What I am trying to do is join the two index's on the id column and have my
results sorted based on a column from the subIndex with a query like the
following.
testServer/solr/MainIndex/select?defType=edismax&q=*&fq={!join from=id to=id
fromIndex=subIndex}id:*&sort=metric desc
desired result
2 "description2 ""name2"
1 "description1 ""name1"
I'm aware that you lose all information from the subIndex the moment the parser
sees "&". What are my options should I want to join two indexes and sort on a
column not present in the main index?
If you or someone else could show me some sample usage I would greatly
appreciate it.
Thanks
> 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
> 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
