Chronicle Computations aren't aware of incorrect configuration

Steps to reproduce:

• Create a nuxeo-stream by calling manager.getAppender(logName)
• The stream is automatically created with 4 partitions
• Configure a StreamProcessor with defaultConcurrency="1" defaultPartitions="1"
• The stream processor will be created with a Computation that only processes the first partition.
• 3 partitions are ignored and will not be processed.

This only applies to Chronicle and not Kafka. Is there something we can do to warn about this situation?