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/10/15 16:58:42 UTC

[jira] [Resolved] (OAK-1096) QueryManager does not have autorefresh

     [ https://issues.apache.org/jira/browse/OAK-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Parvulescu resolved OAK-1096.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 0.11

fixed with http://svn.apache.org/r1532371

Thanks Chris for spotting this!

> 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
>             Fix For: 0.11
>
>         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)