[
https://issues.apache.org/jira/browse/HDFS-13909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821960#comment-16821960
]
Ayush Saxena commented on HDFS-13909:
-------------------------------------
Thanx [~elgoiri] for the comment.
I guess this shall not be that straight.
{code:java}
String path = (String)paramGetter.getParameterForContext(context);
objList[i] = CacheDirectiveInfo.Builder(path){code}
The builder shall expect a {{CacheDirectiveInfo}} not a string,
I guess we need to have changes in RemoteParam to let a cacheDirectiveInfo in
and even have some changes in the invocation calls too, since they expect
Remote Locations to replace it there and along with we need to provide the
namespace to trigger too.
Not a thing that isn't possible, need to check more, but would require changes
in the main invocation track for a Single API, whether we will be having any
functional advantage using this?
[~brahmareddy] [~surendrasingh] Any opinions here. :)
> RBF: Add Cache pools and directives related ClientProtocol apis
> ---------------------------------------------------------------
>
> Key: HDFS-13909
> URL: https://issues.apache.org/jira/browse/HDFS-13909
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Dibyendu Karmakar
> Assignee: Ayush Saxena
> Priority: Major
> Attachments: HDFS-13909-HDFS-13891-01.patch,
> HDFS-13909-HDFS-13891-02.patch
>
>
> Currently addCachePool, modifyCachePool, removeCachePool, listCachePools,
> addCacheDirective, modifyCacheDirective, removeCacheDirective,
> listCacheDirectives these APIs are not implemented in Router.
> This JIRA is intend to implement above mentioned APIs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
