[jira] Commented: (SLING-1823) Use ConfigAdmin configurations for queues

["Carsten Ziegeler (JIRA)" <ji...@apache.org>]

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

Carsten Ziegeler commented on SLING-1823:
-----------------------------------------

A queue configuration gets a list of topics (kind of regexps) which match the job topic. Through this matching algorithm a queue can process a set of topics. It should also be possible to have a single configuration which creates various topics, like

topic matcher: org.apache.x.y.*
queue name: {0}

This queue processes all topics starting with org.apache.x.y. and a new queue is used for every sub topic, so if jobs org.apache.x.y.A and org.apache.x.y.B are processed, two queues A and B are created

> Use ConfigAdmin configurations for queues
> -----------------------------------------
>
>                 Key: SLING-1823
>                 URL: https://issues.apache.org/jira/browse/SLING-1823
>             Project: Sling
>          Issue Type: New Feature
>          Components: Extensions
>    Affects Versions: Extensions Event 2.4.0
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Extensions Event 3.0.0
>
>
> Currently the jobs send to the job handler might contain queue configuration information, like a queue name, parallel settings etc. These props are used to create queues. This approach has a least two potential problems:
> - What happens if two jobs specify the same queue name with different settings?
> - The developer creating the code to send the job might not be the person deciding what is processed in which queue and how
> Therefore it would make more sense to have a queue as a configuration in the ConfigAdmin . this would make maintenance easier and allows to have a single place for queue configurations. Of course the old props should still be supported for compatibility.
> The configurations can then be easily added, viewed and monitored through the web console.
> The main queue is a configuration which is always available

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.