On Thu, Apr 23, 2009 at 11:52 PM, wrote:
> I figured it out. We are using Hibernate Search and in my ORM class I
> am doing the following:
>
> @Field(index=Index.TOKENIZED,store=Store.YES)
> protected String objectId;
>
> So when I persisted a new object to our database I was inadvertently
> cre
I figured it out. We are using Hibernate Search and in my ORM class I
am doing the following:
@Field(index=Index.TOKENIZED,store=Store.YES)
protected String objectId;
So when I persisted a new object to our database I was inadvertently
creating a document in the Lucene index with the tokenized a
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
On Thu, Apr 23, 2009 at 10:39 PM, wrote:
> I'm getting a strange error when I make a Lucene (2.2.0) query:
>
> java.lang.RuntimeException: there are more terms than documents in field
> "objectId", but it's impossible to sort on tokenized fields
>
Is it possible that, for at least one document,
Sorry for that terrible formatting. Let me try again.
==
Hello,
I'm getting a strange error when I make a Lucene (2.2.0) query:
java.lang.RuntimeException: there are more terms than documents in field
"objectId", but it's impossible to sort
