Good point. You might have input fields for year, month, and day. You could ignore those, but use them to make a date field.
wunder On Jul 3, 2013, at 8:32 AM, Jack Krupansky wrote: > Setting both indexed and stored to false means to ignore input values for > that field. > > The effective use case is that these fields may have values in the update > input stream and they will be ignored. Without these field definitions, those > same field values would cause exceptions - references to undefined fields. In > other words, you are telling Solr that it is okay to have inputs for these > fields - simply ignore them. > > But... 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.apache.org > Subject: Use case indexed="false" stored="false" field > > Hello all, > > > 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"/> > > > ? > > > Thanks.
