...

Current State: Discussion
Discussion Thread: here
Jira: 

Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).

...

Proposed Change

All changes suggested in this KIP will only be applied when connectors are created, for connectors already deployed at the time this is implemented no changes are made, they can be updated and deleted like before.

For new connectors, Change the validation of connector names will be changed to trim leading and trailing whitespaces and reject zero length strings after trimming. This would allow for whitespaces in connector names but remove potential confusion caused by accidentally padding the name with whitespaces, which is easily possible due to the create request having the name as a json value, not in the url. This will only affect the creation of new connectors, 

Apart from that no characters will be rejected.

...

There is no new public interface, however the behavior of the create connector api will change a little bit. . Existing connectors are not affected by this change and can be updated and queried just like today.

Following implementation of this KIP, leading and trailing whitespaces in connector names will be trimmed before the connector is created. In the response to the create request the updated name will be reflected. See the following table for a few examples:

...

Migration plan and compatibility

Backward compatibility should be given, subject to testing.for existing connectors is given, as all changes suggested here only affect connectors when they are created. The possibility to update and delete existing connectors is not impacted.

For new connectors that are created after implementing this change limitations are restricted to a few scenarios described below. Apart from those, Since no characters are restricted nothing that previously worked should break based on this KIP. Connectors with an empty name were broken before and could not be deleted anyway, so there is no reason to half-support these any further. It is however a change in behavior to reject these. 

There As mentioned there are however two scenarios that are affected by this change:

...