[
https://issues.apache.org/jira/browse/OAK-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778844#comment-13778844
]
Jukka Zitting commented on OAK-1048:
------------------------------------
-0 on going through the node type API, as it's not optimized for the kinds of
access patterns needed here. If we want, we can wrap some of the common
NodeState access patterns to a utility class, but I would avoid introducing any
more indirection than that.
> 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
