I was just wondering what is the best way, i.e. the best place, to implement indexing of a different entity when an index of another entity is triggered.

For example:

Say Object1 had changed and was set to be indexed but instead of indexing Object1 I index Object2.

Any help would be greatly appreciated.

I'm confused, why would you like to index an object which didn't change?

Thanks for replying :)

I am trying to index an object that represents a view that contains the data that has changed.

This gives me the best performance in terms of indexing and I also don't have the complications involved with embedded indexes and it contained in counterpart.

I was thinking that maybe I could override the listener and when class of object that had changed was of type Object1.class I could just pass in the Object2.class. But is there a better way? I read in another of your posts that FullText..EventListener is going to become final, the comments say this as well, so overriding it is not the best idea.

Is there another point, a better point, I could extend Hibernate Search to accomplish this?

Or would it be better to create a custom Worker?

If anyone can offer a suggestion I will go away try it and report back.. Please :)

Hello, you could try to use a custom JPA entitylistener, you don't need to extend Search's implementation, and then load your view-entity and send the additional work to the backend. I didn't try it, feedback welcome ;)