An interactive CLI tool for managing Kafka topics
write!
's into single batched write!
's)PagedVec
)c
on the topics view. The -M
flag must be set when running Topiks to allow topic creation. The expected input is [topic name]:[partitions]:[replication factor]
. Topic config will be set to the default cluster settings, which can be changed via Topiks after successful creation. Topic names are limited to 249 alphanumeric characters, _
, or .
.Here it is, the alpha+001 version, which I hope to have you help test with me. This has been used on both local and real Kafka clusters, but more testing is always useful.
This version should be relatively safe to use on your Kafka cluster; this is especially true in read-only mode (i.e. not using -M
and -D
flags). It goes without saying, but, user beware when testing.
When modifying topic configs, I've discovered that some—but not all—of the configs are validated by the cluster when changes are applied. For example, message.format.version
allows for free, unvalidated text. In this case, when changed to an invalid value, the topic will become corrupted on the cluster.
And you can build it yourself using Cargo.