[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-318?pag... ] Hardy Ferentschik commented on HSEARCH-318: ------------------------------------------- Nothing. This must be a typo. Juraci is working on getting the test working on different database types. There is no relation. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-318?pag... ] Sanne Grinovero commented on HSEARCH-318: ----------------------------------------- Could you describe it a bit more? Maybe I can help, but I'm not understanding what you'd like to do. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-318?pag... ] Hardy Ferentschik updated HSEARCH-318: -------------------------------------- Summary: Extend IndexWriterSetting to take additional constructor arguement (was: Extend IndexWriterSetting to include a flag indicating whether it makes sense to have different settings for batch and index) I must have been on drugs when I wrote the original description for this issue :) It only started to make sense to me once I looked at the linked issue. At the moment the IndexWriterSetting constructor only takes the configuration key name. I was suggesting to add another parameter to the constructor which indicates whether this particular option can have different values for batch vs transactional mode. As mentioned in the linked issue having different values for use_compound_file in batch and transactional mode should throw an exception. This additional parameter could be another emum: public enum ModeDisparity { ALLOWED, WARN, THROW_EXCEPTION } Given that the linked issue is already resolved this might be obsolete now. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-318?pag... ] Sanne Grinovero updated HSEARCH-318: ------------------------------------ Summary: Extend IndexWriterSetting to take additional constructor argument (was: Extend IndexWriterSetting to take additional constructor arguement) -- 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