Mailing-List: contact dev-help@pig.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@pig.apache.org
Date: Thu, 27 Sep 2012 08:59:07 +1100 (NCT)
From: "Cheolsoo Park (JIRA)" <jira@apache.org>
To: pig-dev@hadoop.apache.org
Message-ID: <1058577933.130891.1348696747921.JavaMail.jiratomcat@arcas>
In-Reply-To: <1749546955.4374.1345881059933.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (PIG-2891) HBaseStorage can't work with HBase
 0.94, as the connect method changed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Cheolsoo Park commented on PIG-2891:
------------------------------------

Hi Bill, thanks for the question.

So the original problem that Russell ran into is because he used the fat "pig.jar" with hbase-0.94. Since there is a mismatch between client (hbase-0.90) and server (hbase-0.94), the above exception is thrown. However, this problem can be worked around by using "pig-withouthadoop.jar", so there is no need for any immediate fix. So I think that this jira can be closed.

In the long term, we probably want to stop embedding hbase in the fat jar as Dmitriy suggested, but that can be done part of PIG-2885. Please let me know if anyone has objections.

Thanks!
                
> HBaseStorage can't work with HBase 0.94, as the connect method changed
> ----------------------------------------------------------------------
>
>                 Key: PIG-2891
>                 URL: https://issues.apache.org/jira/browse/PIG-2891
>             Project: Pig
>          Issue Type: Bug
>          Components: build, internal-udfs
>    Affects Versions: 0.10.0, 0.11
>         Environment: Mac OS X, HBase on local mode, Pig on local mode
>            Reporter: Russell Jurney
>            Assignee: Alan Gates
>              Labels: builtin, fun, happy, hbase, pants, udf
>             Fix For: 0.11, 0.10.1
>
>         Attachments: PIG-2891.patch
>
>
> Pig HBaseStorage doesn't work against a local mode HBase 0.94.1.
> Updating the JAR in ivy/libraries.properties addresses the issue, which is pasted here: 
> 2012-08-24 23:27:07,431 [main] ERROR org.apache.pig.tools.grunt.Grunt - ERROR 2999: Unexpected internal error. Not a host:port pair: ?'58971@russell-jurneys-macbook-pro.local10.0.1.11,55171,1345873780529
> 2012-08-24 23:27:07,431 [main] ERROR org.apache.pig.tools.grunt.Grunt - java.lang.IllegalArgumentException: Not a host:port pair: ?'58971@russell-jurneys-macbook-pro.local10.0.1.11,55171,1345873780529
> 	at org.apache.hadoop.hbase.HServerAddress.<init>(HServerAddress.java:60)
> 	at org.apache.hadoop.hbase.zookeeper.RootRegionTracker.dataToHServerAddress(RootRegionTracker.java:82)
> 	at org.apache.hadoop.hbase.zookeeper.RootRegionTracker.waitRootRegionLocation(RootRegionTracker.java:73)
> 	at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:575)
> 	at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:555)
> 	at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:684)
> 	at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:586)
> 	at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:555)
> 	at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:684)
> 	at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:590)
> 	at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:555)
> 	at org.apache.hadoop.hbase.client.HTable.<init>(HTable.java:171)
> 	at org.apache.hadoop.hbase.client.HTable.<init>(HTable.java:145)
> 	at org.apache.hadoop.hbase.mapreduce.TableOutputFormat.setConf(TableOutputFormat.java:196)
> 	at org.apache.pig.backend.hadoop.hbase.HBaseStorage.getOutputFormat(HBaseStorage.java:593)
> 	at org.apache.pig.newplan.logical.rules.InputOutputFileValidator$InputOutputFileVisitor.visit(InputOutputFileValidator.java:80)
> 	at org.apache.pig.newplan.logical.relational.LOStore.accept(LOStore.java:66)
> 	at org.apache.pig.newplan.DepthFirstWalker.depthFirst(DepthFirstWalker.java:64)
> 	at org.apache.pig.newplan.DepthFirstWalker.depthFirst(DepthFirstWalker.java:66)
> 	at org.apache.pig.newplan.DepthFirstWalker.depthFirst(DepthFirstWalker.java:66)
> 	at org.apache.pig.newplan.DepthFirstWalker.walk(DepthFirstWalker.java:53)
> 	at org.apache.pig.newplan.PlanVisitor.visit(PlanVisitor.java:50)
> 	at org.apache.pig.newplan.logical.rules.InputOutputFileValidator.validate(InputOutputFileValidator.java:45)
> 	at org.apache.pig.backend.hadoop.executionengine.HExecutionEngine.compile(HExecutionEngine.java:288)
> 	at org.apache.pig.PigServer.compilePp(PigServer.java:1310)
> 	at org.apache.pig.PigServer.executeCompiledLogicalPlan(PigServer.java:1247)
> 	at org.apache.pig.PigServer.execute(PigServer.java:1239)
> 	at org.apache.pig.PigServer.executeBatch(PigServer.java:333)
> 	at org.apache.pig.tools.grunt.GruntParser.executeBatch(GruntParser.java:136)
> 	at org.apache.pig.tools.grunt.GruntParser.parseStopOnError(GruntParser.java:197)
> 	at org.apache.pig.tools.grunt.GruntParser.parseStopOnError(GruntParser.java:169)
> 	at org.apache.pig.tools.grunt.Grunt.exec(Grunt.java:84)
> 	at org.apache.pig.Main.run(Main.java:602)
> 	at org.apache.pig.Main.main(Main.java:154)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:597)
> 	at org.apache.hadoop.util.RunJar.main(RunJar.java:156)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira