Re: Use case indexed="false" stored="false" field

[Shawn Heisey]

On 7/3/2013 9:22 AM, Ali, Saqib wrote:
What would be the use case for such a field:
         <field name="stored_on" type="tdate" indexed="false" stored="false"/>


and

         <field name="summary" type="string" indexed="false" stored="false"/>

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 conjunction with other fields.

If I can get the app developers to switch over to using edismax more, I 
will get rid of the catchall field and then set that field to indexed 
and not stored.

Thanks,
Shawn