yes, that's the whole point :)
the doc will have to be adjusted probably mark the feature as
deprecated.
On Jun 21, 2008, at 18:05, Sanne Grinovero wrote:
looks like a very good idea, does this mean people don't need to do
this (taken from docs):
"It is critical that batchSize in the previ
Bernard <[EMAIL PROTECTED]>
Subject: [hibernate-dev] [Hibernate Search] session.flushToIndexes()
To: hibernate-dev@lists.jboss.org
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
I never liked the way we work around mass insertion and OOME tod
looks like a very good idea, does this mean people don't need to do this
(taken from docs):
"It is critical that batchSize in the previous example matches the
batch_size value described previously."
?
Should we remove the option and references from documentation?
2008/6/21 Emmanuel Bernard <[EMAIL
I never liked the way we work around mass insertion and OOME today
hibernate.search.worker.batch_size has many drawbacks
- the value is not accessible programatically
- it applies to any operations regardless of mass indexing
- it is used 99% of the time in close conjunction with a % and
ses
