Extends FullTextIndexEventListener

ggrossetie · **Joined:** Fri Jul 20, 2012 10:19 am **Posts:** 7

Hi,

I tried to replace the FullTextIndexEventListener with my custom listener. I first used a duplication strategy to avoid the registration of FullTextIndexEventListener.
The following code in ContextHelper is problematic because my custom listener need to extends the FullTextIndexEventListener :

Code:

                //FIXME this sucks since we mandate the event listener use
      for ( PostInsertEventListener candidate : listeners ) {
         if ( candidate instanceof FullTextIndexEventListener ) {
            listener = (FullTextIndexEventListener) candidate;
            break;
         }
      }

The code comment below scare me because my code will soon break :

Code:

//TODO make this class final as soon as FullTextIndexCollectionEventListener is removed.
public class FullTextIndexEventListener

Can you give me the right direction to take to be compatible with the future version of Hibernate ?

Thanks,
Guillaume.

sanne.grinovero · **Posted:** Thu Aug 09, 2012 4:27 am

Hi Guillaume,
could you explain why you need to extend the FullTextIndexEventListener?

As you have seen from the comment we would like to make it final to cleanup several code areas, but to be fair that comment has been there for long and we never actually did it as we want to make sure all use cases are covered in some way.

Since we introduced conditional indexing [1] I thought we have all use cases covered, so please tell us what you need to do?

1 - http://in.relation.to/Bloggers/HibernateSearch410FinalConditionalIndexingAndMore

kanwuin1 · **Joined:** Mon Aug 13, 2012 2:40 am **Posts:** 1

Thank you for this article.Really impressed! Everything is very, very clear, open is a description of the problem. It contains the information.

ggrossetie · **Joined:** Fri Jul 20, 2012 10:19 am **Posts:** 7

Sorry for the late reply and thanks for the link.
We're using custom event listener because in our context non-indexed entity must trigger reindexing.
Example :

Code:

Customer {
String name;
}
@Indexed
Invoice {
String number;
Long customerId;
}

If the customer name changed we need to reindex the "Invoice index" which contains the customer name. We work on a SOA architecture with separated databases (so no direct reference between Invoice and Customer).
We're using Lucene to bridge/aggregate our data but I think this is not the best use of this technology maybe a data grid/nosql solution will be more suitable...

Guillaume.