[discuss] IndexEditor and excluding paths to reduce indexing time

[Chetan Mehrotra <ch...@gmail.com>]

Hi Team,

Currently an IndexEditor would traverse the whole repo (or subtree if
configured in non root path) to perform reindex. Depending on the repo
size this process can take quite a bit of time. It would be faster if
an IndexEditor can exclude certain paths from traversal

Consider an application like Adobe AEM and an index which only index
dam:Asset. Such nodes would not be found in paths like /var,
/jcr:system which might contain lots of node. If the index editor
skips such path then lots of redundant traversal can be avoided.

For now I was thinking to add this in say LuceneIndexEditor. Or if it
can be implemented as a wrapper like SubtreeEditor then that would
also work.

Thoughts?

Chetan Mehrotra

Re: [discuss] IndexEditor and excluding paths to reduce indexing time

[Davide Giannella <da...@apache.org>]

On 05/12/2014 11:32, Tommaso Teofili wrote:
> Hi Chetan
>
> sounds a good idea to me, where would you define that?
> Maybe in the index definition, right?
>
+1 for having a String[] property for it. I like `excludePaths` :)

Cheers
Davide

Re: [discuss] IndexEditor and excluding paths to reduce indexing time

[Tommaso Teofili <to...@gmail.com>]

Hi Chetan

sounds a good idea to me, where would you define that?
Maybe in the index definition, right?

Regards,
Tommaso



2014-12-05 10:41 GMT+01:00 Chetan Mehrotra <ch...@gmail.com>:

> Hi Team,
>
> Currently an IndexEditor would traverse the whole repo (or subtree if
> configured in non root path) to perform reindex. Depending on the repo
> size this process can take quite a bit of time. It would be faster if
> an IndexEditor can exclude certain paths from traversal
>
> Consider an application like Adobe AEM and an index which only index
> dam:Asset. Such nodes would not be found in paths like /var,
> /jcr:system which might contain lots of node. If the index editor
> skips such path then lots of redundant traversal can be avoided.
>
> For now I was thinking to add this in say LuceneIndexEditor. Or if it
> can be implemented as a wrapper like SubtreeEditor then that would
> also work.
>
> Thoughts?
>
> Chetan Mehrotra
>