Thanks again Alex.
I should have clarified the use of browse request handler. The reason I'm
simulating the request handler parameters of my production system using
browse. I used a separate request handler, stripped down all properties to
match "select". I finally narrowed down the issue to Minim
I am not sure why you are even trying this against /browse, but the
easy way to compare handlers is to add echoParams=all to both requests
and compare all parameters side-by-side.
Regards,
Alex.
Newsletter and resources for Solr beginners and intermediates:
http://www.solr-start.com/
On
Sorry to bump this up, but can someone please explain the parsing behaviour
of a join query (show above) in respect to different request handler ?
--
View this message in context:
http://lucene.472066.n3.nabble.com/How-to-retrieve-parent-documents-without-a-nested-structure-block-join-tp4297510
Thanks Alex, this has been extremely helpful. There's one doubt though.
The query returns expected result if I use "select" or "query" request
handler, but fails for others. Here's the debug output from "/select" using
edismax.
http://localhost:8983/solr/techproducts/query?q=({!join%20from=manu_i
This seems to work against the techproducts example in 6.2:
({!join from=manu_id_s to=id}ipod) (name:GB18030 -manu_id_s:*)
Two clauses, first one does join and parent mapping. The second one
looks at the records that don't have the mapping key at all and run
the match against that. In your case,
Thanks for getting back on this. I was trying to formulate a query in similar
lines but not able to construct it (multiple clauses) correctly so far. That
can be attributed to my inexperience with Solr queries as well. Can you
please point to any documentation / example for my reference ?
Appreci
Can't you just have two clauses in the query, one that does join and one
that does the same search again but with additional rule of not having a
parentID? Then nested documents match first clause and get "joined" into
the parent record. And non nested documents would match by themselves. I
think y
Thanks Alex. With the conventional join query I'm able to return the parent
document based on a query match on the child. But, it filters out any other
documents which are outside the scope of join condition. For e.g. in my
case, I would expect the query to return :
1
Parent title
123
Why not a traditional join?
https://cwiki.apache.org/confluence/display/solr/Other+Parsers#OtherParsers-JoinQueryParser
Regards,
Alex.
Newsletter and resources for Solr beginners and intermediates:
http://www.solr-start.com/
On 23 September 2016 at 00:16, Shamik Bandopadhyay wrote:
> Hi
