[
https://issues.apache.org/jira/browse/JCR-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger resolved JCR-3699.
-----------------------------------
Resolution: Invalid
This is by design. The specification allows an implementation to run queries
only against the persisted state of the repository [0]. This is what Jackrabbit
does.
[0] http://www.day.com/specs/jcr/2.0/6_Query.html#6.5%20Search%20Scope
> 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
>
> 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
(v6.1#6144)
