You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ryan P (JIRA)" <ji...@apache.org> on 2016/03/22 11:56:25 UTC

[jira] [Created] (KAFKA-3445) ConnectorConfig should validate TASKS_MAX_CONFIG's lower bound limit

Ryan P created KAFKA-3445:
-----------------------------

             Summary: ConnectorConfig should validate TASKS_MAX_CONFIG's lower bound limit 
                 Key: KAFKA-3445
                 URL: https://issues.apache.org/jira/browse/KAFKA-3445
             Project: Kafka
          Issue Type: Improvement
          Components: config
            Reporter: Ryan P
            Priority: Trivial


I'll be the first to admit this is a bit nit picky any property marked with Importance.HIGH should be guarded against non-sensical values. 

With that said I would like to suggest that TASKS_MAX_CONFIG be validating against a lower bound limit of 1. 

I do understand this is unlikely to happen and the configuration is nonsensical but there is no penalty for stopping someone from trying it out. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)