[
https://issues.apache.org/jira/browse/KAFKA-14470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17651098#comment-17651098
]
Satish Duggana edited comment on KAFKA-14470 at 12/22/22 6:54 AM:
------------------------------------------------------------------
[~ijuma] [~mimaison] `LogOffsetMetadata` refactoring to move to storage module
is being done as part of https://issues.apache.org/jira/browse/KAFKA-14480.
Glad to raise PR against https://issues.apache.org/jira/browse/KAFKA-14543 for
that specific change if you have not yet started working on that.
was (Author: satish.duggana):
[~ijuma] [~mimaison] `LogOffsetMetadata` refactoring to move to storage module
is being done as part of https://issues.apache.org/jira/browse/KAFKA-14480. Let
me know if I can raise PR against
https://issues.apache.org/jira/browse/KAFKA-14543 for that specific change.
> 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)
