[
https://issues.apache.org/jira/browse/HDFS-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13746763#comment-13746763
]
Colin Patrick McCabe commented on HDFS-5052:
--------------------------------------------
bq. I'd mildly prefer the same style as listStatus, since we can add 1 on the
server side.
OK. I will switch it to be the same as that, for consistency.
bq. Yep, my point was that we already require paths to be absolute (see the
DFSUtil#isValidName check in DFS#getPathName and FSNamesystem. Seems like the
normalization is unnecessary since nothing else server side does it, and maybe
you could just call DFSUtil#isValidName to do the absolute check (and more).
If we start allowing non-normalized paths, we could have people add both /a and
/a/, etc. I'd rather do this in the CacheManager than in FSNamesystem, since
the rationale for doing it is to preserve CacheManager invariants.
I will switch to using {{DFSUtil#isValidName}} to avoid duplicating this logic.
> Add cacheRequest/uncacheRequest support to NameNode
> ---------------------------------------------------
>
> Key: HDFS-5052
> URL: https://issues.apache.org/jira/browse/HDFS-5052
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: datanode, namenode
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Attachments: HDFS-5052.003.patch, HDFS-5052.004.patch,
> HDFS-5052-caching.002.patch, HDFS-5052-caching.004.patch
>
>
> Add cacheRequest/uncacheRequest/listCacheRequest support to DFSAdmin and
> NameNode. Maintain a list of active CachingRequests on the NameNode.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
