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.
===========================================================================
