If I update an Hibernate entity, all the indexed fields are re-indexed? Well, perhaps this is not the question because I have seen this is true. Lucene can't update a Document, but you need to delete it and add again with the new values.

My problem is that I have a indexed field marked as @Transient and after the update, this field is missing from Lucene index. This is collateral effect of the delete-and-create "update" method. This @Transient field is used to store the extracted text from a PDF, for example. The whole entity is used to store files, as you can guess. Let's call the entity "StoredFile".

I wonder if is possible to create a custom FieldBridge which get the old indexed field content and copy to the new created Lucene Document. The final objective is to avoid the text extraction from PDF and the following indexing process each time a property of the "StoredFile" changes.

Or perhaps there is a better solution?

Hi,

@Transient does not have an effect on indexing. If the property has a value when getting indexed, this value should be available in the Lucene Document for searching.

One problem could be if you persist the entity for the first time (with some data in the transient field which gets indexed) and then load the entity later again from the database. In this case the transient field is of course empty. If you now modify something else in the entity and persist again, the transient field is empty and hence nothing will be indexed and the old indexed value is lost. Is this your problem?

--Hardy

Yes, this is my problem? If there is an event thrown when Hibernate Search, commits the modification into the Lucene index, should be nice to attach a class to manage this case. I would retrieve the Lucene's document previously stored before deletion. I expect I can explain it better:

1.- Make a modification to the entity
2.- Make it persist -> Hibernate.Session.update(entity)
3.- Hibernate Search call to Lucene.Index to delete the old Lucene.Document and create a new one.

In step 3, I would like to intercept the call to Lucene and fill the missing entity properties again. Is this possible o I should use Lucene directly?

Regards.

There is no event in Hibernate Search, but there are Hibernate/JPA events you could use. If you are using JPA you could for example use @PostLoad.

Ok, thanks.