[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-tabpanelfocusedCommentId=14645758#comment-14645758
]
Uwe Schindler edited comment on SOLR-6234 at 7/29/15 9:15 AM:
--
Seems to pass now:
https://builds.apache.org/job/Lucene-Solr-SmokeRelease-trunk/245/console
The problem was just that smoke tester does the good test to build the Solr
javadocs in isolation. The default builds don't trigger this, because they
only check the javadocs as a whole.
was (Author: thetaphi):
Seems to pass now. The problem was just that smoke tester does the good test to
build the Solr javadocs in isolation. The default builds don't trigger this,
because they only check the javadocs as a whole.
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: Mikhail Khludnev
Labels: features, patch, test
Fix For: 5.3
Attachments: SOLR-6234-javadocsfix.patch, SOLR-6234.patch,
SOLR-6234.patch, SOLR-6234.patch, SOLR-6234.patch, SOLR-6234.patch,
SOLR-6234.patch, SOLR-6234.patch, otherHandler.patch
it adds ability to call Lucene's JoinUtil by specifying local param, ie
\{!join score=...} It supports:
- {{score=none|avg|max|total}} local param (passed as ScoreMode to JoinUtil)
- -supports {{b=100}} param to pass {{Query.setBoost()}}- postponed till
SOLR-7814.
- -{{multiVals=true|false}} is introduced- YAGNI, let me know otherwise.
- 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
--
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-tabpanelfocusedCommentId=14645573#comment-14645573
]
Uwe Schindler edited comment on SOLR-6234 at 7/29/15 6:58 AM:
--
The problem still occurs in nightly's smoker builds (both 5.x and trunk). Was
this committed?
{noformat}
[smoker] Verify...
[smoker]
[smoker]
file:///x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-5.x/lucene/build/smokeTestRelease/tmp/unpack/solr-5.3.0/solr/build/docs/solr-core/org/apache/solr/search/join/ScoreJoinQParserPlugin.html
[smoker] BROKEN LINK:
file:///x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-5.x/lucene/build/smokeTestRelease/tmp/unpack/solr-5.3.0/lucene/build/docs/core/org/apache/lucene/search/join.ScoreMode.html
[smoker] Traceback (most recent call last):
[smoker] File
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-5.x/dev-tools/scripts/smokeTestRelease.py,
line 1487, in module
[smoker] main()
[smoker] File
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-5.x/dev-tools/scripts/smokeTestRelease.py,
line 1432, in main
[smoker] smokeTest(c.java, c.url, c.revision, c.version, c.tmp_dir,
c.is_signed, ' '.join(c.test_args))
[smoker] File
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-5.x/dev-tools/scripts/smokeTestRelease.py,
line 1477, in smokeTest
[smoker] unpackAndVerify(java, 'solr', tmpDir, 'solr-%s-src.tgz' %
version, svnRevision, version, testArgs, baseURL)
[smoker] File
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-5.x/dev-tools/scripts/smokeTestRelease.py,
line 583, in unpackAndVerify
[smoker] verifyUnpacked(java, project, artifact, unpackPath,
svnRevision, version, testArgs, tmpDir, baseURL)
[smoker] File
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-5.x/dev-tools/scripts/smokeTestRelease.py,
line 702, in verifyUnpacked
[smoker] checkJavadocpathFull('%s/solr/build/docs' % unpackPath, False)
[smoker] File
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-5.x/dev-tools/scripts/smokeTestRelease.py,
line 918, in checkJavadocpathFull
[smoker] raise RuntimeError('broken javadocs links found!')
[smoker] RuntimeError: broken javadocs links found!
{noformat}
The link is definitely wrong as it goes to core module not join.
was (Author: thetaphi):
The problem still occurs in nightly's smoker builds (both 5.x and trunk). Was
this committed?
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: Mikhail Khludnev
Labels: features, patch, test
Fix For: 5.3
Attachments: SOLR-6234.patch, SOLR-6234.patch, SOLR-6234.patch,
SOLR-6234.patch, SOLR-6234.patch, SOLR-6234.patch, SOLR-6234.patch,
otherHandler.patch
it adds ability to call Lucene's JoinUtil by specifying local param, ie
\{!join score=...} It supports:
- {{score=none|avg|max|total}} local param (passed as ScoreMode to JoinUtil)
- -supports {{b=100}} param to pass {{Query.setBoost()}}- postponed till
SOLR-7814.
- -{{multiVals=true|false}} is introduced- YAGNI, let me know otherwise.
- 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
--
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-tabpanelfocusedCommentId=14622426#comment-14622426
]
Mikhail Khludnev edited comment on SOLR-6234 at 7/10/15 3:17 PM:
-
bq. it may be easiest for JoinQParser to detect score=... and delegate
+1
bq. the multiVals=true|false parameter is supposed to do?
it's just exposing JoinUtil.createJoinQuery() functionality, it implies that
fromField is multivalue SortedSetDV and these values are looped.
another interesting feature request which I've heard is to treat toField
multivalue and hence accumulate several from-side scores in to-side values.
it's not in the patch, and should be done in JoinUtil first.
bq. exactly what query is the boost applied to
this parser calls JoinUtil.createJoinQuery() and then calls setBoost() on its'
result.
bq. why aren't we using standard boosting mechanisms?
I might be unaware of 'standard boosting mechanisms' I only aware about
\{!boost but people ask for more sugar.
was (Author: mkhludnev):
bq. it may be easiest for JoinQParser to detect score=... and delegate
+1
bq. the multiVals=true|false parameter is supposed to do?
it's just exposing JoinUtil.createJoinQuery() functionality, it implies that
fromField is multivalue SortedSetDV and these values are looped.
bq. exactly what query is the boost applied to
this parser calls JoinUtil.createJoinQuery() and then calls setBoost() on its'
result.
bq. why aren't we using standard boosting mechanisms?
I might be unaware of 'standard boosting mechanisms' I only aware about
\{!boost but people ask for more sugar.
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: 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-tabpanelfocusedCommentId=14622449#comment-14622449
]
Ryan Josal edited comment on SOLR-6234 at 7/10/15 3:22 PM:
---
It seems like the parser can find out if it's multivalued for itself by
checking the otherCore's Schema.
I think multivalued to field on the current core should be a separate ticket
since it is not a feature of the qparser, it's an improvement to JoinUtil. I
can have a patch for that later; I have it working.
was (Author: rjosal):
It seems like the parser can find out if it's multivalued for itself by
checking the otherCore's Schema.
I think multivalued to field should be a separate ticket since it is not a
feature of the qparser
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: 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-tabpanelfocusedCommentId=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: ysee...@gmail.com):
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: 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-tabpanelfocusedCommentId=14619521#comment-14619521
]
Ryan Josal edited comment on SOLR-6234 at 7/8/15 10:47 PM:
---
I've attached otherHandler.patch, which is a patch on top of the existing
ScoreJoinQParserPlugin.java from the Dec 14 patch, which shows changes to add a
feature where the user can supply handler=/select (for example) in localparams,
to apply the config from the handler in the other core. You'll notice that the
request is built from localParams instead of params so that whatever your
current core params are don't override the other core configured params. If
this breaks something, it could be changed to only do that when the handler
localParam is present. This patch is quick and dirty because it uses
reflection to get the defaults,appends,invariants config from the
BaseRequestHandler class. Really, the access level of those variables should
change, or the method should be moved there.
Personally I'm using this feature to join my deals core with my products core
as the othercore, and I wanted it to do a regular search against the products
core. This approach could actually be used in the \!join qparser too. If this
patch is useful for somebody, great!
was (Author: rjosal):
I've attached otherHandler.patch, which is a patch on top of the existing
ScoreJoinQParserPlugin.java from the Dec 14 patch, which shows changes to add a
feature where the user can supply handler=/select (for example) in localparams,
to apply the config from the handler in the other core. You'll notice that the
request is built from localParams instead of params so that whatever your
current core params are don't override the other core configured params. If
this breaks something, it could be changed to only do that when the handler
localParam is present. This patch is quick and dirty because it uses
reflection to get the defaults,appends,invariants config from the
BaseRequestHandler class. Really, the access level of those variables should
change, or the method should be moved there.
Personally I'm using this feature to join my deals core with my products core
as the othercore, and I wanted it to do a regular search against the products
core. This approach could actually be used in the !join qparser too. If this
patch is useful for somebody, great!
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, 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: 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-tabpanelfocusedCommentId=14583437#comment-14583437
]
Ryan Josal edited comment on SOLR-6234 at 6/12/15 2:15 PM:
---
[~neerajlajpal] Solr parses the value of q with a single parser, which will be
whatever your defType is. In order to do something like that you can use
nested queries:
{noformat}
important_category:322^4 _query_:{!scorejoin from=_root_ to=id score=avg
multiVals=false v=$jq}jq=(brandid:1398^4 OR brandid:237^4.5)
{noformat}
was (Author: rjosal):
[~neerajlajpal] Solr parses the value of q with a single parser, which will be
whatever your defType is. In order to do something like that you can use
nested queries:
important_category:322^4 _query_:{!scorejoin from=_root_ to=id score=avg
multiVals=false v=$jq}jq=(brandid:1398^4 OR brandid:237^4.5)
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
Labels: features, patch, test
Fix For: 5.3
Attachments: SOLR-6234.patch, SOLR-6234.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: 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-tabpanelfocusedCommentId=14583437#comment-14583437
]
Ryan Josal edited comment on SOLR-6234 at 6/12/15 2:13 PM:
---
[~neerajlajpal] Solr parses the value of q with a single parser, which will be
whatever your defType is. In order to do something like that you can use
nested queries:
important_category:322^4 _query_:{!scorejoin from=_root_ to=id score=avg
multiVals=false v=$jq}jq=(brandid:1398^4 OR brandid:237^4.5)
was (Author: rjosal):
[~neerajlajpal] Solr parses the value of q with a single parser, which will be
whatever your defType is. In order to do something like that you can use
nested queries:
important_category:322^4 _query_:{!scorejoin from=_root_ to=id score=avg
multiVals=false}
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
Labels: features, patch, test
Fix For: 5.3
Attachments: SOLR-6234.patch, SOLR-6234.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: 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-tabpanelfocusedCommentId=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}metric1debugQuery=true
lst name=debug
str name=rawquerystring
{!scorejoin from=id to=id fromIndex=subIndex}{!func}metric1
/str
str name=querystring
{!scorejoin from=id to=id fromIndex=subIndex}{!func}metric1
/str
str name=parsedquery
OtherCoreJoinQuery(OtherCoreJoinQuery [fromIndex=subIndex,
fromCoreOpenTime=1418333501496 extends SameCoreJoinQuery
[fromQuery=int(metric1), fromField=id, toField=id, scoreMode=None, boost=1.0]])
/str
str name=parsedquery_toString
OtherCoreJoinQuery [fromIndex=subIndex, fromCoreOpenTime=1418333501496 extends
SameCoreJoinQuery [fromQuery=int(metric1), fromField=id, toField=id,
scoreMode=None, boost=1.0]]
/str
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}metric1debugQuery=true
lst name=debug
str name=rawquerystring
{!scorejoin from=id to=id fromIndex=subIndex}{!func}view_rank
/str
str name=querystring
{!scorejoin from=id to=id fromIndex=subIndex}{!func}view_rank
/str
str name=parsedquery
OtherCoreJoinQuery(OtherCoreJoinQuery [fromIndex=subIndex,
fromCoreOpenTime=1418333501496 extends SameCoreJoinQuery
[fromQuery=int(metric1), fromField=id, toField=id, scoreMode=None, boost=1.0]])
/str
str name=parsedquery_toString
OtherCoreJoinQuery [fromIndex=subIndex, fromCoreOpenTime=1418333501496 extends
SameCoreJoinQuery [fromQuery=int(metric1), fromField=id, toField=id,
scoreMode=None, boost=1.0]]
/str
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-tabpanelfocusedCommentId=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}metric1debugQuery=true
lst name=debug
str name=rawquerystring
{!scorejoin from=id to=id fromIndex=subIndex}{!func}metric1
/str
str name=querystring
{!scorejoin from=id to=id fromIndex=subIndex}{!func}metric1
/str
str name=parsedquery
OtherCoreJoinQuery(OtherCoreJoinQuery [fromIndex=subIndex,
fromCoreOpenTime=1418333501496 extends SameCoreJoinQuery
[fromQuery=int(metric1), fromField=id, toField=id, scoreMode=None, boost=1.0]])
/str
str name=parsedquery_toString
OtherCoreJoinQuery [fromIndex=subIndex, fromCoreOpenTime=1418333501496 extends
SameCoreJoinQuery [fromQuery=int(metric1), fromField=id, toField=id,
scoreMode=None, boost=1.0]]
/str
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}metric1debugQuery=true
lst name=debug
str name=rawquerystring
{!scorejoin from=id to=id fromIndex=subIndex}{!func}metric1
/str
str name=querystring
{!scorejoin from=id to=id fromIndex=subIndex}{!func}metric1
/str
str name=parsedquery
OtherCoreJoinQuery(OtherCoreJoinQuery [fromIndex=subIndex,
fromCoreOpenTime=1418333501496 extends SameCoreJoinQuery
[fromQuery=int(metric1), fromField=id, toField=id, scoreMode=None, boost=1.0]])
/str
str name=parsedquery_toString
OtherCoreJoinQuery [fromIndex=subIndex, fromCoreOpenTime=1418333501496 extends
SameCoreJoinQuery [fromQuery=int(metric1), fromField=id, toField=id,
scoreMode=None, boost=1.0]]
/str
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
