Hi, I understand Hibernate Search uses @ID field as Document Id when using JPA. However, in our case, we have a surrogate id as primary key and a natural (business) ID as another field. Because the way our business works, the underlying DB data can be changes in two ways: incremental changes via Hibernate and a overall data replacement via SQL (bypassing Hibernate). No matter how the data is changed, the natural ID should always refer to the same entity in real world. but the surrogate ID will be changes since it is auto generated.

What I want to do is to tell Lucene to index the natural ID rather than the surrogate ID so that even though the underlying data is changed, the search result I got from using the old index is still valid.

Is there a way in Hibernate Search to use a field as DocumentId while having the @ID annotation on another field?

I think that the Hibernate Search and Validator board is where you should post this question.

Thanks for the heads up. I reposted it here.
Think this thread can be deleted