[hibernate-issues] [Hibernate-JIRA] Reopened: (HSEARCH-201) IndexWriter settings meant for transactional operations won't be inherited by the settings meant for batch operations
Sanne Grinovero (JIRA)
noreply at atlassian.com
Thu Nov 5 09:01:13 EST 2009
[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sanne Grinovero reopened HSEARCH-201:
-------------------------------------
Forgot fixing a testcase (ShardsConfigurationTest) checking for the old behaviour
> 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: Sanne Grinovero
> Priority: Minor
> Fix For: 3.2.0.Beta1
>
>
> 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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list