[GORA-555] Improve Lucene query implementation with NumericRangeQuery

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.8
• Fix Version/s: 0.9
• Component/s: gora-lucene
• Assignee: Xavier Sumba
• Reporter: Kevin Ratnasekera
• Created: 18/Mar/19 14:08
• Updated: 30/Apr/19 07:25
• Resolved: 30/Apr/19 07:25

Description

There are performance benefits around NumericRangeQuery. Please notice comment on LuceneQuery implementation.

 //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);
      }

Issue Links

• links to: GitHub Pull Request #158