Thank you Shawn for the excellent use case. :)
On Wed, Jul 3, 2013 at 9:34 AM, Shawn Heisey wrote:
> On 7/3/2013 9:22 AM, Ali, Saqib wrote:
>
>> What would be the use case for such a field:
>>
>> > stored="false"/>
>>
>>
>> and
>>
>> > stored="false"/>
>>
>
> I have a field li
On 7/3/2013 9:22 AM, Ali, Saqib wrote:
What would be the use case for such a field:
and
I have a field like this in my schema. That field is used as one of the
source fields that get copied to my "catchall" field. I don't need the
field by itself, but I use it in conj
Or you may have dynamic field as stored but ignore some specific fields
that would otherwise be matching the dynamic field mask. Useful if you are
trying to get metadata but not content out of something.
This is based on specific field names matching before dynamic ones.
Regards,
Alex.
Person
.. you could still have update processors that look at the values of
> "ignored" fields and maybe assigns them to other, non-ignored fields.
>
> -- Jack Krupansky
>
> -Original Message- From: Ali, Saqib
> Sent: Wednesday, July 03, 2013 11:22 AM
> To: solr-user@lucene
i, Saqib
> Sent: Wednesday, July 03, 2013 11:22 AM
> To: solr-user@lucene.apache.org
> Subject: Use case indexed="false" stored="false" field
>
> Hello all,
>
>
> What would be the use case for such a field:
>
>
>
>
> and
>
>
>
>
> ?
>
>
> Thanks.
Krupansky
-Original Message-
From: Ali, Saqib
Sent: Wednesday, July 03, 2013 11:22 AM
To: solr-user@lucene.apache.org
Subject: Use case indexed="false" stored="false" field
Hello all,
What would be the use case for such a field:
stored="false"/>
and
?
Thanks.
Maybe to ignore?
You can set a dynamic Field to ignore as well.
On Wed, Jul 3, 2013 at 9:22 AM, Ali, Saqib wrote:
> Hello all,
>
>
> What would be the use case for such a field:
>
> stored="false"/>
>
>
> and
>
> stored="false"/>
>
>
> ?
>
>
> Thanks.
>
--
Bill Bell
billn
Hello all,
What would be the use case for such a field:
and
?
Thanks.
