On 26/08/2014 15:10, Justin Edelson wrote: > ... > In this case, I think Thomas's suggestion makes much more sense. Let's > just add a property to the QID which allows an index to be restricted > to particular paths. > As said previously there was something in my idea that was not convincing me, hence I started the discussion here :)
After this discussion I'm as well for keeping the reindex as it is. We could in case enhance it, if not already, to make sure that if an index definition is under a specific path, only that path is traversed rather than the whole repo. As said: if not already. Nevertheless we have some use cases where we could need a workaround like it and I thought of a groovy script to be used in the oak-console. This script will receive in input a list of paths to parse and will reindex only those. We could have cases where an index is defined as root level but the end user knows that at the current stage it's actually used only by part of the content tree. In this way it won't be part of the core but a util that someone can use as not. Thoughts? Regards Davide
