[jira] [Updated] (KAFKA-1775) Re-factor TopicCommand into thew handerAdminMessage call
[ https://issues.apache.org/jira/browse/KAFKA-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-1775: --- Issue Type: Improvement (was: Sub-task) Parent: (was: KAFKA-1694) > Re-factor TopicCommand into thew handerAdminMessage call > - > > Key: KAFKA-1775 > URL: https://issues.apache.org/jira/browse/KAFKA-1775 > Project: Kafka > Issue Type: Improvement >Reporter: Joe Stein >Assignee: Andrii Biletskyi > > kafka-topic.sh should become > kafka --topic --everything else the same from the CLI perspective so we need > to have the calls from the byte lalery get fed into that same code (few > changes as possible called from the handleAdmin call after deducing what > "Utility"[1] it is operating for > I think we should not remove the existing kafka-topic.sh and preserve the > existing functionality (with as little code duplication as possible) until > 0.9 (and there we can remove it after folks have used it for a release or two > and feedback and the rest)[2] > [1] https://issues.apache.org/jira/browse/KAFKA-1772 > [2] https://issues.apache.org/jira/browse/KAFKA-1776 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-1775) Re-factor TopicCommand into thew handerAdminMessage call
[ https://issues.apache.org/jira/browse/KAFKA-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-1775: Fix Version/s: (was: 0.8.3) > Re-factor TopicCommand into thew handerAdminMessage call > - > > Key: KAFKA-1775 > URL: https://issues.apache.org/jira/browse/KAFKA-1775 > Project: Kafka > Issue Type: Sub-task >Reporter: Joe Stein >Assignee: Andrii Biletskyi > > kafka-topic.sh should become > kafka --topic --everything else the same from the CLI perspective so we need > to have the calls from the byte lalery get fed into that same code (few > changes as possible called from the handleAdmin call after deducing what > "Utility"[1] it is operating for > I think we should not remove the existing kafka-topic.sh and preserve the > existing functionality (with as little code duplication as possible) until > 0.9 (and there we can remove it after folks have used it for a release or two > and feedback and the rest)[2] > [1] https://issues.apache.org/jira/browse/KAFKA-1772 > [2] https://issues.apache.org/jira/browse/KAFKA-1776 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-1775) Re-factor TopicCommand into thew handerAdminMessage call
[ https://issues.apache.org/jira/browse/KAFKA-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1775: --- Status: In Progress (was: Patch Available) > Re-factor TopicCommand into thew handerAdminMessage call > - > > Key: KAFKA-1775 > URL: https://issues.apache.org/jira/browse/KAFKA-1775 > Project: Kafka > Issue Type: Sub-task >Reporter: Joe Stein >Assignee: Andrii Biletskyi > Fix For: 0.8.3 > > > kafka-topic.sh should become > kafka --topic --everything else the same from the CLI perspective so we need > to have the calls from the byte lalery get fed into that same code (few > changes as possible called from the handleAdmin call after deducing what > "Utility"[1] it is operating for > I think we should not remove the existing kafka-topic.sh and preserve the > existing functionality (with as little code duplication as possible) until > 0.9 (and there we can remove it after folks have used it for a release or two > and feedback and the rest)[2] > [1] https://issues.apache.org/jira/browse/KAFKA-1772 > [2] https://issues.apache.org/jira/browse/KAFKA-1776 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-1775) Re-factor TopicCommand into thew handerAdminMessage call
[ https://issues.apache.org/jira/browse/KAFKA-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Stein updated KAFKA-1775: - Status: Patch Available (was: Reopened) > Re-factor TopicCommand into thew handerAdminMessage call > - > > Key: KAFKA-1775 > URL: https://issues.apache.org/jira/browse/KAFKA-1775 > Project: Kafka > Issue Type: Sub-task >Reporter: Joe Stein >Assignee: Andrii Biletskyi > Fix For: 0.8.3 > > > kafka-topic.sh should become > kafka --topic --everything else the same from the CLI perspective so we need > to have the calls from the byte lalery get fed into that same code (few > changes as possible called from the handleAdmin call after deducing what > "Utility"[1] it is operating for > I think we should not remove the existing kafka-topic.sh and preserve the > existing functionality (with as little code duplication as possible) until > 0.9 (and there we can remove it after folks have used it for a release or two > and feedback and the rest)[2] > [1] https://issues.apache.org/jira/browse/KAFKA-1772 > [2] https://issues.apache.org/jira/browse/KAFKA-1776 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-1775) Re-factor TopicCommand into thew handerAdminMessage call
[ https://issues.apache.org/jira/browse/KAFKA-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Stein updated KAFKA-1775: - Description: kafka-topic.sh should become kafka --topic --everything else the same from the CLI perspective so we need to have the calls from the byte lalery get fed into that same code (few changes as possible called from the handleAdmin call after deducing what "Utility"[1] it is operating for I think we should not remove the existing kafka-topic.sh and preserve the existing functionality (with as little code duplication as possible) until 0.9 (and there we can remove it after folks have used it for a release or two and feedback and the rest)[2] [1] https://issues.apache.org/jira/browse/KAFKA-1772 [2] https://issues.apache.org/jira/browse/KAFKA-1772 was: kafka-topic.sh should become kafka --topic --everything else the same from the CLI perspective so we need to have the calls from the byte lalery get fed into that same code (few changes as possible called from the handleAdmin call after deducing what "Utility"[1] it is operating for [1] https://issues.apache.org/jira/browse/KAFKA-1772 > Re-factor TopicCommand into thew handerAdminMessage call > - > > Key: KAFKA-1775 > URL: https://issues.apache.org/jira/browse/KAFKA-1775 > Project: Kafka > Issue Type: Sub-task >Reporter: Joe Stein > Fix For: 0.8.3 > > > kafka-topic.sh should become > kafka --topic --everything else the same from the CLI perspective so we need > to have the calls from the byte lalery get fed into that same code (few > changes as possible called from the handleAdmin call after deducing what > "Utility"[1] it is operating for > I think we should not remove the existing kafka-topic.sh and preserve the > existing functionality (with as little code duplication as possible) until > 0.9 (and there we can remove it after folks have used it for a release or two > and feedback and the rest)[2] > [1] https://issues.apache.org/jira/browse/KAFKA-1772 > [2] https://issues.apache.org/jira/browse/KAFKA-1772 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-1775) Re-factor TopicCommand into thew handerAdminMessage call
[ https://issues.apache.org/jira/browse/KAFKA-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Stein updated KAFKA-1775: - Description: kafka-topic.sh should become kafka --topic --everything else the same from the CLI perspective so we need to have the calls from the byte lalery get fed into that same code (few changes as possible called from the handleAdmin call after deducing what "Utility"[1] it is operating for I think we should not remove the existing kafka-topic.sh and preserve the existing functionality (with as little code duplication as possible) until 0.9 (and there we can remove it after folks have used it for a release or two and feedback and the rest)[2] [1] https://issues.apache.org/jira/browse/KAFKA-1772 [2] https://issues.apache.org/jira/browse/KAFKA-1776 was: kafka-topic.sh should become kafka --topic --everything else the same from the CLI perspective so we need to have the calls from the byte lalery get fed into that same code (few changes as possible called from the handleAdmin call after deducing what "Utility"[1] it is operating for I think we should not remove the existing kafka-topic.sh and preserve the existing functionality (with as little code duplication as possible) until 0.9 (and there we can remove it after folks have used it for a release or two and feedback and the rest)[2] [1] https://issues.apache.org/jira/browse/KAFKA-1772 [2] https://issues.apache.org/jira/browse/KAFKA-1772 > Re-factor TopicCommand into thew handerAdminMessage call > - > > Key: KAFKA-1775 > URL: https://issues.apache.org/jira/browse/KAFKA-1775 > Project: Kafka > Issue Type: Sub-task >Reporter: Joe Stein > Fix For: 0.8.3 > > > kafka-topic.sh should become > kafka --topic --everything else the same from the CLI perspective so we need > to have the calls from the byte lalery get fed into that same code (few > changes as possible called from the handleAdmin call after deducing what > "Utility"[1] it is operating for > I think we should not remove the existing kafka-topic.sh and preserve the > existing functionality (with as little code duplication as possible) until > 0.9 (and there we can remove it after folks have used it for a release or two > and feedback and the rest)[2] > [1] https://issues.apache.org/jira/browse/KAFKA-1772 > [2] https://issues.apache.org/jira/browse/KAFKA-1776 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-1775) Re-factor TopicCommand into thew handerAdminMessage call
[ https://issues.apache.org/jira/browse/KAFKA-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Stein updated KAFKA-1775: - Description: kafka-topic.sh should become kafka --topic --everything else the same from the CLI perspective so we need to have the calls from the byte lalery get fed into that same code (few changes as possible called from the handleAdmin call after deducing what "Utility"[1] it is operating for [1] https://issues.apache.org/jira/browse/KAFKA-1772 was: kafka-topic.sh should become kafka --topic --verything else the same from the CLI perspective so we need to have the calls from the byte lalery get fed into that same code (few changes as possible called from the handleAdmin call after deducing what "Utility"[1] it is operating for [1] https://issues.apache.org/jira/browse/KAFKA-1772 > Re-factor TopicCommand into thew handerAdminMessage call > - > > Key: KAFKA-1775 > URL: https://issues.apache.org/jira/browse/KAFKA-1775 > Project: Kafka > Issue Type: Sub-task >Reporter: Joe Stein > Fix For: 0.8.3 > > > kafka-topic.sh should become > kafka --topic --everything else the same from the CLI perspective so we need > to have the calls from the byte lalery get fed into that same code (few > changes as possible called from the handleAdmin call after deducing what > "Utility"[1] it is operating for > [1] https://issues.apache.org/jira/browse/KAFKA-1772 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
