lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-5648) Index/search multi-valued time durations
Date Thu, 05 Jun 2014 01:45:02 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-5648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14018405#comment-14018405
] 

ASF subversion and git services commented on LUCENE-5648:
---------------------------------------------------------

Commit 1600555 from [~dsmiley] in branch 'dev/trunk'
[ https://svn.apache.org/r1600555 ]

LUCENE-5648: DateRangePrefixTree and NumberRangePrefixTreeStrategy

> 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
>         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.2#6252)

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


Mime
View raw message