[
https://issues.apache.org/jira/browse/HDFS-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Wang updated HDFS-6345:
------------------------------
Attachment: hdfs-6345-2.patch
Thanks for reviewing Colin, new patch adds better comments. The if check in
CacheManager is a bit tricky, since it's used to break out of the loop either
if the directive was not found (since it should be the first item in the
tailMap), or if we found it and are on the second item. Made the comment say
that.
I think the test failure is also a flake, saw it on another JIRA and works okay
locally.
> DFS.listCacheDirectives() should allow filtering based on cache directive ID
> ----------------------------------------------------------------------------
>
> Key: HDFS-6345
> URL: https://issues.apache.org/jira/browse/HDFS-6345
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: caching
> Affects Versions: 2.4.0
> Reporter: Lenni Kuff
> Assignee: Andrew Wang
> Attachments: hdfs-6345-1.patch, hdfs-6345-2.patch
>
>
> DFS.listCacheDirectives() should allow filtering based on cache directive ID.
> Currently it throws an exception.
> For example:
> {code}
> long directiveId = <some id value>;
> CacheDirectiveInfo filter = new CacheDirectiveInfo.Builder()
> .setId(directiveId)
> .build();
> RemoteIterator<CacheDirectiveEntry> itr = dfs.listCacheDirectives(filter);
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
