THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
MetadataRequest => [topics] |
Stays the same as version 0 however behavior changes.
In version 0 there was no way to request no topics, and and empty list signified all topics.
In version 1 a A null topics list (size -1 on the wire) will indicate that a user wants no ALL topic metadata. Compared to an empty list (size 0) which indicates metadata for all NO topics should be returned.
Metadata Response (version 1)
MetadataResponse => [brokers] controller_id [internal_topics] [topics_marked_for_deletion] [topic_metadata] brokers => node_id host port rack is_controller node_id => INT32 host => STRING port => INT32 rack => NULLABLE_STRING controller_idis_controller => INT32BOOLEAN STRING topic_metadata => topic_error_code topicis_internal marked_for_deletion [partition_metadata]
topic_error_code => INT16
topic => STRING
is_internal => BOOLEAN
marked_for_deletion => BOOLEAN
partition_metadata => partition_error_code partition_id leader [replicas] [isr]
partition_error_code => INT16
partition_id => INT32
leader => INT32 |
Adds rack, iscontroler_controllerid, isinternal_internal topics and topics_marked_for_deletion to the version 0 response.
...