]
Sanne Grinovero updated HSEARCH-743:
------------------------------------
Fix Version/s: (was: 4.0)
4.0.0.Alpha1
Unify configuration settings for batch and transaction indexwriter
settings
---------------------------------------------------------------------------
Key: HSEARCH-743
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-743
Project: Hibernate Search
Issue Type: Remove Feature
Components: documentation, engine
Reporter: Sanne Grinovero
Assignee: Sanne Grinovero
Fix For: 4.0.0.Alpha1
In the Hibernate Search 3.0 era a new IndexWriter would have been opened for each
"List of Work" (set of index operations) to be performed: each index change
would acquire the index lock, each changeset could not be applied in parallel. So to be as
quick as possible with these frequent and small index changes, you'd likely wanted an
"interactive IndexWriter configuration", significantly different than the
settings being used for batch indexing: so Hibernate Search had two different sets of
parameters which could be set.
Since 3.1 the back-end became a bit better: updates to different indexes would be applied
in parallel, but still for each changeset a new IW was opened and released.
During 3.2 we introduced the massindexer which provides a new alternative to the batching
use case, and also HSEARCH-327 which basically requires to never change the IndexWriter
configuration during non-massindexer work: since then if this option is enabled we might
be inconsistent about which options are being used - and definitely doesn't make much
sense anymore.
We agreed at that timeframe that it should be deprecated, and warnings have been logged
since then on some options which really needed consistency - but it was never removed to
keep compatibility: removing now for version 4.0
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: