There was a thread on this exact issue.If you are using 2.3, the payload api would help with that.
-John On Thu, Feb 14, 2008 at 3:59 AM, Gauri Shankar <[EMAIL PROTECTED]> wrote: > Thanks a lot for both of you. > > yes, I am talking about internally assigned document id. > > Erick : I am already using the unique id into the index mapped to one of > our > DB's primary key to uniquely identify the docs from index. Now to get the > value of this unique field i need to call getDocumet(). But when the > resultset is too large than this step is very slow as I am calling > getDocument for each hit. Now I am using the FIELDCACHE and that has > improved a lot. But I am thinking If I can find a way so that docId can be > my unique ids and that will super optimize our search. > Any suggestions?? > > Thanks, > Gauri Shankar > > On Sat, Feb 9, 2008 at 9:10 PM, Erick Erickson <[EMAIL PROTECTED]> > wrote: > > > If you're referring to the internally-assigned document id, I don't > think > > there is a way. Assuming you're trying to assign one yourself or some > > such. > > > > From all the discussions I've seen, I don't think there's even a faint > > possibility that controlling this will be added to Lucene. Note that > > existing IDs change as your index changes. > > > > Why do you care? What problem are you trying to solve? One common > > suggestion is to create your own field (as Patrick suggests) that > contains > > your own unique ID. Using TermEnum/TermDocs will give you efficient > > ways of going from your unique ID to a docID... > > > > Best > > Erick > > > > On Feb 9, 2008 7:38 AM, Gauri Shankar <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > > > > > I would like to get the control over the docId field from my code. Can > > > anyone suggest some way for doing the same? > > > > > > > > > -- > > > Warm Regards, > > > Gauri Shankar > > > > > > > > > -- > Warm Regards, > Gauri Shankar >
