<p>Why not commit the Infinispan tx at lock release, instead of at indexwriter's commit?</p>
<p><blockquote type="cite">On 9 22, 2009 2:16 AM, "Łukasz Moreń" <<a href="mailto:lukasz.moren@gmail.com">lukasz.moren@gmail.com</a>> wrote:<br><br>Hi,<br><br>Thanks for explanation.<br>Maybe better I will concentrate on the first release and postpone distributed writing.<br>
<br>There is already LockStrategy that uses Infinispan. With using it I was wrapping changes made by IndexWriter in Infinispan transaction, because of performance reasons -<br>
on lock obtaining transaction was started, on lock release transaction was commited. Hovewer Ispn transaction commit on lock release is not good idea since IndexWriter calls index commit before lock is released(and ispn transaction is committed). <br>
I was thinking to override Workspace class and getIndexWriter(start infinispan tx), commitIndexWriter (commit tx) methods to wrap IndexWrite lifecycle, but this needs few other changes. Some other ideas?<br><br>Cheers,<br>
Lukasz<br><br><div class="gmail_quote">2009/9/21 Sanne Grinovero <span dir="ltr"><<a href="mailto:sanne.grinovero@gmail.com" target="_blank">sanne.grinovero@gmail.com</a>></span><p><font color="#500050">
>
> Hi Łukasz,
> you've rightful concerns, because the way the IndexWriter tries to
> achieve the l...</font></p></div><br>
</blockquote></p>