Return-Path: X-Original-To: apmail-lucene-dev-archive@www.apache.org Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EE7E511604 for ; Wed, 30 Jul 2014 18:42:43 +0000 (UTC) Received: (qmail 28597 invoked by uid 500); 30 Jul 2014 18:42:40 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 28468 invoked by uid 500); 30 Jul 2014 18:42:40 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 28247 invoked by uid 99); 30 Jul 2014 18:42:40 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Jul 2014 18:42:40 +0000 Date: Wed, 30 Jul 2014 18:42:40 +0000 (UTC) From: "Michael McCandless (JIRA)" To: dev@lucene.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (LUCENE-5860) Use Terms.getMin/Max to speed up range queries/filters MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/LUCENE-5860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-5860: --------------------------------------- Attachment: LUCENE-5860.patch Patch. I also hit and fixed a bug in MemoryIndex's TermsEnum seek-by-ord ... > Use Terms.getMin/Max to speed up range queries/filters > ------------------------------------------------------ > > Key: LUCENE-5860 > URL: https://issues.apache.org/jira/browse/LUCENE-5860 > Project: Lucene - Core > Issue Type: Improvement > Reporter: Michael McCandless > Assignee: Michael McCandless > Fix For: 5.0, 4.10 > > Attachments: LUCENE-5860.patch > > > As of LUCENE-5610, Lucene's Terms API now exposes min and max terms in > each field. I think we can use this in our term/numeric range > query/filters to avoid visiting a given segment by detecting up front > that the terms in the segment don't overlap with the query's range. > Even though block tree avoids disk seeks in certain cases when the > term cannot exist on-disk, I think this change would further avoid > disk seeks in additional cases because the min/max term has > more/different information than the in-memory FST terms index. -- 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