]
Emmanuel Bernard resolved HSEARCH-385.
--------------------------------------
Resolution: Fixed
Fix Version/s: 3.2.0.CR1
I could not reproduce with the 3.2 version (available in
)
Some changes I made recently have fixed this problem I think. Particularly HSEARCH-476
Lazy ManyToOne association with @containedIn annotation cause HSearch
create entity index with documentId = 0
-------------------------------------------------------------------------------------------------------------
Key: HSEARCH-385
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-385
Project: Hibernate Search
Issue Type: Bug
Affects Versions: 3.1.0.GA, 3.1.1.GA
Environment: Hibernate 3.3.1.GA, Postgresql 8.3
Reporter: Grégoire Rolland
Priority: Critical
Fix For: 3.2.0.CR1
Attachments: hsearch.tar.gz
In a transaction, create Entity1 associated to one Entity2 (E1->E2 lazy oneToMany,
E2->E1 lazy manyToOne).
In antoher transaction, find Entity2, modify Entity2.
On commit, I get this log :
2009-07-02 11:42:18,791 TRACE
[org.hibernate.search.backend.impl.lucene.works.DeleteExtWorkDelegate] - Removing class
org.foo.hibernate.search.jira.Entity1#0 by id using an IndexWriter.
2009-07-02 11:42:18,792 TRACE
[org.hibernate.search.backend.impl.lucene.works.AddWorkDelegate] - add to Lucene index:
class
org.foo.hibernate.search.jira.Entity1#0:Document<stored/uncompressed,indexed<_hibernate_class:org.foo.hibernate.search.jira.Entity1>
stored/uncompressed,indexed<uid:0>
stored/uncompressed,indexed<entities2.uid:224136060>>
in the index :
1 document for Entity, with the correct Id, and 1 document with Id = 0, index is
corrupted.
See the test case for more info.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: