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 "Jukka Zitting (JIRA)" <ji...@apache.org> on 2013/11/12 17:51:17 UTC

[jira] [Resolved] (OAK-1048) Unify node type management in the query index impls

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

Jukka Zitting resolved OAK-1048.
--------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 0.14)
                   0.11

Done partially in revision 1536366 with the new TypePredicate class.

However, in the higher level code (SelectorImpl, etc.) the node type information is used in more complex ways (need to be able to access subtype names for example to construct a Lucene query) that become tricky to do efficiently in a generic utility class.

Thus I'll leave the higher level code as-is and resolve this as Fixed based on revision 1536366.

> Unify node type management in the query index impls
> ---------------------------------------------------
>
>                 Key: OAK-1048
>                 URL: https://issues.apache.org/jira/browse/OAK-1048
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, query
>            Reporter: Alex Parvulescu
>            Assignee: Jukka Zitting
>             Fix For: 0.11
>
>
> Currently the query index implementations that are node type aware access this info directly from the NodeState by reading the child nodes.
> This is fragile (the node type managemet impl may change structure and break the tests), and also may hide some access patterns which are node-type related behind normal _getChildNode_ calls.



--
This message was sent by Atlassian JIRA
(v6.1#6144)