THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| No Format |
|---|
CONFIGS FOR TOPIC topicA
Name Value Sensitive Read-only Default Source
compression.type = producer false false Default trueuser
message.format.version = 1.0-IV0 false false Default trueuser
file.delete.delay.ms = 600006000 false false trueClient of user
leader.replication.throttled.replicas = false false Default trueuser
max.message.bytes = 1000012 false false Default trueuser
min.compaction.lag.ms = 0 false false true Default user
message.timestamp.type = CreateTime false false true Default user
min.insync.replicas = 1 false false true Default user
segment.jitter.ms = 0 false false Default trueuser
preallocate = false false false true Default user
index.interval.bytes = 4096 false false Default trueuser
min.cleanable.dirty.ratio = 0.5 false false true Default user
unclean.leader.election.enable = false false false true Default user
retention.bytes = 10 false false falseUser
delete.retention.ms = 86400000 false false trueDefault user
cleanup.policy = delete false false true Default user
flush.ms = 9223372036854775807 false false Default trueuser
follower.replication.throttled.replicas = false false true Default user
segment.bytes = 1073741824 false false true Default user
retention.ms = 604800000 false false true Default user
segment.ms = 604800000 false false true Default user
message.timestamp.difference.max.ms = 9223372036854775807 false false Default trueuser
flush.messages = 9223372036854775807 false false Default trueuser
segment.index.bytes = 10485760 false false trueDefault user
|
As seen above, the describe format becomes more organized and it will also return default properties (as the protocol currently supports that). In case of alter we will also do an extra describe after executing the alter and print the most fresh state.
...