[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-201?pag...
]
Sanne Grinovero reassigned HSEARCH-201:
---------------------------------------
Assignee: Emmanuel Bernard
assigning to Emmanuel to get his opinion.
either
1) we do the change and write a red warning in the documentation
2) we reject this
3) we find a way to implement the new one and deprecate the old way of setting the values,
so we can give users some time to update configuration files. How?
3 - A) we change the property name, so we can use the new one, and still support the
old logging some warning.
3 - B) I don't know.. ideas?
My understanding from our last chat is that you would like 3B, but I can't code that
:-)
I'd suggest taking 1) or 2).
IndexWriter settings meant for transactional operations won't be
inherited by the settings meant for batch operations
---------------------------------------------------------------------------------------------------------------------
Key: HSEARCH-201
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-201
Project: Hibernate Search
Issue Type: Deprecation
Components: engine
Reporter: Sanne Grinovero
Assignee: Emmanuel Bernard
Priority: Minor
Fix For: 3.2.0
Currently if a property has been set for "transaction" but not for
"batch", the batch operation will use the same setting as defined in the
transaction property;
It appears to be a bit confusing and difficult to understand which settings are being
set.
Current inheritance is to be considered "deprecated" and will be disabled,
please begin declaring both values independently.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira