[ 
https://issues.apache.org/jira/browse/HDFS-7824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14376839#comment-14376839
 ] 

Xiaoyu Yao commented on HDFS-7824:
----------------------------------

Thanks [~arpitagarwal] or the help!. All failures are directly or indirectly 
caused by missing the new Builder class 
{code}org.apache.hadoop.fs.ContentSummary$Builder {code} added from this patch. 
Looks like the jars build for this patch is overwritten by other Jenkins run. I 
can't repro the failure on my local machine either.

{code}
The failures are caused by missing Caused by: java.lang.ClassNotFoundException: 
org.apache.hadoop.fs.ContentSummary$Builder
        at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
        at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
{code}

> GetContentSummary API and its namenode implementaion for Storage Type 
> Quota/Usage
> ---------------------------------------------------------------------------------
>
>                 Key: HDFS-7824
>                 URL: https://issues.apache.org/jira/browse/HDFS-7824
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: datanode, namenode
>            Reporter: Xiaoyu Yao
>            Assignee: Xiaoyu Yao
>         Attachments: HDFS-7824.00.patch, HDFS-7824.01.patch, 
> HDFS-7824.02.patch, HDFS-7824.03.patch
>
>
> This JIRA is opened to provide API support of GetContentSummary with storage 
> type quota and usage information. It includes namenode implementation, client 
> namenode RPC protocol and Content.Counts refactoring. It is required by 
> HDFS-7701 (CLI to display storage type quota and usage).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to