: name="lastsignindate"></field> which caused a SOLR exception. Is it intended
: that SOLR treats an empty field differently from it simply not being sent at
: all? Or is this just a consequence of how it's coded?

i don't know that it was specificly intended, but it does have it's 
advantages.

The issue of having an optional way to "ignore" empty values has come up 
in the past...

   https://issues.apache.org/jira/browse/SOLR-1772

...my comments in that issue address a few reasons why i think it would 
make more sense to have it be a new optional UpdateProcessor instead of a 
property of the FieldTypes.


-Hoss


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to