[
https://issues.apache.org/jira/browse/HDFS-8090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14487253#comment-14487253
]
Rakesh R commented on HDFS-8090:
--------------------------------
Thanks [~vinayrpet] for the work. In the latest patch {{chunkSize}} attribute
is deleted from {{hdfs.proto}}, any specific reason for this. But I could see
{{if (this.options.containsKey(CHUNK_SIZE_KEY))}} logic is still used in
ESSchema and got confused, am I missing anything?
{code}
- required uint32 chunkSize = 5;
- repeated ECSchemaOptionEntryProto options = 6;
+ repeated ECSchemaOptionEntryProto options = 5;
{code}
bq. IMO audit log not required for this call as this is systemwide call. not
particular to any path.
Makes sense to me.
> Erasure Coding: Add RPC to client-namenode to list all ECSchemas loaded in
> Namenode.
> ------------------------------------------------------------------------------------
>
> Key: HDFS-8090
> URL: https://issues.apache.org/jira/browse/HDFS-8090
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Vinayakumar B
> Assignee: Vinayakumar B
> Attachments: HDFS-8090-01.patch, HDFS-8090-02.patch
>
>
> ECSchemas will be configured and loaded only at the Namenode to avoid
> conflicts.
> Client has to specify one of these schemas during creation of ecZones.
> So, add an RPC to ClientProtocol to get all ECSchemas loaded at namenode, so
> that client can choose only any one of these.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
