You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "Julian Reschke (Jira)" <ji...@apache.org> on 2019/12/18 12:45:00 UTC

[jira] [Closed] (JCR-3699) JCR_SQL2 queries don't see modifications inside a transaction the changes were made in

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

Julian Reschke closed JCR-3699.
-------------------------------

> JCR_SQL2 queries don't see modifications inside a transaction the changes were made in
> --------------------------------------------------------------------------------------
>
>                 Key: JCR-3699
>                 URL: https://issues.apache.org/jira/browse/JCR-3699
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core, query
>    Affects Versions: 2.6.3
>            Reporter: Radoslaw Stachowiak
>            Priority: Major
>
> When Jackrabbit is used with JTA, Lucene index is updated on transaction commit. Due to this, changes made inside a transaction are not visible to queries run from inside the same transaction.
> Steps to reproduce:
> 1. Begin JTA transaction.
> 2. Add a node.
> 3. Use a JCR_SQL2 query to find the node.
> Expected: node is found.
> Actual: node is not found.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)