Hi Marc, dirty checking in Hibernate Search only inspects indexed properties, and reindexes only if one of the indexed properties is flagged as dirty (by Hibernate Core). So having removed indexed properties with a smaller set of paths by using the new includePaths, this would also reduce the set of properties being inspected to see if indexing should be triggered. Bottom line, this should work already..
Feel free to write a test to verify this, I'd be glad to include it: this is a nice side-effect which I expect to work but we didn't verify. Sanne On 7 March 2012 15:51, Marc Schipperheyn <m.schipperh...@gmail.com> wrote: > With the new includePaths on IndexedEmbedded is it now possible to have a > more specific "dirty" check? Since you are indexing less paths, it stands > to reason that less objects will need to be reindexed because they are > (potentially) "dirty" during a save operation. I'm just curious if new > opportunities arise to reduce the number of queries executed here > > Marc > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
