You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Mike Percy (JIRA)" <ji...@apache.org> on 2016/02/26 12:41:18 UTC

[jira] [Updated] (KUDU-474) Reimplement current Kudu on-disk storage approach as allocation strategy

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

Mike Percy updated KUDU-474:
----------------------------
    Parent: KUDU-423

> Reimplement current Kudu on-disk storage approach as allocation strategy
> ------------------------------------------------------------------------
>
>                 Key: KUDU-474
>                 URL: https://issues.apache.org/jira/browse/KUDU-474
>             Project: Kudu
>          Issue Type: Sub-task
>          Components: fs
>    Affects Versions: M4.5
>            Reporter: Adar Dembo
>            Assignee: Adar Dembo
>
> To make it easier to compare the existing Kudu approach to on-disk storage with the new ones envisioned in Todd's design document, we should reimplement it as a "plugin" to the new block storage API.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)