Hi, (Probably a question for Carsten). Is the right way to implement topology based queue exclusion by implementing a topology discovery PropertyProvider that provides the property:
org.apache.sling.event.jobs.consumer.topics containing a , separated list of topics the instance can handle. If so I have 2 questions: Since this list is topology dependent (depends on which is master) and will itself have to be generated after a topology change which may take some time to filter through the discovery hub spoke implementation, will it cause the Job Queue to restart multiple times on a relevant property change. ? Also, how are Topics excluded from a list of capabilities for each instance. I have read through the code in the constructor of TopologyCapabilities and the getPotentialTargets, detectTartgets and I cant see how to exclude a topic from an instance, only how to include. What is the best way of excluding a topic from a instance without having to whitelist all known topics. ? Best Regards Ian
