[
https://issues.apache.org/jira/browse/KAFKA-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16107997#comment-16107997
]
Jason Gustafson commented on KAFKA-1944:
----------------------------------------
I personally don't think it's worth introducing alternative configs just so we
can rename classes internally. The naming is unfortunate, but many users have
gotten used to it and having multiple config names seems rather annoying
(deprecation is a slow process). It sounds like we are in agreement on
deprecating {{log.cleaner.enable}}? Maybe we should do that in a separate
JIRA/KIP and consider closing this as "won't fix"?
> Rename LogCleaner and related classes to LogCompactor
> -----------------------------------------------------
>
> Key: KAFKA-1944
> URL: https://issues.apache.org/jira/browse/KAFKA-1944
> Project: Kafka
> Issue Type: Bug
> Reporter: Gwen Shapira
> Assignee: Pranav Maniar
> Labels: newbie
>
> Following a mailing list discussion:
> "the name LogCleaner is seriously misleading. Its more of a log compactor.
> Deleting old logs happens elsewhere from what I've seen."
> Note that this may require renaming related classes, objects, configs and
> metrics.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
