[
https://issues.apache.org/jira/browse/SLING-5406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-5406.
-------------------------------------
Resolution: Fixed
I've refactored the change handling in rev 1722178.
Queue configuration changes have no influence anymore as no jobs are reassigned
etc. therefore I could remove the whole logic for that part.
Property changes are now more lightweight than before as they don't cause the
job processing to restart.
> Optimize configuration change handling
> --------------------------------------
>
> Key: SLING-5406
> URL: https://issues.apache.org/jira/browse/SLING-5406
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Event 4.1.0
>
>
> There are different kinds of configuration changes:
> - changes in queue configuration
> - topology changes
> Currently these are handled slightly different and can occur concurrently.
> We should unify the code and run it through the same methods. The change
> detection can be further optimized to ignore irrelevant changes (e.g. new
> consumers)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
