[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-5?page=...
]
Stephane Epardaud commented on HSEARCH-5:
-----------------------------------------
@Emmanuel: not enough beer certainly ;)
@Sanne: Sorry about the late answer :(
1) It is unlikely I'll have time to update my patch to the current code base until
there is a reason for my employer to pay me to do this.
2) If two different values hash to the same hash, then your hashing function is bad ;)
3) You make a good point, but I was entirely unable to retrieve enough info from Hibernate
to construct the hash of the indexed entities prior to the current change, which is why it
is stored at all. Otherwise I would construct both hashes (old/new) while reindexing.
4) Wasted space in the index is not a problem for me, especially compared with the order
of magnitude we gained when our entities stopped propagating changes to all the other
indexes where they were embedded even though nothing indexed changed.
Only index an entity when it's index properties have physically
changed
-----------------------------------------------------------------------
Key: HSEARCH-5
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-5
Project: Hibernate Search
Issue Type: New Feature
Components: engine
Reporter: Emmanuel Bernard
Priority: Minor
Attachments: hibernate-search-3.0.1.GA-hashing_patch.diff,
hibernate-search-3.0.1.GA-id_field_patch.diff
--
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