My current solution is overriding the out-of-the-box shard routing, and forcing each document and its attachment to go into a specific shard. But this is so I can support the query time joins (because join are only performed between documents in the same shard).
I'm a bit concerned by this approach only because it forces me to overdrive out-of-the-box solr behavior. I didn't implement the whole thing yet, so can't say anything about performance. You're saying that your block-join solution does the same thing at index time (putting document and its attachments in the same shard), but at query time it doesn't require to perform explicit join? If you could add an example of what you'll index, and how you'll query , it would be very helpful. Also, if this ticket is going to get into one of the next releases, and it solves the join problem, it seems that its worth waiting for. Mikhail Khludnev wrote > during indexing whole block (doc and it's attachment) goes into particular > shard, then it's can be queried per every shard and results are merged. > > btw, do you feel any problem with your current approach - query time joins > and out-of-the-box shard routing? > > > On Tue, Jul 2, 2013 at 5:19 PM, adfel70 < > adfel70@ > > wrote: > >> I'm not familiar with block join in lucene. I've read a bit, and I just >> want >> to make sure - do you think that when this ticket is released, it will >> solve >> the current problem of solr cloud joins? >> >> Also, can you elaborate a bit about your solution? >> >> >> Jack Krupansky-2 wrote >> > It sounds like 4.4 will have an RC next week, so the prospects for >> block >> > join in 4.4 are kind of dim. I mean, such a significant feature should >> > have >> > more than a few days to bake before getting released. But... who knows >> > what >> > Yonik has planned! >> > >> > -- Jack Krupansky >> > >> > -----Original Message----- >> > From: adfel70 >> > Sent: Tuesday, July 02, 2013 7:41 AM >> > To: >> >> > solr-user@.apache >> >> > Subject: Re: Converting nested data model to solr schema >> > >> > As you see it, does SOLR-3076 fixes my problem? >> > >> > Is SOLR-3076 fix getting into solr 4.4? >> > >> > >> > Mikhail Khludnev wrote >> >> On Mon, Jul 1, 2013 at 5:56 PM, adfel70 < >> > >> >> adfel70@ >> > >> >> > wrote: >> >> >> >>> This requires me to override the solr document distribution >> mechanism. >> >>> I fear that with this solution I may loose some of solr cloud's >> >>> capabilities. >> >>> >> >> >> >> It's not clear whether you aware of >> >> http://searchhub.org/2013/06/13/solr-cloud-document-routing/ , but >> what >> >> you >> >> did doesn't sound scary to me. If it works, it should be fine. I'm not >> >> aware of any capabilities that you are going to loose. >> >> Obviously SOLR-3076 provides astonishing query time performance, with >> >> offloading actual join work into index time. Check it if you current >> >> approach turns slow. >> >> >> >> >> >> -- >> >> Sincerely yours >> >> Mikhail Khludnev >> >> Principal Engineer, >> >> Grid Dynamics >> >> >> >> <http://www.griddynamics.com> >> >> < >> > >> >> mkhludnev@ >> > >> >> > >> > >> > >> > >> > >> > >> > -- >> > View this message in context: >> > >> http://lucene.472066.n3.nabble.com/Converting-nested-data-model-to-solr-schema-tp4074351p4074668.html >> > Sent from the Solr - User mailing list archive at Nabble.com. >> >> >> >> >> >> -- >> View this message in context: >> http://lucene.472066.n3.nabble.com/Converting-nested-data-model-to-solr-schema-tp4074351p4074696.html >> Sent from the Solr - User mailing list archive at Nabble.com. >> > > > > -- > Sincerely yours > Mikhail Khludnev > Principal Engineer, > Grid Dynamics > > <http://www.griddynamics.com> > < > mkhludnev@ > > -- View this message in context: http://lucene.472066.n3.nabble.com/Converting-nested-data-model-to-solr-schema-tp4074351p4074876.html Sent from the Solr - User mailing list archive at Nabble.com.
