[
https://issues.apache.org/jira/browse/LUCENE-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand updated LUCENE-4936:
---------------------------------
Attachment: LUCENE-4936.patch
Here is a work-around for the issue: the consumer stops trying to perform GCD
compression as soon as it encounters a value outside the [ -MAX_VALUE/2 -
MAX_VALE/2 ] range. This prevents overflows from happening and I can't think of
a reasonable use-case that would benefit from GCD compression and have values
outside of this range?
> docvalues date compression
> --------------------------
>
> Key: LUCENE-4936
> URL: https://issues.apache.org/jira/browse/LUCENE-4936
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/index
> Reporter: Robert Muir
> Assignee: Adrien Grand
> Attachments: LUCENE-4936.patch, LUCENE-4936.patch, LUCENE-4936.patch,
> LUCENE-4936.patch
>
>
> DocValues fields can be very wasteful if you are storing dates (like solr's
> TrieDateField does if you enable docvalues) and don't actually need all the
> precision: e.g. "date-only" fields like date of birth with no time component,
> time fields without milliseconds precision, and so on.
> Ideally we'd compute GCD of all the values to save space
> (numberOfTrailingZeros is not really enough here), but i think we should at
> least look for values like 86400000, 3600000, and 1000 to be practical.
--
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: [email protected]
For additional commands, e-mail: [email protected]
