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, is there a reason why I should not do that?
If it is ok, I could submit a patch.
Thanks.
On Tue, Dec 6, 2011 at 1:20 PM, Pascal Dimassimo <
pascal.dimass...@sematext.com> wrote:
> 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 documents of index1
> by matching the "tag" field.
>
> According to my tests, It looks like the "restaurant" query will always be
> parsed using the Lucene QParser. I did not find a way to use another
> QParser, like Dismax. Am I right or is there a way?
>
> Thanks!
>
> --
> Pascal Dimassimo
> ----
> Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
> Lucene ecosystem search :: http://search-lucene.com/
>
>
--
Pascal Dimassimo
----
Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
Lucene ecosystem search :: http://search-lucene.com/
