I developed a join transformer plugin that did that (although it didn't flatten the results like that). The one thing that was painful about it is that the TextResponseWriter has references to both the IndexSchema and SolrReturnFields objects for the primary core. So when you add a SolrDocument from another core it returned the wrong fields. I worked around that by transforming the SolrDocument to a NamedList. Then when it gets to processing the IndexableFields it uses the wrong IndexSchema, I worked around that by transforming each field to a hard Java object (through the IndexSchema and FieldType of the correct core). I think it would be great to patch TextResponseWriter with multi core writing abilities, but there is one question, how can it tell which core a SolrDocument or IndexableField is from? Seems we'd have to add an attribute for that.
The other possibly simpler thing to do is execute the join at index time with an update processor. Ryan On Tuesday, October 6, 2015, Mikhail Khludnev <mkhlud...@griddynamics.com> wrote: > On Wed, Oct 7, 2015 at 7:05 AM, Ali Nazemian <alinazem...@gmail.com > <javascript:;>> wrote: > > > it > > seems there is not any way to do that right now and it should be > developed > > somehow. Am I right? > > > > yep > > > -- > Sincerely yours > Mikhail Khludnev > Principal Engineer, > Grid Dynamics > > <http://www.griddynamics.com> > <mkhlud...@griddynamics.com <javascript:;>> >
