> Jukka Zitting wrote: > It should be fairly easy to optimize this by just updating > the changed path references in the search index for any nodes > that haven't been changed during the move.
I suppose updating the nodes that *have* changed. Furthermore, I do doubt wether this is that easy, because AFAIU you cannot update some lucene Field in a lucene document: the entire document needs to be reindexed. And this obviously gets very expensive for renaming some node with a large subtree below it. I must be missing something, but I really do not see how you can implement this efficiently without changing lucene code (which for a reason does never 'change' a Field but can only append a new document) -Ard > > BR, > > Jukka Zitting >
