You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Davide Giannella (JIRA)" <ji...@apache.org> on 2015/05/18 16:30:01 UTC

[jira] [Closed] (OAK-2814) Refactor the optimize logic regarding path include and exclude to avoid duplication

     [ https://issues.apache.org/jira/browse/OAK-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Davide Giannella closed OAK-2814.
---------------------------------

Bulk close for 1.0.14

> Refactor the optimize logic regarding path include and exclude to avoid duplication
> -----------------------------------------------------------------------------------
>
>                 Key: OAK-2814
>                 URL: https://issues.apache.org/jira/browse/OAK-2814
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>            Priority: Minor
>              Labels: technical_debt
>             Fix For: 1.3.0, 1.0.14
>
>         Attachments: OAK-2814-v1.patch
>
>
> {{ObservationManagerImpl}} has a optimize method which process the list of includes and excludes and removes redundant clauses. That logic is now also being used in index filtering (OAK-2599) and is getting duplicated.
> Going forward we need to refactor this logic so that both places can use it without copying. Possibly making it part of PathUtils
> [~mduerig] Also suggested to further optimize
> bq. Also PathFilter#optimise could be further optimised by removing entries that subsume each other (e.g. including /a/b, /a is the same as including (/a. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)