In a repository which has indexing enabled, when a node is being updated and only has property changes, the current code will reindex all the node's children.

This is a bug which, once fixed, should (significantly) improve performance because the only case when after a node update the children should be re-indexed is only when the path of the parent node has changed. In all other cases the children should never the "touched" .