[
https://issues.apache.org/jira/browse/SOLR-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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: [email protected]
For additional commands, e-mail: [email protected]
