[
https://issues.apache.org/jira/browse/HDFS-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240849#comment-13240849
]
Aaron T. Myers commented on HDFS-3000:
--------------------------------------
bq. The namespace quota is quite specific to HDFS.
Is it? I don't have any specific counterexamples, but I'd be surprised if other
file systems didn't have a similar concept, given that INodes are usually a
finite resource.
bq. Setting quota is pure admin method but users could use chown for changing
groups although they cannot change owner.
I suppose that distinction is reasonable. The distinction, then, is "a
requirement of superuser privileges in all cases."
But, that still leaves open the issue of the asymmetry between getting/setting
quotas. Does that not concern you at all, Nicholas?
> 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
