[
https://issues.apache.org/jira/browse/OAK-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795036#comment-13795036
]
Michael Dürig commented on OAK-1052:
------------------------------------
Thanks for reviewing. I applied the patch at revision 1532263.
On a related note, could we get rid off {{ExecutionContext.getRootTree()}} and
replace the client code with something along the lines of
{code}
Tree rootTree = new ImmutableRoot(executionContext.getRootState()))
{code}
This would reduce redundancies and simplify the code in other places.
> 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)