Hi Mikhail, The per row scenario would cater for queries that is looking at specific rows with. For example, I need address and bank details of a member that is stored on a different core
I guess what I am trying to do is get Solr search functionality that is similar to DB, something which I can easily plug my marious corporate solutions into o that they can retrieve info -----Original Message----- From: Mikhail Khludnev [mailto:m...@apache.org] Sent: 26 January 2017 09:23 AM To: solr-user Subject: Re: Solr Search Handler Suggestion Hello, Moenieb. It'd worth to mention that it's not effective to include, java-user@ in this thread. Also, this proposal is purposed DIH, that's worth to be mentioned in subj. Then, this config looks like it will issue solr request per every parent row that's deadly inefficient. On Wed, Jan 25, 2017 at 10:53 AM, Moenieb Davids <moenieb.dav...@gpaa.gov.za > wrote: > Hi Guys, > > Just an Idea for easier config of search handlers: > > Will it be feasible to configure a search handler that has its own > schema based on the current core as well as inserting nested objects > from cross core queries. > > Example (for illustration purpose, ignore syntax :) ) <document> > > <field column="id" name="xxx" /> > > <field column="FieldA" name="yyy" /> > > <field column="FieldB" name="zzz" /> > <entity name="liked_items" processor="SolrEntityProcessor" url=" > http://localhost:8983/solr/items"; query="user_liking_this:${thiscore.id}" > > > <field column="ResultColA" name="nameA" /> > <field column="ResultColB" name="nameB" /> > </entity> > > <field column="FieldC" name="123" /> > <entity name="liked_items" processor="SolrEntityProcessor" url=" > http://localhost:8983/solr/items"; query="user_liking_this:${thiscore.id}" > > > <field column="ResultColA" name="nameA" /> > <field column="ResultColB" name="nameB" /> > </entity> > > </document> > > This will allow you to create endpoints to interact and return fields > and their values from others cores and seems to be possibly easier to manage? > > > > > > > > > > > ============================================================ > =============== > GPAA e-mail Disclaimers and confidential note > > This e-mail is intended for the exclusive use of the addressee only. > If you are not the intended recipient, you should not use the contents > or disclose them to any other person. Please notify the sender > immediately and delete the e-mail. This e-mail is not intended nor > shall it be taken to create any legal relations, contractual or otherwise. > Legally binding obligations can only arise for the GPAA by means of a > written instrument signed by an authorised signatory. > ============================================================ > =============== > -- Sincerely yours Mikhail Khludnev =========================================================================== GPAA e-mail Disclaimers and confidential note This e-mail is intended for the exclusive use of the addressee only. If you are not the intended recipient, you should not use the contents or disclose them to any other person. Please notify the sender immediately and delete the e-mail. This e-mail is not intended nor shall it be taken to create any legal relations, contractual or otherwise. Legally binding obligations can only arise for the GPAA by means of a written instrument signed by an authorised signatory. ===========================================================================
