lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (JIRA) <j...@apache.org>
Subject [jira] [Closed] (SOLR-440) Should use longs for internal DateField storage
Date Tue, 19 Feb 2013 23:19:13 GMT

     [ https://issues.apache.org/jira/browse/SOLR-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jan Høydahl closed SOLR-440.
----------------------------

    Resolution: Duplicate

This is fixed way back, closing.
                
> Should use longs for internal DateField storage
> -----------------------------------------------
>
>                 Key: SOLR-440
>                 URL: https://issues.apache.org/jira/browse/SOLR-440
>             Project: Solr
>          Issue Type: Improvement
>          Components: search
>    Affects Versions: 1.2, 1.3
>            Reporter: Stu Hood
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message