On Mar 13, 2009, at 18:45, Sanne Grinovero wrote:
I don't quite understand why, the new EventListenerREgister will be
bundled
with the IndexWork Listener always right? What backward compatible
mode do
you have?
So I'll discard compatibility with old configurations of Search? this
means so
2009/3/13 Emmanuel Bernard :
> hello
>
> On Mar 13, 2009, at 17:54, Sanne Grinovero wrote:
>
>> Hi,
>> about this issue (HSEARCH-178) I've implemented a patch following your
>> directions and
>> your idea is working very well, but I'm having some trouble about the
>
> Cool
>
>>
>> configuration
>>
hello
On Mar 13, 2009, at 17:54, Sanne Grinovero wrote:
Hi,
about this issue (HSEARCH-178) I've implemented a patch following your
directions and
your idea is working very well, but I'm having some trouble about the
Cool
configuration
of listeners.
An additional flush listener is needed;
Hi,
about this issue (HSEARCH-178) I've implemented a patch following your
directions and
your idea is working very well, but I'm having some trouble about the
configuration
of listeners.
An additional flush listener is needed; I've patched the
autoregistration but people
not using annotations wil
We discussed the issue with Sanne and for Hibernate Search we have a
workaround solution that does not penalize Hibernate Core. This
solution can be applied by everybody but it's not the easiest thing on
Earth.
The idea is to queue as you said but inside custom event listeners. In
our cas
Hi,
I've built a testcase for HSEARCH-178 (the loading collections in flush issue).
It succeeds when using a transaction, and fails with AssertionFailure
when not using one.
I've noticed that people reporting this problem
(among others http://forum.hibernate.org/viewtopic.php?p=2381840)
actually
Not sure what you mean by your "In theory it should not"... The very
nature of @PostUpdate is that it is going to be getting called during a
flush cycle...
wrt "is it possible to move the post* event after the flush?"...
There are really 2 answers.
1) According to the JPA spec, can we do
Ahhh
In theory it should not as Hibernate Search reads data in the
beforeCompletion phase.
Unless people do not apply changes in a transaction in which case we
need to execute the read in the post* event.
We will check whether or not people use surrounding transactions
(Hibernate aware Tx
Is this somehow different than the "attempt to load stuff into the PC
during flush" scenarios I see in any of these related issues?
-
Steve Ebersole
Project Lead
http://hibernate.org
st...@hibernate.org
Principal Software Engineer
JBoss, a division of Red Hat
http://jboss.com
http://redhat.com
