[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-tabpanelfocusedCommentId=14650527#comment-14650527
]
ASF subversion and git services commented on SOLR-6234:
---
Commit 1693760 from m...@apache.org in branch 'dev/trunk'
[ https://svn.apache.org/r1693760 ]
SOLR-6234: moving lines in CHANGES.txt
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-trunk-CHANGES-fix.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] [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-tabpanelfocusedCommentId=14649489#comment-14649489
]
Cassandra Targett commented on SOLR-6234:
-
[~mkhludnev]. First, thanks so much for proactively updating the Ref Guide with
your changes.
I hope you don't mind too much, but I modified your text in a few ways:
* The online version of the Ref Guide is always for the upcoming release of
Solr, and as such we don't spend a lot of time describing how features used to
work. While I understand that causes some confusion from time-to-time, a major
problem with the old Solr Wiki was the attempt to maintain documentation for
older versions of Solr along with the changes along the way. Personally, I find
no harm mentioning when a feature was introduced, but at that point our
convention is to remove documentation for the old behavior (unless, of course,
the section is describing how to migrate to the new behavior).
* With this general guideline, on the Uploading Data with Index Handlers page I
flipped the emphasis to note the need to use the score parameter when deleting
with the Join QP to avoid the error, and omitted the reference to 5.3 because
the guide is for 5.3 already, and the section we're pointing to says the param
was introduced in 5.3.
* I re-worded the text a bit to provide more context for a less-expert user.
* Standardized phrasings - i.e., plain Solr is usually referred to as
standalone Solr.
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] [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-tabpanelfocusedCommentId=14649878#comment-14649878
]
Mikhail Khludnev commented on SOLR-6234:
Impl notes:
* toString() is a little bit odd, it looks like
{code}
debug: {
rawquerystring: {!join from=id to=manu_id_s score=max
fromIndex=products}inc,
querystring: {!join from=id to=manu_id_s score=max
fromIndex=products}inc,
parsedquery: OtherCoreJoinQuery(OtherCoreJoinQuery [fromIndex=products,
fromCoreOpenTime=1438087133575 extends SameCoreJoinQuery [fromQuery=text:inc,
fromField=id, toField=manu_id_s, scoreMode=Max]]),
parsedquery_toString: OtherCoreJoinQuery [fromIndex=products,
fromCoreOpenTime=1438087133575 extends SameCoreJoinQuery [fromQuery=text:inc,
fromField=id, toField=manu_id_s, scoreMode=Max]],
explain: {
{code}
Let me know if you need to change it.
* for cross core join: when you commit into {{fromIndex}} query cache entry
equality is determined by coreOpenTime() which is obtained from
{{System.currentTimeMillis()}} it might cause some issues on edge
cases/plarforms (that's why it wasn't covered with test), but this approach was
inherited from \{!join}. Raise an issue if it's significant 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: 5.3
Reporter: Mikhail Khludnev
Assignee: Mikhail Khludnev
Labels: features, patch, test
Fix For: 5.3
Attachments: SOLR-6234-javadocsfix.patch,
SOLR-6234-trunk-CHANGES-fix.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] [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-tabpanelfocusedCommentId=14648326#comment-14648326
]
Mikhail Khludnev commented on SOLR-6234:
[~jpountz][~thetaphi] thanks for your help!
[~thelabdude],[~ctargett], I hit cwiki, would you mind to check:
*
https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=32604257selectedPageVersions=50selectedPageVersions=49
*
https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=32604277selectedPageVersions=71selectedPageVersions=70
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] [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-tabpanelfocusedCommentId=14646715#comment-14646715
]
Uwe Schindler commented on SOLR-6234:
-
bq. run before commit beside of test and precommit? Is prerelease worth to run?
Precommit is fine. nightly-smoke is only needed for real structural changes. In
fact, the Javadocs changes were structural :-) So whenever you touch the
build.xmls it may be good to run nightly-smoke, but in most cases I just wait
for Jenkins to fail :-)
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] [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-tabpanelfocusedCommentId=14646744#comment-14646744
]
ASF subversion and git services commented on SOLR-6234:
---
Commit 1693343 from m...@apache.org in branch 'dev/branches/branch_5x'
[ https://svn.apache.org/r1693343 ]
SOLR-6234: move ScoreJoinQParserPlugin.java into oas.search.join
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] [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-tabpanelfocusedCommentId=14646711#comment-14646711
]
Uwe Schindler commented on SOLR-6234:
-
No worries! This would have happened with me, too. This is just horrible
dependency stuff and crazy javadocs linter.
See it like that: It wook me half an hour to find out what's going on. After
reading Smoke Tester source and seeing that it does ant clean and then ant
javadocs in Solr only, it was clear to me what's wrong :-) - Solr was not
building all required Lucene Javadocs before creating their own!
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] [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-tabpanelfocusedCommentId=14646691#comment-14646691
]
Mikhail Khludnev commented on SOLR-6234:
{{precommit}} and {{nightly-smoke}} passed. Committing
{code}
D solr/core/src/java/org/apache/solr/search/ScoreJoinQParserPlugin.java
moved to
solr/core/src/java/org/apache/solr/search/join/ScoreJoinQParserPlugin.java
A +
solr/core/src/java/org/apache/solr/search/join/ScoreJoinQParserPlugin.java
moved from
solr/core/src/java/org/apache/solr/search/ScoreJoinQParserPlugin.java
{code}
into {{^/lucene/dev/branches/branch_5x}}
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] [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-tabpanelfocusedCommentId=14645644#comment-14645644
]
Uwe Schindler commented on SOLR-6234:
-
Found the problem: Solr's common-build misses to build Join's Javadocs:
{code:xml}
!-- dependency to ensure all lucene javadocs are present --
target name=lucene-javadocs
depends=javadocs-lucene-core,javadocs-analyzers-common,javadocs-analyzers-icu,javadocs-analyzers-kuromoji,javadocs-analyzers-phonetic,javadocs-analyzers-smartcn,javadocs-analyzers-morfologik,javadocs-analyzers-stempel,javadocs-analyzers-uima,javadocs-backward-codecs,javadocs-codecs,javadocs-expressions,javadocs-suggest,javadocs-grouping,javadocs-queries,javadocs-queryparser,javadocs-highlighter,javadocs-memory,javadocs-misc,javadocs-spatial,javadocs-test-framework/
{code}
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] [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-tabpanelfocusedCommentId=14645758#comment-14645758
]
Uwe Schindler commented on SOLR-6234:
-
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] [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-tabpanelfocusedCommentId=14645604#comment-14645604
]
Adrien Grand commented on SOLR-6234:
It might be related to the fact that ScoreJoinQParserPlugin was put in a
different package in 5.x compared to trunk? (my IDE complains that the package
declaration does not match the folder the class is in)
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] [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-tabpanelfocusedCommentId=14645640#comment-14645640
]
Uwe Schindler commented on SOLR-6234:
-
This happens under the following condition:
- The release TAR file has correct javadocs, all links will be correct for the
occifial release (they user http://lucene.apache.org/core/5_3_0/join/...)
- Smoke tester fails when it unpacks the SRC-TGZ file (solr-5.3.0-src.tgz) and
then runs ant documentation on it. In this case, the cross project links are
static filesystem links (as seen above). Unfortunately, under this condition it
seems to choose the wrong package. Maybe its a problem of order? I have the
feeling we may have the same package in core and join that leads to the fact
that it uses wrong module? It may also caused by not fully built Lucene
javadocs?
Did you try the following;
- ant clean
- cd solr
- ant javadocs
(to isolate the whole thing out of full build). To me it looks like smoketester
does not generate the full Lucene Javadocs, so it fails (see
https://builds.apache.org/job/Lucene-Solr-SmokeRelease-5.x/ws/lucene/build/smokeTestRelease/tmp/unpack/solr-5.3.0/javadocs.log).
So this could be a dependency problem. When solr builds javadocs it missies to
trigger building of Lucenes Join.
Unfortunately I cannot take care (vacation from today) and the release of 5.3.0
is close, so I would suggest to remove the cross module links for now and open
separate issue to fix this.
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] [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-tabpanelfocusedCommentId=14645673#comment-14645673
]
ASF subversion and git services commented on SOLR-6234:
---
Commit 1693197 from [~thetaphi] in branch 'dev/trunk'
[ https://svn.apache.org/r1693197 ]
SOLR-6234: Fix Javadocs dependency to join module
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] [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-tabpanelfocusedCommentId=14645700#comment-14645700
]
Adrien Grand commented on SOLR-6234:
Thanks Uwe!
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] [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-tabpanelfocusedCommentId=14645763#comment-14645763
]
Uwe Schindler commented on SOLR-6234:
-
...out for vacation :-)
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] [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-tabpanelfocusedCommentId=14645677#comment-14645677
]
Uwe Schindler commented on SOLR-6234:
-
Fixed (hopefully) - waiting for next nightly run. If it still does not work, I
hopy you can fix it based on my patch.
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] [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-tabpanelfocusedCommentId=14645675#comment-14645675
]
ASF subversion and git services commented on SOLR-6234:
---
Commit 1693198 from [~thetaphi] in branch 'dev/branches/branch_5x'
[ https://svn.apache.org/r1693198 ]
Merged revision(s) 1693197 from lucene/dev/trunk:
SOLR-6234: Fix Javadocs dependency to join module
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] [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-tabpanelfocusedCommentId=14645573#comment-14645573
]
Uwe Schindler commented on SOLR-6234:
-
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] [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-tabpanelfocusedCommentId=14645879#comment-14645879
]
Mikhail Khludnev commented on SOLR-6234:
[~thetaphi], danke schön! Sorry, guys. I knew I broke something by my first
commit.
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] [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-tabpanelfocusedCommentId=14645934#comment-14645934
]
Adrien Grand commented on SOLR-6234:
Mikhail, was it intentional to move ScoreJoinQParserPlugin to a different
package when backporting? It's in oas.search in 5x and oas.search.join in trunk.
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] [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-tabpanelfocusedCommentId=14645968#comment-14645968
]
Mikhail Khludnev commented on SOLR-6234:
oh no. to clarify: I committed it to trunk first, then shoot my leg by old svn
while merge into branch_5x.
I prefer to move ScoreJoinQParserPlugin into oas.search.join at branch_5x if
there is no objection. But would you tell me what I need to run before commit
beside of test and precommit? Is prerelease worth to run?
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] [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-tabpanelfocusedCommentId=14644366#comment-14644366
]
ASF subversion and git services commented on SOLR-6234:
---
Commit 1693092 from m...@apache.org in branch 'dev/trunk'
[ https://svn.apache.org/r1693092 ]
SOLR-6234: Scoring for query time join
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,
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] [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-tabpanelfocusedCommentId=14644466#comment-14644466
]
ASF subversion and git services commented on SOLR-6234:
---
Commit 1693101 from m...@apache.org in branch 'dev/branches/branch_5x'
[ https://svn.apache.org/r1693101 ]
SOLR-6234: Scoring for query time join
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,
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] [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-tabpanelfocusedCommentId=14644577#comment-14644577
]
Mikhail Khludnev commented on SOLR-6234:
the latest patch adds a tag into solr/common-build.xml which fixes it. I did
run precommit for sure a plenty of times. fwiw build passed
https://builds.apache.org/job/Lucene-Solr-Tests-trunk-Java8/245/
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,
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] [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-tabpanelfocusedCommentId=14644515#comment-14644515
]
Timothy Potter commented on SOLR-6234:
--
Looks like some problems with the Javadoc still ... I'm getting this from
running the smoke tester. [~mkhludnev] did you run precommit?
{code}
[smoker]
file:///Users/timpotter/dev/lw/projects/solr_trunk_co/lucene/build/smokeTestRelease/tmp/unpack/solr-6.0.0/solr/build/docs/solr-core/org/apache/solr/search/join/ScoreJoinQParserPlugin.html
[smoker] BROKEN LINK:
file:///Users/timpotter/dev/lw/projects/solr_trunk_co/lucene/build/smokeTestRelease/tmp/unpack/solr-6.0.0/lucene/build/docs/core/org/apache/lucene/search/join.ScoreMode.html
[smoker] Traceback (most recent call last):
[smoker] File
/Users/timpotter/dev/lw/projects/solr_trunk_co/dev-tools/scripts/smokeTestRelease.py,
line 1463, in module
[smoker] main()
[smoker] File
/Users/timpotter/dev/lw/projects/solr_trunk_co/dev-tools/scripts/smokeTestRelease.py,
line 1408, in main
[smoker] smokeTest(c.java, c.url, c.revision, c.version, c.tmp_dir,
c.is_signed, ' '.join(c.test_args))
[smoker] File
/Users/timpotter/dev/lw/projects/solr_trunk_co/dev-tools/scripts/smokeTestRelease.py,
line 1453, in smokeTest
[smoker] unpackAndVerify(java, 'solr', tmpDir, 'solr-%s-src.tgz' %
version, svnRevision, version, testArgs, baseURL)
[smoker] File
/Users/timpotter/dev/lw/projects/solr_trunk_co/dev-tools/scripts/smokeTestRelease.py,
line 592, in unpackAndVerify
[smoker] verifyUnpacked(java, project, artifact, unpackPath,
svnRevision, version, testArgs, tmpDir, baseURL)
[smoker] File
/Users/timpotter/dev/lw/projects/solr_trunk_co/dev-tools/scripts/smokeTestRelease.py,
line 701, in verifyUnpacked
[smoker] checkJavadocpathFull('%s/solr/build/docs' % unpackPath, False)
[smoker] File
/Users/timpotter/dev/lw/projects/solr_trunk_co/dev-tools/scripts/smokeTestRelease.py,
line 893, in checkJavadocpathFull
[smoker] raise RuntimeError('broken javadocs links found!')
[smoker] RuntimeError: broken javadocs links found!
{code}
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,
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] [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-tabpanelfocusedCommentId=14633843#comment-14633843
]
Timothy Potter commented on SOLR-6234:
--
looks good [~mkhludnev] +1 to commit. Please be sure to add documentation for
this new feature to the refguide. I'll add a separate unit test that uses this
feature to verify SOLR-6357 once this is 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: Timothy Potter
Labels: features, patch, test
Fix For: 5.3
Attachments: 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] [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-tabpanelfocusedCommentId=14625777#comment-14625777
]
Mikhail Khludnev commented on SOLR-6234:
I can, if you wish, as well as handle other suggestions, but only in the end of
this week.
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] [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-tabpanelfocusedCommentId=14624923#comment-14624923
]
Timothy Potter commented on SOLR-6234:
--
[~mkhludnev] are you going to update the latest patch I posted to have
bq. JoinQParser to detect score=... and delegate
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] [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-tabpanelfocusedCommentId=14621979#comment-14621979
]
Mikhail Khludnev commented on SOLR-6234:
[~thelabdude] I like SOLR-4905 much. If it's possible I prefer to create a
patch right after SOLR-6234 is committed, just prefer to work on smaller units.
Let me know if you see it as a blocker, and I'll dig into SOLR-4905 (I still
unaware of its' details).
[~dsmiley] I'm neutral about this - I agree that it would be convenient, but
have a concern, nevermind.
Here is another off-top-just-a-thought: since Lucene has query/filter cache
\{!join} algorithm can be migrated on intrinsic Lucene's IndexSearcher.
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] [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-tabpanelfocusedCommentId=14622428#comment-14622428
]
Mikhail Khludnev commented on SOLR-6234:
I think it's not so important.
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] [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-tabpanelfocusedCommentId=14622426#comment-14622426
]
Mikhail Khludnev commented on SOLR-6234:
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] [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-tabpanelfocusedCommentId=14622461#comment-14622461
]
Yonik Seeley commented on SOLR-6234:
bq. it's just exposing JoinUtil.createJoinQuery() functionality, it implies
that fromField is multivalue SortedSetDV
That's a Java API that can change from release-to-release. Our HTTP APIs
should stand alone and not be defined in terms of implementation details.
In this specific case, we should either know or be able to figure that out,
right? The user shouldn't have to specify.
bq. this parser calls JoinUtil.createJoinQuery() and then calls setBoost() on
its' result.
Seems like that should be a separate issue (boosting the current query from
within local params for that query). If it's a good idea, it should be done in
a generic way for all queries / qparsers.
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] [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-tabpanelfocusedCommentId=14622363#comment-14622363
]
Timothy Potter commented on SOLR-6234:
--
Thanks [~ysee...@gmail.com], makes sense.
[~mkhludnev] I didn't quite grok your last comment:
bq. I'm neutral about this - I agree that it would be convenient, but have a
concern, nevermind. Here is another off-top-just-a-thought: since Lucene has
query/filter cache {!join} algorithm can be migrated on intrinsic Lucene's
IndexSearcher.
Can you elaborate?
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] [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-tabpanelfocusedCommentId=14622449#comment-14622449
]
Ryan Josal commented on SOLR-6234:
--
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] [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-tabpanelfocusedCommentId=14622375#comment-14622375
]
Yonik Seeley commented on SOLR-6234:
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] [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-tabpanelfocusedCommentId=14622330#comment-14622330
]
Timothy Potter commented on SOLR-6234:
--
Ok, we can tackle adding 4905 as a separate ticket.
Regarding David's comment, what does {!join} do that {!scorejoin} does not?
(besides 4905) if nothing, then it seems to make sense to just replace {!join}
with this implementation vs. introducing a new qparser type.
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] [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-tabpanelfocusedCommentId=14622343#comment-14622343
]
Yonik Seeley commented on SOLR-6234:
bq. Regarding David's comment, what does {!join} do that {!scorejoin} does not?
(besides 4905) if nothing, then it seems to make sense to just replace {!join}
From an API perspective, nothing that I'm aware of. From an implementation
perspective, it can be faster or slower depending on the details (it's a
different implementation). So it makes sense to perhaps consolidate the APIs,
but keep the different implementations (sort of like facet.method does for
faceting).
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] [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-tabpanelfocusedCommentId=14620709#comment-14620709
]
Timothy Potter commented on SOLR-6234:
--
Actually ... hold that thought ... looks like code is still hitting
JoinQParserPlugin.java for some reason ??? I'll dig.
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] [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-tabpanelfocusedCommentId=14621658#comment-14621658
]
Ryan Josal commented on SOLR-6234:
--
That makes a lot of sense David, I would prefer this as it would reduce
confusion, some similar code, and make implementation changes in the future
more flexible.
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] [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-tabpanelfocusedCommentId=14621648#comment-14621648
]
David Smiley commented on SOLR-6234:
One tiny bit of input I have on this is rather cosmetic but nonetheless it'd be
nice if the scoring mode could be specified via a local-param on the existing
\{!join} QParserPlugin. It's still a join, we just want the score too. It
very well may have a different implementation when it's scoring but that's an
implementation detail.
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] [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-tabpanelfocusedCommentId=14620738#comment-14620738
]
Timothy Potter commented on SOLR-6234:
--
Well, nm ... I must not have done a full clean / rebuild. After doing so, it is
working! Sorry for the noise ... will start looking into Ryan's contribution as
well now. Thanks [~mkhludnev] - great feature!
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] [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-tabpanelfocusedCommentId=14621414#comment-14621414
]
Timothy Potter commented on SOLR-6234:
--
[~mkhludnev] I'm wondering if we should add the solution for SOLR-4905 to the
scorejoin parser too? It seems like this would be a good thing for scorejoin to
support as well.
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] [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-tabpanelfocusedCommentId=14619385#comment-14619385
]
Ryan Josal commented on SOLR-6234:
--
That will be great Tim! For my personal use case, I added a feature to the
qparser that, after constructing the LocalSolrQueryRequest, would apply the
handler config (defaults, appends, invariants) from the otherCore (say
/select handler) to the request so that in a nutshell your other query could
be a simple string and it would follow whatever edismax rules you had
configured for the other core. That instead of the more strict db style lucene
query syntax. If there's interest I am happy to share the patch.
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
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] [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-tabpanelfocusedCommentId=14619436#comment-14619436
]
Timothy Potter commented on SOLR-6234:
--
[~rjosal] sounds cool ... definitely share the patch!
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
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] [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-tabpanelfocusedCommentId=14619250#comment-14619250
]
Timothy Potter commented on SOLR-6234:
--
I'm working to get this patch committed to trunk / 5x
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
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] [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-tabpanelfocusedCommentId=14619373#comment-14619373
]
Mikhail Khludnev commented on SOLR-6234:
Tell me if I need to improve something! 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: 5.3
Reporter: Mikhail Khludnev
Assignee: Timothy Potter
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] [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-tabpanelfocusedCommentId=14587591#comment-14587591
]
Neeraj Lajpal commented on SOLR-6234:
-
Thanks for pointing that out Ryan.
I will keep that in mind while designing algo that will decide boosting params.
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] [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-tabpanelfocusedCommentId=14586428#comment-14586428
]
Neeraj Lajpal commented on SOLR-6234:
-
Thanks a lot Ryan.
This solved my problem.
But, needed to change a couple of things, enclose the value of _query_ in
double quotes and remove jq.
Without these changes it was not showing any result.
I executed this query:
important_category:322^4 _query_:{!scorejoin from=_root_ to=id score=avg
multiVals=false}(brandid:1398^4 OR brandid:237^4.5)
debug: {
rawquerystring: important_cat:322^4 _query_:\{!scorejoin from=_root_
to=id score=avg multiVals=false}(brandid:1398^4 OR brandid:237^4.5)\,
querystring: important_cat:322^4 _query_:\{!scorejoin from=_root_ to=id
score=avg multiVals=false}(brandid:1398^4 OR brandid:237^4.5)\,
parsedquery: important_cat:322^4.0 SameCoreJoinQuery(SameCoreJoinQuery
[fromQuery=brandid:1398^4.0 brandid:237^4.5, fromField=_root_, toField=id,
scoreMode=Avg, boost=1.0, multiVals=false])
}
Everything looks fine.
Thanks again.
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] [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-tabpanelfocusedCommentId=14586427#comment-14586427
]
Neeraj Lajpal commented on SOLR-6234:
-
Thanks a lot Ryan.
This solved my problem.
But, needed to change a couple of things, enclose the value of _query_ in
double quotes and remove jq.
Without these changes it was not showing any result.
I executed this query:
important_category:322^4 _query_:{!scorejoin from=_root_ to=id score=avg
multiVals=false}(brandid:1398^4 OR brandid:237^4.5)
debug: {
rawquerystring: important_cat:322^4 _query_:\{!scorejoin from=_root_
to=id score=avg multiVals=false}(brandid:1398^4 OR brandid:237^4.5)\,
querystring: important_cat:322^4 _query_:\{!scorejoin from=_root_ to=id
score=avg multiVals=false}(brandid:1398^4 OR brandid:237^4.5)\,
parsedquery: important_cat:322^4.0 SameCoreJoinQuery(SameCoreJoinQuery
[fromQuery=brandid:1398^4.0 brandid:237^4.5, fromField=_root_, toField=id,
scoreMode=Avg, boost=1.0, multiVals=false])
}
Everything looks fine.
Thanks again.
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] [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-tabpanelfocusedCommentId=14586444#comment-14586444
]
Ryan Josal commented on SOLR-6234:
--
I've been using this for a few days now, and here are my comments:
*) it's more functionally useful to have the scores returned with this than the
!join parser.
*) basing it off JoinUtil is a clean solution that centralizes this type of
logic.
*) That being said, scorejoin has performed worse than !join in my tests,
usually almost twice as slow. It's not an exhaustive test by any means, just
an observation. So it doesn't seem fit to replace !join as it is, although it
does feel like this is the right direction to be going for joins.
*) JoinUtil does not currently support multivalue fields for the to index.
It chooses one of the matching values instead of applying the ScoreMode for all
matching documents. It's a fairly small change to TermsIncludingScoreQuery to
add this feature.
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] [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-tabpanelfocusedCommentId=14586457#comment-14586457
]
Ryan Josal commented on SOLR-6234:
--
[~neerajlajpal], glad you got it working. There might be a caution with using
!scorejoin this way. The scores coming back from !scorejoin are from the query
to the fromIndex, and so they're not really related to the score coming from
the important_category matches. The matches from the scorejoin might have a
really high max score, while the matches from the important_category might have
a really low max_score, in a relative sense. Or vice versa. I think this use
case is workable but it's something to keep in mind.
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] [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-tabpanelfocusedCommentId=14583350#comment-14583350
]
Neeraj Lajpal commented on SOLR-6234:
-
I have a doubt regarding query time join.
Example:
I have the document structure like this:
parent1: id, important_category
child1: id, _root_,brandid
child2:id,_root_,brandid
_root_ field of child doc contains value of parent's id.
I want to use query time join. I want all the parent documents after applying
boosts on children's fields and avg their scores, and then apply boost on
important_category field on parent.
My query is like this without boost on parent's field:
{!scorejoin from=_root_ to=id score=avg multiVals=false}(brandid:1398^4 OR
brandid:237^4.5)
It is working fine.
But, I want to apply boost to important_category field of parent also.
If I will use fq it will not impact score, so I have to use q only.
If I make q like : important_category:322^4{!scorejoin from=_root_ to=id
score=avg multiVals=false}(brandid:1398^4 OR brandid:237^4.5)
it is not showing any results.
How can I do this?
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] [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-tabpanelfocusedCommentId=14583437#comment-14583437
]
Ryan Josal commented on SOLR-6234:
--
[~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] [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-tabpanelfocusedCommentId=14579608#comment-14579608
]
Ryan Josal commented on SOLR-6234:
--
This is awesome, the normal !join qparser is mainly only good for fq, but with
scoring, this is good as a q or subquery.
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, 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] [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-tabpanelfocusedCommentId=14308784#comment-14308784
]
Mikhail Khludnev commented on SOLR-6234:
that's would be great if we replicate SOLR-4905 here also. Please vote, let me
know if you need it.
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, 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] [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-tabpanelfocusedCommentId=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}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] [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-tabpanelfocusedCommentId=14244238#comment-14244238
]
Mikhail Khludnev commented on SOLR-6234:
[~Parnit] it clearly explain the reason {{scoreMode=None}}, I believe you just
need to specify any value for this local param. I put it into description
explicitly.
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-tabpanelfocusedCommentId=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] [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-tabpanelfocusedCommentId=14244406#comment-14244406
]
Mikhail Khludnev commented on SOLR-6234:
[~Parnit] could you upload solr folder with index and core configs and send me
the link?
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-tabpanelfocusedCommentId=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-tabpanelfocusedCommentId=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=edismaxq=*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
[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-tabpanelfocusedCommentId=14242524#comment-14242524
]
Mikhail Khludnev commented on SOLR-6234:
bq. lose all information from the subIndex the moment the parser sees .
that's what I don't understand.
nevertheless it should work by supplying field function query as a to side
query
testServer/solr/MainIndex/select?q={!scorejoin from=id to=id
fromIndex=subIndex}metric
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-tabpanelfocusedCommentId=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-tabpanelfocusedCommentId=14242647#comment-14242647
]
Mikhail Khludnev commented on SOLR-6234:
I'm sure sort=score asc.. will reverse results
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-tabpanelfocusedCommentId=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-tabpanelfocusedCommentId=14242762#comment-14242762
]
Mikhail Khludnev commented on SOLR-6234:
bq. Is this a bug.
yes it is. the parsing of fromQuery is incorrect in case of cross core join.
Shame on me. The only excuse is the absence of two cores tests in overall test
codebase.
Committers, is there an example of bi-core test?
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-tabpanelfocusedCommentId=14243108#comment-14243108
]
Mikhail Khludnev commented on SOLR-6234:
[~Parnit] I have a workaround. The problem occurs only during query parsing. I
suppose you can just define optional 'metric' field in the MainIndex that
allows to parse fromQuery, and come further.
Pls post exception if it doesn't help 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),
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-tabpanelfocusedCommentId=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-tabpanelfocusedCommentId=14243218#comment-14243218
]
Mikhail Khludnev commented on SOLR-6234:
[~Parnit] I asked you to use http://wiki.apache.org/solr/FunctionQuery#field ie
you need to
testServer/solr/MC_10001_CatalogEntry_en_US/select?q={!scorejoin from=id to=id
fromIndex=subIndex}metric1
just 'metric1' nothing more, ie no need wildcard metric1:*. Note it will work
if metric is number!
if something goes wrong, add
http://wiki.apache.org/solr/CommonQueryParameters#debugQuery and post here the
link to the output (I hope, explain works there for scorejoin)
regarding the inconvenience, you can declare it in the schema as dynamicField.
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-tabpanelfocusedCommentId=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_rankdebugQuery=true
metric1 is also an int type like you stated
Here is the debug
str name=rawquerystring
{!scorejoin from=id to=id fromIndex=subIndex}metric1
/str
str name=querystring
{!scorejoin from=id to=id fromIndex=subIndex}metric1
/str
str name=parsedquery
OtherCoreJoinQuery(OtherCoreJoinQuery [fromIndex=subIndex,
fromCoreOpenTime=1418333501496 extends SameCoreJoinQuery
[fromQuery=defaultSearch:(metric1 view) rank, fromField=id , toField=id ,
scoreMode=None, boost=1.0]])
/str
str name=parsedquery_toString
OtherCoreJoinQuery [fromIndex=subIndex, fromCoreOpenTime=1418333501496 extends
SameCoreJoinQuery [fromQuery=defaultSearch:(metric1 view) rank, fromField=id,
toField=id, scoreMode=None, boost=1.0]]
/str
lst name=explain/
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-tabpanelfocusedCommentId=14243803#comment-14243803
]
Mikhail Khludnev commented on SOLR-6234:
[~Parnit], ok...not well but, ok.
pay attention to
{code}
fromQuery=defaultSearch:(metric1 view) rank
{code}
it seems like it wasn't recognized as a function query, make a clue:
{code}
{!func}metric1
{code}
ie
{code}
{!scorejoin from=id to=id fromIndex=subIndex}{!func}metric1
{code}
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-tabpanelfocusedCommentId=14213989#comment-14213989
]
Mikhail Khludnev commented on SOLR-6234:
[~ehatcher] this one is great for 4.10.3
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: 4.10.3, 5.0
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-tabpanelfocusedCommentId=14212701#comment-14212701
]
Mikhail Khludnev commented on SOLR-6234:
[~sar...@syr.edu] do you mean this one?
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, Trunk
Reporter: Mikhail Khludnev
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-tabpanelfocusedCommentId=14086577#comment-14086577
]
Mikhail Khludnev commented on SOLR-6234:
damn, the last patch doesn't use {{multiVals}} as a component at
equals/hashcode. It's not a big deal, because the param itself seems pretty
useless. Anyway, I can fixed it in a few mins, if you want to apply the patch.
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.0, 4.10
Reporter: Mikhail Khludnev
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.2#6252)
-
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-tabpanelfocusedCommentId=14073137#comment-14073137
]
Mikhail Khludnev commented on SOLR-6234:
[~martijn.v.groningen] [~rcmuir] let me gently remind you about this patch.
As a side note, this ticket allows to reveal LUCENE-5653, wouldn't you mind to
provide scorejoin for Solr users!
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.0, 4.10
Reporter: Mikhail Khludnev
Attachments: 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}}
- it doesn't cover cross core join case, 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!
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.2#6252)
-
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-tabpanelfocusedCommentId=14057188#comment-14057188
]
Mikhail Khludnev commented on SOLR-6234:
[~jacklo]
I still think we need to *add* this QParse for Solr users, *rather than
decommission the current Solr join*. I agree its' code is not easy to read, but
I suppose it performs better in certain cases, and/or consume fewer memory than
straightforward JoinUtil.
re LUCENE-3759 : I don't believe that true distributed join performs well for
practical usage (here I agree with Yonik's comment at SOLR-4905). As far as I
understand, what you've done in SOLR-4905 allows to do _collocated join_ even
with multiple shards ie. if we place _from_ and _to_ side documents at the same
shard, it's able to join them. I think it's what we need.
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.0, 4.10
Reporter: Mikhail Khludnev
Attachments: 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}}
- it doesn't cover cross core join case, 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!
--
This message was sent by Atlassian JIRA
(v6.2#6252)
-
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-tabpanelfocusedCommentId=14056978#comment-14056978
]
Jack Lo commented on SOLR-6234:
---
It would be better to integrate this into the main JoinQParser where no scoring
would just be the old and default behavior. And since you are using Lucene
JoinUtils, we can get rid of the old code in JoinQParser as well.
I also have a patch that partially make join work in a distributed environment.
It's in [SOLR-4905|https://issues.apache.org/jira/browse/SOLR-4905], but that's
reusing code in JoinQParser and doesn't work if fromIndex has more than 1
shard. However, by fixing
[LUCENE-3759|https://issues.apache.org/jira/browse/LUCENE-3759] and combining
your patch, we can make distributed join work as long as all shards reside
locally.
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.0, 4.10
Reporter: Mikhail Khludnev
Attachments: 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}}
- it doesn't cover cross core join case, 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!
--
This message was sent by Atlassian JIRA
(v6.2#6252)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
