[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-5) Only index an entity when it's index properties have physically changed

[Sanne Grinovero (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39897#action_39897 ] 

Sanne Grinovero commented on HSEARCH-5:
---------------------------------------

Hi Stephane, no problem we'll be able to talk about this next week ;)
I agree point 4) is not a great deal I'm just trying to analyse all details. I'm still not convinced about hashing. If ideal hashing algorithms could be implemented, we could write the inverse function of them, and this would proof that any information could be compressed in a smaller form - against Shannon's source coding theorem - and ultimately I could encode any information into "0" or "1", clearly absurd. Definitely, a high quality hashing implementation has a low ratio of collisions, but zero collisions is impossible. Of course, we could agree that an int has enough space for this being kinda unlikely.

> 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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira