Keeping an index up to date without @ContainedIn

mschipperheyn · **Joined:** Wed Nov 05, 2003 7:22 pm **Posts:** 211

Hi,

In some cases, you have a oneway ManyToOne Relation to an object that doesn't (shouldn't) have a return reference. See the example below.
When you update this Poll object, you want the containing index to be updated also. Is there a scenario for this that doesn't involve creating a reference in the Poll object to the Post object with @ContainedIn?

Arguably, one would like Hibernate Search to monitor changes for all the leaves that are handed to it through IndexedEmbedded automagically.

Code:

@Entity
@Table
@Indexed
public class Post{   
   
   @ManyToOne(cascade=CascadeType.ALL,fetch=FetchType.LAZY)
   @JoinColumn(name="FK_PollId", nullable=true,updatable=false)
   @IndexedEmbedded
   public Poll getPoll() {
      return poll;
   }

}

@Entity
@Table
public class Poll {

   @OneToMany(cascade=CascadeType.ALL,fetch=FetchType.LAZY,mappedBy="poll",orphanRemoval=true)
   @IndexedEmbedded(prefix="question.")
   public List<Question> getQuestions() {
      return questions;
   }

}

@Entity
@Table
public class Question {

   @Column(name="voteCount")
   @Field(index=Index.NO,store=Store.YES)
   @org.hibernate.annotations.Index(name="idxPollCount")
   public int getCount() {
      return count;
   }
}

Kind regards,
Marc

mschipperheyn · **Joined:** Wed Nov 05, 2003 7:22 pm **Posts:** 211

So, yes, you can add this to Poll

Code:

@OneToOne(optional=false,fetch=FetchType.LAZY,mappedBy="poll")
@ContainedIn
public Post getPost(){
   return post;
}

But as far as I'm concerned, Hibernate Search now forced me to tightly couple something that I don't want to tightly couple. But ok, it now works.

However, when I modify a Poll object, I see all of the other (some Lazy, some Extra Lazy because they never ever should be loaded as a whole) unchanged children of Post being loaded by Hibernate, presumably to recreate the entire index record, when only a single field changed. That's a performance killer and it puzzles me each and every time I see something like that happen (I got rid of classbridges alltogether for this very reason).

Any ideas (using Hsearch 4.1.1)?

Cheers,
Marc

mschipperheyn · **Joined:** Wed Nov 05, 2003 7:22 pm **Posts:** 211

When I debug this, I basically see Hibernate correctly identifying the dirty relationships and updating them.
However, when we hit Hibernate Search
PostTransactionWorkQueueSynchronization.beforeCompletion(84) | Processing Transaction's beforeCompletion() phase: org.hibernate.search.backend.impl.PostTransactionWorkQueueSynchronization

Boom! Everything gets initialized, including all the non-dirty and extra lazy items. It's basically a full reindex instead of an update.

Really puzzling and it looks like incorrect behaviour. Any suggestions are appreciated.

Kind regards,
Marc

sanne.grinovero · **Posted:** Mon Sep 03, 2012 9:03 am

Quote:

Arguably, one would like Hibernate Search to monitor changes for all the leaves that are handed to it through IndexedEmbedded automagically.

Arguably I would agree with you, that would be nice. But it's not implemented.

For other readers: we continue discussion on lazy loading in https://forum.hibernate.org/viewtopic.php?f=9&t=1023973