Following up on Shawn's comment, this can be the result of some sort of serialization or, if you're pulling info from a DB the literal string NULL may be returned from the DB.
Solr really has no concept of a distinct value of NULL for a field, in Solr/Lucene terms that's just the total absence of the field from the document. Best, Erick On Sun, Aug 23, 2015 at 8:15 AM, Shawn Heisey <apa...@elyograg.org> wrote: > On 8/23/2015 8:29 AM, Henrique O. Santos wrote: >> I am doing some manual indexing using Solr Admin UI to be exactly sure >> how TrieDateFields and null values work. When I remove the TrieDateField >> from the document, I get the following when trying to index it: >> >> | "msg": "Invalid Date String:'NULL'", >> "code": 400| > > Unless the field is marked as required in your schema, TrieDateField > will work if you have no value for the field. This means the field is > not present in the javabin, xml, or json data sent to Solr for indexing, > not that the empty string is present. > > What you have here is literally the string "NULL" -- four letters. This > will NOT work on any kind of Trie field. > > Sometimes you can run into a conversion glitch related to a Java null > object, but in that case the value is usually lowercase -- "null" -- > which wouldn't work either. > > Thanks, > Shawn >
