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 "Alex Parvulescu (JIRA)" <ji...@apache.org> on 2013/09/27 10:32:04 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 ]

Alex Parvulescu resolved OAK-1048.
----------------------------------

    Resolution: Not A Problem

ok, fair enough. the gain I was looking for in code clarity may be surpassed by the slowness of the apis.

I took some small bits of improvement over to OAK-1051.

closing this as not a problem.
                
> 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: Alex Parvulescu
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira