[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-298?pag...
]
Emmanuel Bernard commented on HSEARCH-298:
------------------------------------------
Yes a warning seems more appropriate. but the doc should not mention usecompoundfile with
the tx or batch prefix. Let's avoid confusion.
Warn for dangerous IndexWriter settings
---------------------------------------
Key: HSEARCH-298
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-298
Project: Hibernate Search
Issue Type: Improvement
Affects Versions: 3.1.0.Beta2
Reporter: Sanne Grinovero
Assignee: Emmanuel Bernard
Priority: Trivial
Fix For: 3.1.0.CR1
Usually we let the user set all IndexWriter tuning settings in a different way in
"batch" mode or in "transaction" mode.
MAX_FIELD_LENGTH and USE_COMPOUND_FILE are actually not impacting only performance but
also how and what gets indexed,
so for MAX_FIELD_LENGTH we need to log a warning (because it sounds really wrong but
someone may like it),
and throw an exception for USE_COMPOUND_FILE (because this would be dangerous).
--
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