[
https://issues.apache.org/jira/browse/KAFKA-14470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17650947#comment-17650947
]
Ismael Juma commented on KAFKA-14470:
-------------------------------------
[~mimaison] Dependencies of the log layer classes would have to be moved too,
yes. In some cases, it may warrant a separate ticket while in others it can be
bundled with one of the tickets that already exists (left to the discretion of
the contributor).
Regarding kraft, yes there are some opportunities once the log layer has been
completed moved to the storage layer. I was having a discussion with Jose
yesterday about this and will file a ticket to capture it.
> Move log layer to storage module
> --------------------------------
>
> Key: KAFKA-14470
> URL: https://issues.apache.org/jira/browse/KAFKA-14470
> Project: Kafka
> Issue Type: Improvement
> Reporter: Ismael Juma
> Assignee: Ismael Juma
> Priority: Major
>
> We introduced the `storage` module as part of KIP-405, but the existing log
> layer remains in the `core` module. Moving the log layer to the `storage`
> module would be another step towards improved modularity and build times
> (similar to `metadata`, `raft` and `group-coordinator`).
> We should do this in an incremental manner to make the code review process
> easier. I will create separate tasks, each one mapping to one pull request.
> In order to understand the feasibility, I tackled a few of the tasks myself.
> Help from the community is appreciated for the unassigned tasks, but it
> probably makes sense to do that after the initial PRs have been submitted.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
