Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Error: there are more terms than documents...
Date: Thu, 23 Apr 2009 16:31:04 -0400
Message-ID: 
 <036829964E44B44F80A0D168BB9849E1018C624B@VOO-EXCHANGE04.internal.sungard.corp>
In-Reply-To: <e05f0fd10904231300u7cadf7c3pe559d1c0ce2dd93c@mail.gmail.com>
Thread-Topic: Error: there are more terms than documents...
Thread-Index: AcnETlAO8TAZH58/RMys91dVvLCNLgAARmlg
From: <Bill.Chesky@sungard.com>
To: <java-user@lucene.apache.org>

Doron, thanks for the reply.

> Is it possible that, for at least one document, multiple "objectId"
fields
> were created?
> This would also create this problem.

I read that online as well.  I don't think so.  We do have an update
process that updates the index.  During the update process we have the
call:

// create new doc object ... objectId will always be the same as before
but // other fields may change
Document doc =3D getDocument(s); =20
// replace old doc for objectId w/ new
indexWriter.updateDocument(new Term("objectId", s.getObjectId()), doc);

However, the getDocument() method is the same method that we use to
create a brand new document when building the index from scratch.  And
I'm sure we only create the "objectId" field once in that method. =20

Unless maybe I'm misunderstanding something about the
IndexWriter.updateDocument() method.  I thought it would delete all
documents that matched the Term passed and add a new one.

Unless maybe there is an issue with my Term argument passed to
updateDocument and it's really not matching the way I think it is and so
we end of with two different documents with the same value in the
"objectId" field.  Could this situation cause the exception?

> The printed document object is the same document object that was
created
> for indexing. But when a document is read from the index (via
IndexReader
> API)
> it will only contain the stored fields. For instance, assume that at
search
> time you would like to get the URL of a result document and display it
to the user.
> For this
> you can at indexing time add the URL to a stored field.
>
> Doron

Ah I think I understand.  I was printing those docs out as I stored
them.  That makes total sense now.  Thanks for the help.

regards,

Bill


---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org