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

Marius Petria reopened SLING-7360:
----------------------------------

I am reopening this issue in order to find a solution that does not introduce 
major backwards incompatibility issues.

[1] 
https://github.com/apache/sling-org-apache-sling-distribution-core/commit/3b959a72a555af2da29363a1e3cde2ae3b157fae

> Support creation of DistributionPackages for delete by 
> DistributionContentSerializer
> ------------------------------------------------------------------------------------
>
>                 Key: SLING-7360
>                 URL: https://issues.apache.org/jira/browse/SLING-7360
>             Project: Sling
>          Issue Type: Improvement
>          Components: Content Distribution
>            Reporter: Dirk Rudolph
>            Assignee: Dirk Rudolph
>            Priority: Minor
>             Fix For: Content Distribution Core 0.3.0
>
>
> For the integration into systems or then sling, that support 
> creation/deletion as part of their API [1], we can implement a 
> {{DistributionContentSerializer}} writing the format the API expects. That 
> currently works well for creation but not for deletion because both 
> {{FileDistributionPackageBuilder}} and {{ResourceDistributionPackageBuilder}} 
> inherit from {{AbstractDistributionPackageBuilder}} which [returns a 
> SimpleDistributionPackage|https://github.com/apache/sling-org-apache-sling-distribution-core/blob/master/src/main/java/org/apache/sling/distribution/packaging/impl/AbstractDistributionPackageBuilder.java#L72]
>  for {{DistributionRequestType.DELETE}}. 
> The other system's API might expect a different format then the one written 
> by {{SimpleDistributionPackage}} so it would be create if it would be 
> possible to delegate the creation of a deletion package to the serializer as 
> well, in case the serializer supports that.
> [1] 
> https://lucene.apache.org/solr/guide/7_2/uploading-data-with-index-handlers.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to