[
https://issues.apache.org/jira/browse/HDFS-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240853#comment-13240853
]
Eli Collins commented on HDFS-3000:
-----------------------------------
ATM has a point wrt the asymmetry, does it make sense to have setOwner and
setQuota live in separate classes? I thought FileSystem/FileContext we're
purely non-admin, but that's not the case.
Another idea, we have an interface for administrative methods (setOwner,
setQuota, etc) but have the implementation still live in FileSystem/Context.
> Add a public API for setting quotas
> -----------------------------------
>
> Key: HDFS-3000
> URL: https://issues.apache.org/jira/browse/HDFS-3000
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs client
> Affects Versions: 0.23.1
> Reporter: Aaron T. Myers
> Assignee: Aaron T. Myers
>
> Currently one can set the quota of a file or directory from the command line,
> but if a user wants to set it programmatically, they need to use
> DistributedFileSystem, which is annotated InterfaceAudience.Private.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
