Since you need to learn about the leader for a topic in order to do
anything, you kind of already have "auto-create" since getting metadata
for a topic will create it if it doesn't exist.
As for auto-delete, log files will be deleted over time (per the usual
policy). There will be residual stuff in ZooKeeper, but I don't think it
will be detrimental to performance (does the broker keep any active
state for a topic that's not being used? - not sure)
Not to say topic deletion isn't a useful feature, but I think punting
out of 0.8 is fine.
-David
On 4/4/13 3:01 PM, Jason Rosenberg wrote:
Ok,
This is a feature I've been hoping for, so I added an upvote to Kafka-330.
But I will defer to you in terms of not wanting to delay 0.8 unnecessarily.
Will we still have a backhanded way to remove a topic if need be?
Ultimately, I'd like to see the feature where a topic automatically is
created on receipt of a new message, and that topic will then automatically
become deleted after a configurable period of inactivity. In otherwords,
auto-creation and auto-deletion.
Jason
On Thu, Apr 4, 2013 at 11:35 AM, Jun Rao <jun...@gmail.com> wrote:
Hi,
We started the work on deleting topics in 0.8 (kafka-330). We realized that
it touches quite a few critical components such as controller, replica
manager, and log, and it will take some time to stabilize this. In order
not to delay the 0.8 release too much, I propose that we push this feature
out of 0.8. Since we don't really support deleting topics in 0.7, this
doesn't reduce the existing features.
Any concerns from people?
Thanks,
Jun
