[ https://issues.apache.org/jira/browse/HBASE-11118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14057426#comment-14057426 ]
André Kelpe commented on HBASE-11118: ------------------------------------- [~ndimiduk] no luck with the snapshot repository: $ gradle clean build The TaskContainer.add() method has been deprecated and is scheduled to be removed in Gradle 2.0. Please use the create() method instead. :cascading-hbase-hadoop2-mr1:clean UP-TO-DATE :cascading-hbase-hadoop2-mr1:compileJava Download https://repository.apache.org/content/repositories/snapshots/org/apache/hbase/hbase-hadoop2-compat/0.98.4-11118-SNAPSHOT/hbase-hadoop2-compat-0.98.4-11118-20140702.231131-2.pom FAILURE: Build failed with an exception. * What went wrong: Could not resolve all dependencies for configuration ':cascading-hbase-hadoop2-mr1:compile'. > Could not resolve org.apache.hbase:${compat.module}:0.98.4-11118-SNAPSHOT. Required by: cascading-hbase:cascading-hbase-hadoop2-mr1:2.5.0-wip-dev > org.apache.hbase:hbase-server:0.98.4-11118-SNAPSHOT cascading-hbase:cascading-hbase-hadoop2-mr1:2.5.0-wip-dev > org.apache.hbase:hbase-server:0.98.4-11118-SNAPSHOT > org.apache.hbase:hbase-prefix-tree:0.98.4-11118-SNAPSHOT > java.lang.NullPointerException (no error message) > Unable to load Maven meta-data from http://repo1.maven.org/maven2/org/apache/hbase/${compat.module}/0.98.4-11118-SNAPSHOT/maven-metadata.xml. > java.lang.IllegalArgumentException (no error message) > Unable to load Maven meta-data from http://conjars.org/repo/org/apache/hbase/${compat.module}/0.98.4-11118-SNAPSHOT/maven-metadata.xml. > java.lang.IllegalArgumentException (no error message) > Unable to load Maven meta-data from https://repository.apache.org/content/repositories/releases/org/apache/hbase/${compat.module}/0.98.4-11118-SNAPSHOT/maven-metadata.xml. > java.lang.IllegalArgumentException (no error message) > Unable to load Maven meta-data from https://repository.apache.org/content/repositories/snapshots/org/apache/hbase/${compat.module}/0.98.4-11118-SNAPSHOT/maven-metadata.xml. > java.lang.IllegalArgumentException (no error message) * Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. BUILD FAILED Total time: 18.433 secs > non environment variable solution for "IllegalAccessError: class > com.google.protobuf.ZeroCopyLiteralByteString cannot access its superclass > com.google.protobuf.LiteralByteString" > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: HBASE-11118 > URL: https://issues.apache.org/jira/browse/HBASE-11118 > Project: HBase > Issue Type: Bug > Affects Versions: 0.98.2 > Reporter: André Kelpe > Priority: Blocker > Fix For: 0.99.0, 0.98.4, 2.0.0 > > Attachments: 11118.098-0.txt, 11118.098.txt, 11118.bytestringer.txt, > 1118.suggested.undoing.optimization.on.clientside.txt, > 1118.suggested.undoing.optimization.on.clientside.txt, > HBASE-11118-0.98.00.patch, HBASE-11118-0.98.01.patch, > HBASE-11118-0.98.02.patch, HBASE-11118-0.98.patch.gz, > HBASE-11118-trunk.patch.gz, HBASE-11118.00.patch, HBASE-11118.01.patch, > HBASE-11118.02.patch, shade_attempt.patch > > > I am running into the problem described in > https://issues.apache.org/jira/browse/HBASE-10304, while trying to use a > newer version within cascading.hbase > (https://github.com/cascading/cascading.hbase). > One of the features of cascading.hbase is that you can use it from lingual > (http://www.cascading.org/projects/lingual/), our SQL layer for hadoop. > lingual has a notion of providers, which are fat jars that we pull down > dynamically at runtime. Those jars give users the ability to talk to any > system or format from SQL. They are added to the classpath programmatically > before we submit jobs to a hadoop cluster. > Since lingual does not know upfront , which providers are going to be used in > a given run, the HADOOP_CLASSPATH trick proposed in the JIRA above is really > clunky and breaks the ease of use we had before. No other provider requires > this right now. > It would be great to have a programmatical way to fix this, when using fat > jars. -- This message was sent by Atlassian JIRA (v6.2#6252)