Hi, On Jan 21, 2008 12:51 PM, Ard Schrijvers <[EMAIL PROTECTED]> wrote: > > 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.
Yes. :-) What I was trying to express were nodes that are moved but not otherwise changed. I.e. the only modification is the path change. > 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) Good point. Though it shouldn't be too difficult to enhance Lucene to reuse a previously analyzed and indexed document as the basis of a slightly modified version. There's also the new document payload feature that might be useful in this regard. BR, Jukka Zitting
