Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of javacache@gmail.com designates
 209.85.221.177 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=JvjjdcWEKXvs5zYFbU+e3nJidT0Ubmq8wCCIQEpThOBEKvh5F2CR5kdfQh08YOlyVD
         ln4E6nWfGdam2EJIE2JquGPllLr4MAjhb605tXSznZmcy1ZkBYlz8xLmxNCB/18QvT+m
         o1Cvh70SRPnGd2d/CWYU382wbtkHnpU7E+hFU=
MIME-Version: 1.0
In-Reply-To: <i2z867513fe1004222116rbe713d43y8ea108a9ced312fb@mail.gmail.com>
References: <SNT128-W3892D8F32F4D67F4D898889080@phx.gbl>
	 <p2p359a92831004221313o95e190c4zce55bfe26441e7dd@mail.gmail.com>
	 <i2z867513fe1004222116rbe713d43y8ea108a9ced312fb@mail.gmail.com>
Date: Sat, 24 Apr 2010 22:11:16 +0800
Message-ID: <r2s738ff0911004240711jf84a74efsd3e7bfeb7035b18d@mail.gmail.com>
Subject: Re: Indexing and Searching fields that have unique values
From: Ivan Liu <javacache@gmail.com>
To: java-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=0016363b9120faf34e0484fc1dc3

--0016363b9120faf34e0484fc1dc3
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable

I think Anshum is right=A1=A3
And may your range is too big and is sorting


2010/4/23 Anshum <anshumg@gmail.com>

> Hi Ravi,
>
> Adding to what Erick said, you could do index the numbers as numeric fiel=
ds
> instead of strings. This should improve things for you by a considerable
> amount.
> P.S: I'm talking with my knowledge on Java Lucene.
> --
> Anshum Gupta
> Naukri Labs!
> http://ai-cafe.blogspot.com
>
> The facts expressed here belong to everybody, the opinions to me. The
> distinction is yours to draw............
>
>
> On Fri, Apr 23, 2010 at 1:43 AM, Erick Erickson <erickerickson@gmail.com
> >wrote:
>
> > You have to provide more info, especially the search code you're
> > using. How many documents in your index? What are you measuring?
> >
> > Anything else you can think of that might help people diagnose
> > your issue.
> >
> > Also, consider asking on the .Net user's list.
> >
> > Known things to look for (in Java).
> > 1> Are you re-opening an index reader each time? Don't
> > 2> Are you sorting? If so, the first querie(s) will fill internal
> >   caches, this takes time. Time subsequent searches.
> >
> > HTH
> > Erick
> >
> > On Thu, Apr 22, 2010 at 3:58 PM, Ravi Patel <rpatel4@live.com> wrote:
> >
> > >
> > >
> > >
> > > Using Lucene.Net
> > >
> > >
> > >
> > > I've built an index of documents.
> > >
> > >
> > >
> > > The documents also have a unique identifier (my identifier, not the
> > lucene
> > > index's id).
> > >
> > > The unique identifers are also a sort order of new-ness (higher id
> values
> > > are newer)
> > >
> > >
> > >
> > > string my_id =3D"1234"
> > >
> > > doc.Add(new Field("id", my_id, Field.Store.YES,
> > Field.Index.UN_TOKENIZED));
> > >
> > >
> > >
> > > Searching for a particular id, or range searches are incredibly slow
> > >
> > >
> > >
> > >
> > >
> > > TermQuery query =3D new TermQuery(new Term("id", "1234"));
> > >
> > > searcher.Search(query)
> > >
> > >
> > >
> > >
> > >
> > > Any tips on how to speed up such an search?
> > >
> > >
> > >
> > > I'm also doing RangeSearches on lower / upper ids, and those are slow
> too
> > >
> > > _________________________________________________________________
> > > The New Busy is not the too busy. Combine all your e-mail accounts wi=
th
> > > Hotmail.
> > >
> > >
> >
> http://www.windowslive.com/campaign/thenewbusy?tile=3Dmultiaccount&ocid=
=3DPID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4
> >
>


--=20
=B3=E5=C0=CB=B0=E5
my blog:=B3=E5=C0=CB=B0=E5 <http://chonglangban.appspot.com/>
my site:Keji Technology <http://kejiblog.appspot.com/>

--0016363b9120faf34e0484fc1dc3--