Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of anithian@gmail.com designates
 74.125.92.24 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:from:date:message-id:subject:to:content-type;
        b=QYXqNHqe1m6lrsLHRFmrVy8D5gxJTA5u3h3FfRroAbz9TlBKog0O+HVYsARfi/DDkb
         20kMkx5PzRNtRqNwvbShwNiFfxBsQT6oMaT/srzOmDJ+MXuIq6+oUYl9lWUhmENskfPc
         bIfqRrD170eIJk/2En66fQTHhyhpOJM5IHfqU=
MIME-Version: 1.0
From: Amit Nithian <anithian@gmail.com>
Date: Mon, 8 Jun 2009 11:34:03 -0700
Message-ID: <9426f1770906081134m21d98915q7147223b0bca88c8@mail.gmail.com>
Subject: Trie Patches- Backportable?
To: solr-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=001e680f1ac4b7c53e046bda7dd4

--001e680f1ac4b7c53e046bda7dd4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi,
I am still using Solr 1.2 with the Lucene 2.2 that came with that version of
Solr. I am interested in taking advantage of the trie filtering to alleviate
some performance problems and was wondering how back-portable these patches
are?

I am also trying to understand how the Trie algorithm cuts down the number
of term queries compared to a normal range query. I was at the recent Bay
Area lucene/solr meetup where this was covered but missed some of the
details.

I know the ideal case is to upgrade to a newer Solr/Lucene but we are
resource constrained and can't devote the time right now to test and upgrade
our production systems to a newer Solr.

Thanks!
Amit

--001e680f1ac4b7c53e046bda7dd4--