Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
1.2, 1.3
-
None
-
None
Description
The current DateField implementation uses formatted Strings internally to store dates.
As a user creating a schema, I assumed that using the DateField type would be more efficient than using an integer field to store seconds. In fact, the DateField type is currently significantly less efficient: ~20 extra bytes are required per value, and String sorting requires that all values fit in memory.
As soon as sorting on long fields has been implemented (SOLR-324), I'd suggest that the date implementation be switched to use long values internally, representing milliseconds since the epoch in UTC. Unfortunately, this will cause index incompatibilities, so the schema version will need to be bumped.
