Hi James,
If you don't want this field to be included in user searches, just omit it from
the search configuration (e.g. if using eDisMax parser, don't put it in the qf
list). To keep it out of search results, exclude it from the fl list. See
http://wiki.apache.org/solr/CommonQueryParameters
and
http://wiki.apache.org/solr/ExtendedDisMax
The overhead from storing it will most likely be very small, and as Micheal
points out it means you could potentially reference documents both ways.
Not sure about the JSON question, but in XML
"<delete><query>uniqueID:7</query></delete>" would remove the whole doc, not
just the uniqueID field.
Tom
On 20 Sep 2012, at 13:38, Spadez <james_will...@hotmail.com> wrote:
> Hi.
>
> My SQL database assigns a uniqueID to each item. I want to keep this
> uniqueID assosiated to the items that are in Solr even though I wont ever
> need to display them or have them searchable. I do however what to be able
> to target specific items in Solr with it, for updating or deleting the
> record.
>
> Right now I have this in my schema:
> <field name="id" type="string" indexed="true" stored="true"/>
>
> However, since I dont want it searchable or stored it should be this:
> <field name="uniqueid" type="string" indexed="false" stored="false"/>
>
> Firstly, is this the correct way of doing this? I saw mention of a "ignore"
> attibute that can be added.
>
> Secondly, if I wanted to do updates to the fields using JSON by targetting
> the uniqueID can I still do something like this:
> "delete": { "uniqueid":"7" }, /* delete entry
> uniqueID=7 */
>
> Thank you for any help you can give. Hope I explained it well enough.
>
> James
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/ID-reference-field-Needed-but-not-searchable-or-retrievable-tp4009162.html
> Sent from the Solr - User mailing list archive at Nabble.com.
