[jira] [Resolved] (GORA-555) Improve Lucene query implementation with NumericRangeQuery

["Kevin Ratnasekera (JIRA)" <ji...@apache.org>]

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

Kevin Ratnasekera resolved GORA-555.
------------------------------------
    Resolution: Fixed

> Improve Lucene query implementation with NumericRangeQuery 
> -----------------------------------------------------------
>
>                 Key: GORA-555
>                 URL: https://issues.apache.org/jira/browse/GORA-555
>             Project: Apache Gora
>          Issue Type: Improvement
>          Components: gora-lucene
>    Affects Versions: 0.8
>            Reporter: Kevin Ratnasekera
>            Assignee: Xavier Sumba
>            Priority: Major
>             Fix For: 0.9
>
>          Time Spent: 3h 50m
>  Remaining Estimate: 0h
>
> There are performance benefits around NumericRangeQuery. Please notice comment on LuceneQuery implementation.
> {code}
>  //TODO: Change this to a NumericRangeQuery when necessary (it's faster)
>       String lower = null;
>       String upper = null;
>       if (getStartKey() != null) {
>         //Do we need to escape the term?
>         lower = getStartKey().toString();
>       }
>       if (getEndKey() != null) {
>         upper = getEndKey().toString();
>       }
>       if (upper == null && lower == null) {
>         q = new MatchAllDocsQuery();
>       } else {
>         q = TermRangeQuery.newStringRange(pk, lower, upper, true, true);
>       }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)