[
https://issues.apache.org/jira/browse/HDFS-12491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16886220#comment-16886220
]
Hadoop QA commented on HDFS-12491:
----------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 5s{color}
| {color:red} HDFS-12491 does not apply to trunk. Rebase required? Wrong
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HDFS-12491 |
| Console output |
https://builds.apache.org/job/PreCommit-HDFS-Build/27236/console |
| Powered by | Apache Yetus 0.8.0 http://yetus.apache.org |
This message was automatically generated.
> Support wildcard in CLASSPATH for libhdfs
> -----------------------------------------
>
> Key: HDFS-12491
> URL: https://issues.apache.org/jira/browse/HDFS-12491
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: libhdfs
> Affects Versions: 2.8.0
> Reporter: John Zhuge
> Assignee: Muhammad Samir Khan
> Priority: Major
> Attachments: HDFS-12491.001.patch, testWildCard.sh
>
>
> According to libhdfs doc, wildcard in CLASSPATH is not support:
> bq. The most common problem is the CLASSPATH is not set properly when calling
> a program that uses libhdfs. Make sure you set it to all the Hadoop jars
> needed to run Hadoop itself as well as the right configuration directory
> containing hdfs-site.xml. It is not valid to use wildcard syntax for
> specifying multiple jars. It may be useful to run hadoop classpath --glob or
> hadoop classpath --jar <path> to generate the correct classpath for your
> deployment.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
