[jira] [Updated] (LUCENE-7814) DateRangePrefixTree trouble finding years in last millennia +292,000,000

["David Smiley (JIRA)" <ji...@apache.org>]

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

David Smiley updated LUCENE-7814:
---------------------------------
    Attachment: LUCENE_7814_DateRangePrefixTree_last_millennia_bug.patch

RandomizedTesting FTW; eventually a year in this millennia turned up with the right circumstances :-)  It could have been made more likely by some point (time instance) optimizations I'm working on now which will get its own issue, plus some crude beasting.  

Here's a patch.  

The only pertinent part of DateNRStrategyTest is the new test method testLastMillennia; the rest is related to some WIP.

> DateRangePrefixTree trouble finding years in last millennia +292,000,000
> ------------------------------------------------------------------------
>
>                 Key: LUCENE-7814
>                 URL: https://issues.apache.org/jira/browse/LUCENE-7814
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: modules/spatial-extras
>            Reporter: David Smiley
>            Assignee: David Smiley
>         Attachments: LUCENE_7814_DateRangePrefixTree_last_millennia_bug.patch
>
>
> Using DateRangePrefixTree (in spatial-extras): When indexing years on or after the last millennia supported by most computer systems, +292,000,000, a range query like {{\[1970 TO *\]}} will fail to find it.  This happens as a result of some off-by-one errors in DateRangePrefixTree.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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