[
https://issues.apache.org/jira/browse/KAFKA-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294046#comment-13294046
]
Prashanth Menon edited comment on KAFKA-329 at 6/13/12 1:21 AM:
----------------------------------------------------------------
Hi Jun,
New patch with your changes incorporated. I think it's functionally complete,
but I may have missed some things.
As for a json library, I'm not sure what plays well specifically with Scala,
though I suspect most basic Java json libs should be fine. I personally have
experience with Jackson which has a nice Scala wrapper lib called Jerkson
(https://github.com/codahale/jerkson). There is also Lift-JSON, but I'm not
familiar with though I've heard good things from people. Perhaps integrating a
JSON lib can be part of a separate JIRA?
was (Author: prashanth.menon):
Hi Jun,
New patch with your changes incorporated. I think it's functionally complete,
but I may have missed some things.
As for a JSON library, I'm not sure what plays well specifically with Scala,
though I suspect basic Java libs should suffice. I personally have experience
with Jackson which has a nice Scala wrapper lib called Jerkson
(https://github.com/codahale/jerkson). There is also Lift-JSON, but I'm not
familiar with though I've heard good things from people. Perhaps integrating a
JSON lib can be part of a separate JIRA?
> Remove the watches/broker for new topics and partitions and change create
> topic admin API to send start replica state change to all brokers
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-329
> URL: https://issues.apache.org/jira/browse/KAFKA-329
> Project: Kafka
> Issue Type: Sub-task
> Affects Versions: 0.8
> Reporter: Neha Narkhede
> Assignee: Prashanth Menon
> Labels: replication
> Attachments: KAFKA-329-DRAFT-v2.patch, KAFKA-329-DRAFT.patch,
> KAFKA-329-v1.patch
>
>
> Currently in 0.8, all brokers register a watch on /brokers/topics and
> /brokers/topics/[topic] for all topics in a Kafka cluster. The watches are
> required to discover new topics.
> There is another way this can be achieved, as proposed here -
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+replication+detailed+design+V2#KafkareplicationdetaileddesignV2-Createtopic
> Basically, the create-topic admin command sends start-replica state change
> request to all brokers in the assigned replicas list.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
