You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Ismael Juma (Jira)" <ji...@apache.org> on 2022/12/14 21:18:00 UTC
[jira] [Updated] (KAFKA-14470) Move log layer to storage module

     [ https://issues.apache.org/jira/browse/KAFKA-14470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ismael Juma updated KAFKA-14470:
--------------------------------
    Description: 
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.

  was:
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.


> 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)