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

Timothee Maret commented on SLING-7754:
---------------------------------------

[~bdelacretaz] good point, indeed 
[DistributionQueue|https://github.com/apache/sling-org-apache-sling-distribution-core/blob/master/src/main/java/org/apache/sling/distribution/queue/spi/DistributionQueue.java]
 does not depend on JCR entities.

AFAIU, the goal of this issue, is to provide an alternative implementation of 
"passive queues" for SCD agents, which would back queue items in the repository 
directly (without leveraging the Sling Jobs API). The alternative 
implementation could likely access the repository using Sling APIs. 

IIUC  the title of the issue puts the emphasis on JCR where it should put the 
emphasis on the repository.

> Implement passive DistributionQueue in JCR
> ------------------------------------------
>
>                 Key: SLING-7754
>                 URL: https://issues.apache.org/jira/browse/SLING-7754
>             Project: Sling
>          Issue Type: Improvement
>          Components: Content Distribution
>            Reporter: Marius Petria
>            Assignee: Marius Petria
>            Priority: Major
>
> In order to minimize dependency on Sling Jobs and improve performance we 
> should offer an implementation passive queues in JCR.
> Passive queues are distribution queues [1] for which no queue processor is 
> defined. They are only used to store items and do not need rebalancing 
> between instances. They just need to be stored and fetched (FIFO semantics) 
> and this can easily be implemented in JCR with a simpler implementation that 
> does not use querying (querying for jobs is problematic like OAK-7495 shows).
> [1] 
> https://github.com/apache/sling-org-apache-sling-distribution-core/blob/master/src/main/java/org/apache/sling/distribution/queue/spi/DistributionQueue.java



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

Reply via email to