[
https://issues.apache.org/jira/browse/SLING-9873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17226583#comment-17226583
]
Rahul Bhardwaj commented on SLING-9873:
---------------------------------------
[~marett] - Thanks for the feedback. Can you please help me understand the use
case that you are mentioning? Under what condition would new code process
package with old separator? AFAIU, the package is created by the code only and
then distributed to the other instance through content distribution process and
therefore, it can only happen if the author is running old code and the
distributed instance is running new code. I think we can be sufficiently
confident that it would not be so because similar argument can apply to all the
topologies, right? Do we support instances running different version of
different bundles.
If the usecase can be encountered in some other scenario, please share.
> A comma in node name causes Sling Content Distribution to fail
> --------------------------------------------------------------
>
> Key: SLING-9873
> URL: https://issues.apache.org/jira/browse/SLING-9873
> Project: Sling
> Issue Type: Bug
> Components: Content Distribution
> Affects Versions: Content Distribution Core 0.4.2
> Reporter: Rahul Bhardwaj
> Assignee: Timothee Maret
> Priority: Major
> Fix For: Content Distribution Core 0.4.4
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Sling content distribution uses comma as a path delimiter [0]but comma is a
> valid jcr character name and hence must not be used as a path delimiter.
> Usage of a comma in name breaks Delete operation of forward replication.
> [0] -
> https://github.com/apache/sling-org-apache-sling-distribution-core/blob/master/src/main/java/org/apache/sling/distribution/packaging/impl/SimpleDistributionPackage.java#L101
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
