<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><br><div>Begin forwarded message:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><b>From: </b></font><font face="Helvetica" size="3" style="font: 12.0px Helvetica">Sanne Grinovero <<a href="mailto:sanne.grinovero@gmail.com">sanne.grinovero@gmail.com</a>></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><b>Date:<span class="Apple-converted-space"> </span></b></font><font face="Helvetica" size="3" style="font: 12.0px Helvetica"> February 18, 2009 15:41:06<span class="Apple-converted-space"> </span>CEST</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><b>To: </b></font><font face="Helvetica" size="3" style="font: 12.0px Helvetica">Emmanuel Bernard <<a href="mailto:emmanuel@hibernate.org">emmanuel@hibernate.org</a>></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><b>Subject: </b></font><font face="Helvetica" size="3" style="font: 12.0px Helvetica"><b>Re: [hibernate-dev] Hibernate Search: configure the LockingFactory</b></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div> </div><div>2009/2/18 Emmanuel Bernard <<a href="mailto:emmanuel@hibernate.org">emmanuel@hibernate.org</a>>:<br><blockquote type="cite"><br></blockquote><blockquote type="cite">On Feb 18, 2009, at 11:49, Sanne Grinovero wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">The "none" doesn't protect at all, so you have to make sure to never open<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">a second indexwriter or use any indexwriter when you are using an<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">indexreader<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">to make changes.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Sounds a bit dangerous IMHO but I don't think we should stop people<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">shooting<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">at their own feet.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">As we are enforcing a single indexwriter and all our indexreaders are<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">readonly since<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">last release, you may want to use it: I think the current design of<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">H.Search<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">doesn't stop us from offering this option.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I've added a note in the docs to use it only if you really understand it.<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Well, if you are only using Hibernate Search to access indexes (90% of our<br></blockquote><blockquote type="cite">user base) and you deploy on one server (80% of our user base), none is a<br></blockquote><blockquote type="cite">compelling solution right? (that's 70% of deployments :))<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote>yes I think it could be used; but I don't think the speed<br>improvement is anything you could measure, and it is dangerous.<br>Bad things will happen to your index if you don't know about it and are in the<br>unlucky 30% of deployments.<br>Also I'm not sure what crazy things could be using the "Native Lucene" APIs<br>exposed...<br>But now at least we don't stop anybody from trying it.<br></div></blockquote></div><br></body></html>