You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Timothee Maret (Jira)" <ji...@apache.org> on 2021/07/09 20:24:00 UTC

[jira] [Commented] (SLING-9051) Package handling should not auto save the session

    [ https://issues.apache.org/jira/browse/SLING-9051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17378275#comment-17378275 ] 

Timothee Maret commented on SLING-9051:
---------------------------------------

[~dsuess] The repository can't save arbitrarily large commit, therefore a transactional handling is possible only for packages of limited size.

Enforcing a limit in the content package extractor does not seem like a sensible option. Unlike today, end users would be required to split large package which is extra work and complexity. Moreover, importing those content packages won't be transactional.

> Package handling should not auto save the session
> -------------------------------------------------
>
>                 Key: SLING-9051
>                 URL: https://issues.apache.org/jira/browse/SLING-9051
>             Project: Sling
>          Issue Type: Bug
>          Components: Content Distribution
>            Reporter: Dominik Süß
>            Priority: Major
>             Fix For: Content Distribution Journal Core 0.2.2
>
>
> For clean transactional behavior of replication the session should not be autoSaved - the ootb behavior of filevault is to autoSave the nodes all 1024 nodes. This behavior should be changed somehow to keep transactional integrity
> https://github.com/apache/sling-org-apache-sling-distribution-journal/blob/0b977dbd4782291c14f4173e76ef1451568100a2/src/main/java/org/apache/sling/distribution/journal/impl/subscriber/ContentPackageExtractor.java#L95-L97



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