[
https://issues.apache.org/jira/browse/OAK-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795111#comment-13795111
]
Alex Parvulescu commented on OAK-1052:
--------------------------------------
bq. executionContext.getRootState()
this would affect the AbstractRoot call where the _rootState_ object appears to
be coming from the unsecured builder, so I don't think passing that around is
good.
What I'm wondering thought is if it would work the other way around, remove the
node state and just rely on the tree. But that would touch a lot of code in the
query engine that works on NodeStates.
> Introduce execution context for executing queries
> -------------------------------------------------
>
> Key: OAK-1052
> URL: https://issues.apache.org/jira/browse/OAK-1052
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Reporter: Michael Dürig
> Attachments: OAK-1052.patch
>
>
> In OAK-1037 we found that each query execution results in multiple calls to
> {{AbstractRoot.getRootState}}. This might lead to breaking an invariant of
> the query engine, which probably assumes that the returned node state is the
> same during the course of a query. To prevent this I suggest to introduce an
> execution context, which provides a stable state for a query execution.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
