lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (LUCENE-1470) Add TrieRangeQuery to contrib
Date Thu, 27 Nov 2008 10:45:44 GMT

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

thetaphi edited comment on LUCENE-1470 at 11/27/08 2:45 AM:
-----------------------------------------------------------------

bq. Did you mean TermEnum.skipTo? See LUCENE-1437.

Yes exactly that, I wrote seekTop(), but meant skipTo(). The patch in this issue is only a
faster scanning approach, but the best would be to make skipTo() use the same logic like SegmentInfoReader.terms
that uses seeking on disk and so on, but this comment would be  better for the above issue.

I am fine with calling IndexReader.terms(Term) to use the cache and faster seeking. The cost
of creating new instances of TermEnums is less than doing disk reads.

      was (Author: thetaphi):
    bq. Did you mean TermEnum.skipTo? See LUCENE-1437.

Yes exactly that, I wrote seekTop(), but meant skipTo(). The patch in this patch is only a
faster scanning approach, but the best would be to make skipTo() use the same logic like SegmentInfoReader.terms
that uses seeking on disk and so on, but this comment would be  better for the above issue.

I am fine with calling IndexReader.terms(Term) to use the cache and faster seeking. The cost
of creating new instances of TermEnums is less than doing disk reads.
  
> Add TrieRangeQuery to contrib
> -----------------------------
>
>                 Key: LUCENE-1470
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1470
>             Project: Lucene - Java
>          Issue Type: New Feature
>          Components: contrib/*
>    Affects Versions: 2.4
>            Reporter: Uwe Schindler
>            Assignee: Michael McCandless
>         Attachments: LUCENE-1470.patch, LUCENE-1470.patch, LUCENE-1470.patch
>
>
> According to the thread in java-dev (http://www.gossamer-threads.com/lists/lucene/java-dev/67807
and http://www.gossamer-threads.com/lists/lucene/java-dev/67839), I want to include my fast
numerical range query implementation into lucene contrib-queries.
> I implemented (based on RangeFilter) another approach for faster
> RangeQueries, based on longs stored in index in a special format.
> The idea behind this is to store the longs in different precision in index
> and partition the query range in such a way, that the outer boundaries are
> search using terms from the highest precision, but the center of the search
> Range with lower precision. The implementation stores the longs in 8
> different precisions (using a class called TrieUtils). It also has support
> for Doubles, using the IEEE 754 floating-point "double format" bit layout
> with some bit mappings to make them binary sortable. The approach is used in
> rather big indexes, query times are even on low performance desktop
> computers <<100 ms (!) for very big ranges on indexes with 500000 docs.
> I called this RangeQuery variant and format "TrieRangeRange" query because
> the idea looks like the well-known Trie structures (but it is not identical
> to real tries, but algorithms are related to it).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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


Mime
View raw message