[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-361) Only index an entity if an indexed property has changed

Tom Waterhouse (JIRA) noreply at atlassian.com
Mon Dec 27 14:15:05 EST 2010


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

Tom Waterhouse commented on HSEARCH-361:
----------------------------------------

This is a big issue for embedded collections.  We have nested associations for which non-indexed field updates are causing a load of all related entities.  

In the case where indexed fields are updated the related index update cost makes sense.  When updating a non-indexed field of an embedded object the expectation is that no extra index processing will occur.

> Only index an entity if an indexed property has changed
> -------------------------------------------------------
>
>                 Key: HSEARCH-361
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-361
>             Project: Hibernate Search
>          Issue Type: New Feature
>            Reporter: Emmanuel Bernard
>             Fix For: 3.4.0
>
>
> PostUpdateEvent has state and oldState
> and EntityPersister has getPropertyNames() and findDirty()

-- 
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

        


More information about the hibernate-issues mailing list