[
https://issues.apache.org/jira/browse/KAFKA-18229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17909771#comment-17909771
]
Chia-Ping Tsai commented on KAFKA-18229:
----------------------------------------
{quote}
If we totally remove the directory from the packaging, then users who upgrade
via the tar.gz will still see the "kraft" directory in their local install
directory. Maybe we can move the configs and leave a DEPRECATED text file under
"kraft"?
{quote}
not sure whether we have to handle the orphan files/folders caused by tar.gz
upgrade. Also, how to ensure users will read those DEPRECATED text file after
upgrading?
{quote}
Another thing we could consider is printing a warning in the start script if
the config path includes "kraft" in the last directory segment.
{quote}
I'm ok with this approach if we must give some warnings to users.
{quote}
We will also need to update our docs for references of "config/kraft"
{quote}
+1
> Move configs out of "kraft" directory
> -------------------------------------
>
> Key: KAFKA-18229
> URL: https://issues.apache.org/jira/browse/KAFKA-18229
> Project: Kafka
> Issue Type: Sub-task
> Reporter: David Arthur
> Assignee: TengYao Chi
> Priority: Blocker
> Fix For: 4.0.0
>
>
> We should consider moving the broker/controller configs out of the "kraft"
> sub-directory and removing that directory. For a new 4.0 user, it could be a
> bit confusing that some configs are in "configs" and some are in
> "configs/kraft".
> I know it will probably break a bunch of example code out there, but I don't
> think we should keep this directory around forever.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
