[ https://issues.apache.org/jira/browse/LUCENE-5648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14245812#comment-14245812 ]
ASF subversion and git services commented on LUCENE-5648: --------------------------------------------------------- Commit 1645382 from [~dsmiley] in branch 'dev/branches/branch_5x' [ https://svn.apache.org/r1645382 ] LUCENE-5648: spatial NumberRangePrefixTree refactorings, mostly: * rename NRPT.LevelledValue -> UnitNRShape, NRPT.NRShape -> SpanUnitsNRShape, both subclass new NRPT.NRShape marker class; make all 3 public and use these types in method signatures as appropriate. * remove NRPT pass-through convenience methods on NRPTStrategy (not needed; maintenance burden) * re-order some factory/parsing methods in NRPT to keep together at the top * UnitNRShape implements Comparable, and both NRShape implements Cloneable * improve randomized test to pick better random calendars * more docs > Index/search multi-valued time durations > ---------------------------------------- > > Key: LUCENE-5648 > URL: https://issues.apache.org/jira/browse/LUCENE-5648 > Project: Lucene - Core > Issue Type: New Feature > Components: modules/spatial > Reporter: David Smiley > Assignee: David Smiley > Fix For: 5.0, Trunk > > Attachments: LUCENE-5648.patch, LUCENE-5648.patch, LUCENE-5648.patch, > LUCENE-5648.patch > > > If you need to index a date/time duration, then the way to do that is to have > a pair of date fields; one for the start and one for the end -- pretty > straight-forward. But if you need to index a variable number of durations per > document, then the options aren't pretty, ranging from denormalization, to > joins, to using Lucene spatial with 2D as described > [here|http://wiki.apache.org/solr/SpatialForTimeDurations]. Ideally it would > be easier to index durations, and work in a more optimal way. > This issue implements the aforementioned feature using Lucene-spatial with a > new single-dimensional SpatialPrefixTree implementation. Unlike the other two > SPT implementations, it's not based on floating point numbers. It will have a > Date based customization that indexes levels at meaningful quantities like > seconds, minutes, hours, etc. The point of that alignment is to make it > faster to query across meaningful ranges (i.e. [2000 TO 2014]) and to enable > a follow-on issue to facet on the data in a really fast way. > I'll expect to have a working patch up this week. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org