[
https://issues.apache.org/jira/browse/OAK-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Parvulescu updated OAK-1096:
---------------------------------
Attachment: OAK-1096.patch
attaching proposed patch (fix+test)
the idea is to turn the QueryResult creation into a session operation which
would trigger the refresh behavior.
> QueryManager does not have autorefresh
> --------------------------------------
>
> Key: OAK-1096
> URL: https://issues.apache.org/jira/browse/OAK-1096
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr, query
> Affects Versions: 0.10
> Reporter: Christan Keller
> Assignee: Alex Parvulescu
> Attachments: Issue.java, OAK-1096.patch
>
>
> Having two sessions A and B.
> A writes something for example /content/page/text = "text"
> Accessing B's QueryManager and exexcute a query for "text" nothing will be
> found.
> Triggering an explicit refresh on B before the query and the hit is found.
> I assume that the autorefresh is missed for that case
--
This message was sent by Atlassian JIRA
(v6.1#6144)
