GitHub user vahidhashemian opened a pull request:

    https://github.com/apache/kafka/pull/2673

    KAFKA-4858: Broker should ignore long topic names

    Starting from the 0.10.0.0 release topics names of over 249 characters are 
not allowed (`kafka-topics.sh` would disallow the creation). However, it is 
possible to use an older client version against the more recent brokers and 
attempt to create topics with longer names.
    This causes problems with the broker when trying to bring the corresponding 
partitions online (as described in the 
[JIRA](https://issues.apache.org/jira/browse/KAFKA-4858)).
    This PR makes the broker ignore those topics to avoid the reported failures.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/vahidhashemian/kafka KAFKA-4858

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/2673.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2673
    
----
commit 0614c9d0e59fc0b6f63b42b1358e8f0ed4f450dc
Author: Vahid Hashemian <vahidhashem...@us.ibm.com>
Date:   2017-03-10T22:44:47Z

    KAFKA-4858: Broker should ignore long topic names
    
    Starting from the 0.10.0.0 release topics names of over 249 characters are 
not allowed (`kafka-topics.sh` would disallow the creation). However, it is 
possible to use an older client version against the more recent brokers and 
attempt to create topics with longer names.
    This causes problems with the broker when trying to bring the corresponding 
partitions online (as described in the 
[JIRA](https://issues.apache.org/jira/browse/KAFKA-4858)).
    This PR makes the broker ignore those topics to avoid the reported failures.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to