Hold it. "date", "tdate", "pdate" _are_ primitive types. Under the
covers date/tdate are just a tlong type, newer Solrs have a "pdate"
which is a point numeric type. All that these types do is some parsing
up front so you can send human-readable data (and get it back). But
under the covers it's
While you're generally right, in this case it might make sense to stick
to a primitive type.
I see "unixtime" as a technical information, probably from
System.currentTimeMillis(). As long as it's not used as a "real world"
date but only for sorting based on latest updates, or chosing which
There was time ago a Solr installation which had the same problem, and the
author explained me that the choice was made for performance reasons.
Apparently he was sure that handling everything as primitive types would
give a boost to the Solr searching/faceting performance.
I never agreed ( and
What Hoss said, and in addition somewhere some
custom code has to be translating things back and
forth. For dates, Solr wants -MM-DDTHH:MM:SSZ
as a date string it knows how to deal with. That simply
couldn't parse as a float type so there's some custom
code that transforms dates into a float
: Here is my question. In schema.xml, there is this field:
:
:
:
: Question: why is this declared as a float datatype? I'm just looking
: for an explanation of what is there – any changes come later, after I
: understand things better.
You would hvae to ask the creator of that
I have inherited a working SOLR installation, that has not been upgraded since
solr 4.0. My task is to bring it forward (at least 6.x, maybe 7.x). I am
brand new to SOLR.
Here is my question. In schema.xml, there is this field:
Question: why is this declared as a float
