[
https://issues.apache.org/jira/browse/HDFS-10996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15614112#comment-15614112
]
SammiChen commented on HDFS-10996:
----------------------------------
Set EC policy to an existing none empty file or unset EC policy from an none
empty file will force the existing file content transform between EC stripping
and 3x continuous layout which may be time consuming. So I agree we done it
somewhere else, tools like Mover.
As for this JIRA, there are multiple {{create}} APIs. Instead of adding a
bunch of new create APIs with each has one new Erasure Code Policy parameter,
I'd like to improve current {{setErasureCodingPolicy}}, make it accept both
directory path and file path. If it's a file path, this file must have no data
content, otherwise the {{setErasureCodingPolicy}} will fail.
I'd like to hear your thoughts, [~drankye], [~andrew.wang], thanks!
> Ability to specify per-file EC policy at create time
> ----------------------------------------------------
>
> Key: HDFS-10996
> URL: https://issues.apache.org/jira/browse/HDFS-10996
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: erasure-coding
> Affects Versions: 3.0.0-alpha1
> Reporter: Andrew Wang
> Assignee: SammiChen
>
> Based on discussion in HDFS-10971, it would be useful to specify the EC
> policy when the file is created. This is useful for situations where app
> requirements do not map nicely to the current directory-level policies.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
