Thanks Hoss!
Here it is:
https://issues.apache.org/jira/browse/SOLR-2972
On Wed, Dec 14, 2011 at 4:47 PM, Chris Hostetter
wrote:
>
> : I have been doing more tracing in the code. And I think that I
> understand a
> : bit more. The problem does not seem to be dismax+join, but
> : dismax+join+from
: I have been doing more tracing in the code. And I think that I understand a
: bit more. The problem does not seem to be dismax+join, but
: dismax+join+fromIndex.
Correct. join+dismax works fine as i already demonstrated...
: >> Note: even with that hardcoded "lucene" bug, you can still overr
Hi,
I have been doing more tracing in the code. And I think that I understand a
bit more. The problem does not seem to be dismax+join, but
dismax+join+fromIndex.
When doing this joined dismax query on the same index:
http://localhost:8080/solr/gutenberg/select?q={!join+from=id+to=id+v=$qq}&qq={!d
Thanks Hoss!
But unfortunately, the dismax parameters (like qf) are not passed over to
the fromIndex. In fact, even if using var dereferencing makes Dismax to be
selected as the "fromQueryParser", the query that is passed to the
JoinQuery object contains nothing to indicate that it should use dism
: Is there a specific reason why it is hard-coded to use the "lucene"
: QParser? I was looking at JoinQParserPlugin.java and here it is in
: createParser:
:
: QParser fromQueryParser = subQuery(v, "lucene");
:
: I could pass another param named "fromQueryParser" and use it instead of
: "lucene"
Hi,
Is there a specific reason why it is hard-coded to use the "lucene"
QParser? I was looking at JoinQParserPlugin.java and here it is in
createParser:
QParser fromQueryParser = subQuery(v, "lucene");
I could pass another param named "fromQueryParser" and use it instead of
"lucene". But again,
Hi,
Thanks for this! But your "partner-tmo" request handler is probably
configured with your ing-content index, no? In my case, I'd like to execute
a dismax query on the fromIndex.
On Tue, Dec 6, 2011 at 2:57 PM, Jeff Schmidt wrote:
> Hi Pascal:
>
> I have an issue similar to yours, but also ne
Hi Pascal:
I have an issue similar to yours, but also need to facet the joined documents...
I've been playing with various things. There's not much documentation I can
find.
Looking at http://wiki.apache.org/solr/Join, in the fourth example you can see
the join being relegated to a filter quer
Hi,
I was trying Solr Join across 2 cores on the same Solr installation. Per
example:
/solr/index1/select?q={!join fromIndex=index2 from=tag to=tag}restaurant
My understanding is that the "restaurant" query will be executed on index2
and the results of this query will be joined with the document
