-Re: Hadoop-common-2.2.0 cannot find PlatformName
Ted Yu 2013-12-05, 23:18
How did you launch your java client ?
Take a look at the sample command in this section:
On Fri, Dec 6, 2013 at 7:11 AM, Su, Xiandong <[EMAIL PROTECTED]> wrote:
> I am trying to have a simple java client to connect to HBase in HDP 2.0.
> I am using maven to manage my dependencies and using the same version for
> the jars as HDP 2.0 specified:
> I am getting the NoClassDefFoundError which is strange. It is used inside
> hadoop-common-2.2.0.jar which is brought in by hadoop-client. I would
> assume whatever jar that contains this class should have been a dependency
> of hadoop-common-2.2.0. But that seems not be the case here.
> Has anyone on the forum using the same version running into this issue?
> p.s. here is the full exception trace:
> java.lang.NoClassDefFoundError: org/apache/hadoop/util/PlatformName
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.hadoop.hbase.util.Methods.call(Methods.java:39)
> at org.apache.hadoop.hbase.security.User.call(User.java:414)
> at org.apache.hadoop.hbase.security.User.callStatic(User.java:404)
> at org.apache.hadoop.hbase.security.User.access$200(User.java:48)
> at org.apache.hadoop.hbase.security.User$SecureHadoopUser.(User.java:221)
> at org.apache.hadoop.hbase.security.User$SecureHadoopUser.(User.java:216)
> at org.apache.hadoop.hbase.security.User.getCurrent(User.java:139)
> at org.apache.hadoop.hbase.client.HConnectionKey.(HConnectionKey.java:67)
> at org.apache.hadoop.hbase.client.HBaseAdmin.(HBaseAdmin.java:182)
> IMPORTANT WARNING: Information contained in this email is intended for the
> use of the individual to whom it is addressed, and may contain information
> that is privileged, confidential, and exempt from disclosure under
> applicable law. If you are not the intended recipient, or the employee or
> agent responsible for delivering the message to the intended recipient, you
> are hereby notified that any dissemination, distribution, or copying of
> this communication is STRICTLY FORBIDDEN. If you have received this
> communication in error, please notify us immediately by return email and
> delete this document. Thank you.