Elek, Marton commented on HDFS-13415:

Thank you [~msingh] to check the patch.

It's hard to grep for cblock as this expression is used at many places in the 
existing hdfs code (...cBlock).

I addressed all the issues in the latest patch (you can see the diff between 
the two patches here: 

The only exception is the TestConfiguration.java (item 3). Here the cblock is 
just a custom example string to test the configuration. The code itself isn't 
related to the cblock. I would keep it as is, because it would introduce 
additional differences betweeen trunk and HDFS-7240 which could make the merge 
review harder.

> Ozone: Remove cblock code from HDFS-7240 (move to a different branch)
> ---------------------------------------------------------------------
>                 Key: HDFS-13415
>                 URL: https://issues.apache.org/jira/browse/HDFS-13415
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ozone
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
>            Priority: Minor
>         Attachments: HDFS-13415-HDFS-7240.001.patch, 
> HDFS-13415-HDFS-7240.002.patch
> The Ozone components (hdds/ozone) and cblock components (cblock) has 
> different stability. We suggest to separated the development: Ozone could 
> remain on HDFS-7240 and could be merged to the trunk as voted by the 
> community.
> The cblock development could be kept on a separated feature branch 
> (HDFS-11118) and could be developed and merged independently.
> To achieve this we 
>  1. need to remove the cblock code from HDFS-7240 branch (this is what this 
> jira about)
>  2. Create a new branch from the latest HDFS-7240 which contains the cblock 
> server (not in this jira)

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to