You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (JIRA)" <ji...@apache.org> on 2015/07/14 17:36:04 UTC
[jira] [Resolved] (SLING-4881) NoSQL Generic Resource Provider:
Preserve order of changed resources
[ https://issues.apache.org/jira/browse/SLING-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Seifert resolved SLING-4881.
-----------------------------------
Resolution: Fixed
Completed: At revision: 1690990
patch applied, thanks
> NoSQL Generic Resource Provider: Preserve order of changed resources
> ---------------------------------------------------------------------
>
> Key: SLING-4881
> URL: https://issues.apache.org/jira/browse/SLING-4881
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: NoSQL Generic Resource Provider 0.5.0
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Fix For: NoSQL Generic Resource Provider 0.5.0
>
>
> comment from Levente Santha in SLING-4381:
> {quote}
> I've made some experiments recently with NoSQL Generic Resource Provider and it was very useful.
> I've noticed an issue where the order of changed resources is not preserved in NoSqlResourceProvider and it can happen that for the create() method a path gets passed which has no parent in the backing NoSQL storage yet. I've also attached the patch SLING-4381_Preserve_order_of_changed_resources_.patch for this.
> {quote}
> this includes a patch:
> https://issues.apache.org/jira/secure/attachment/12743313/SLING-4381_Preserve_order_of_changed_resources_.patch
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)