wrong Similarity used when sharing index among entities
-------------------------------------------------------
Key: HSEARCH-271
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-271
Project: Hibernate Search
Issue Type: Bug
Components: engine
Affects Versions: 3.1.0.Beta1
Reporter: Sanne Grinovero
When the same IndexWriter is used during a transaction commit for two or more entities
(sharing the same index) but having different Similarities,
the Similarity used is the one from the first entity to be indexed.
No warning is logged and it's hard to recognize without being a paranoid Similarity
expert...
If the two Entities share an object hierarchy, then Search correctly throws an exception
during startup.
Should we throw an exception also on index sharing or solve it to support different
Similarities even on different obejcts being part of same tree? (to be consistent)
--
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