On Feb 18, 2009, at 11:49, Sanne Grinovero wrote:
The "none" doesn't protect at all, so you have to make
sure to never
a second indexwriter or use any indexwriter when you are using an
to make changes.
Sounds a bit dangerous IMHO but I don't think we should stop people
at their own feet.
As we are enforcing a single indexwriter and all our indexreaders are
last release, you may want to use it: I think the current design of
doesn't stop us from offering this option.
I've added a note in the docs to use it only if you really
Well, if you are only using Hibernate Search to access indexes (90% of
our user base) and you deploy on one server (80% of our user base),
none is a compelling solution right? (that's 70% of deployments :))