THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
| Table of Contents |
|---|
Status
Current state: Under discussion Accepted
Discussion thread: TODO https://lists.apache.org/thread/scx75cjwm19jyt19wxky41q9smf5nx6d
Vote thread: https://lists.apache.org/thread/dgq332o5j25rwddbvfydf7ttrclldw17
JIRA: KAFKA-15575
Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).
...
A new connector property will be introduced as an emergency measure to disable this behavior:
| Name | Type | Default | Importance | Description (sample; subject to change during code review) |
|---|---|---|---|---|
| tasks.max.enforce | boolean | true | low | (Deprecated) Whether to enforce that the tasks.max property is respected by the connector. By default, connectors that generate too many tasks will fail, and existing sets of tasks that exceed the tasks.max property will also be failed. If this property is set to false, then connectors will be allowed to generate more than the maximum number of tasks, and existing sets of tasks that exceed the tasks.max property will be allowed to run. This property is deprecated and will be removed in an upcoming major release. |
A future major (x.0.0) release
In an upcoming major release, the tasks.max.enforce property will be removed and it will become impossible to disable enforcement of the tasks.max property.
IdeallyAssuming the KIP is implemented and released in 3.8.0, this will may take place with the in 4.0.0 release (assuming the KIP is completed in time), but we may delay the removal of this property depending on feedback from the communitymay also be delayed until 5.0.0 or a subsequent major version bump in order to allow users to more gracefully adapt to the change in runtime behavior by Kafka Connect.
All patch (x.y.z, z >= 1) releases on older versions
...