sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SLING-7382) Send Content-Type header along with the DistributionPackage's content in forward and reverse distribution
Date Mon, 15 Jan 2018 18:35:03 GMT

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

ASF GitHub Bot commented on SLING-7382:
---------------------------------------

Buuhuu opened a new pull request #5: SLING-7382: move content-type logic to DistributionPackage
and DistributionPackageInfo
URL: https://github.com/apache/sling-org-apache-sling-distribution-core/pull/5
 
 
   Moving the logic for the content-type to DistributionPackage/DistributionPackageInfo ensures
that for both producer and consumer side the contentType is set and the implementation can
rely on it. On the other hand no further verification is implemented yet. 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Send Content-Type header along with the DistributionPackage's content in forward and
reverse distribution
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: SLING-7382
>                 URL: https://issues.apache.org/jira/browse/SLING-7382
>             Project: Sling
>          Issue Type: Improvement
>          Components: Content Distribution
>            Reporter: Dirk Rudolph
>            Priority: Minor
>
> Along with SLING-7357 the transmission of DistributionPackage's Content-Type has been
implemented for forward distribution to allow writing DistributionContentSerializers targeting
different kinds of sinks in forward distribution.
> An addition to that use case is the implementation of the same in the opposite direction.
For example sling not only being a source in a stream processing cluster but also being
a sink. 
> For example:
> 1. We have a authoring instance where editors create content
> 2. That content gets distributed to a publishing instance
> 3. From the publishing instance the content gets distributed to apache solr
> 4. Solr runs [ClassificationUpdateProcessorFactory|https://lucene.apache.org/solr/7_2_0/solr-core/org/apache/solr/update/processor/ClassificationUpdateProcessorFactory.html]
enriching the content
> 5. The authoring instance periodically pulls back the classified content
> A real world example would be smart tagging, where human judgment is applied on a subset
of content and classification with existing infrastructure is done to enrich the all of the
content. 



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

Mime
View raw message