[
https://issues.apache.org/jira/browse/HIVE-11137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14610816#comment-14610816
]
Nishant Kelkar commented on HIVE-11137:
---------------------------------------
>From the hive.log, I see the following two issues:
{code}
2015-07-01 11:13:28,877 ERROR [Thread-17]: thrift.ThriftCLIService
(ThriftBinaryCLIService.java:run(101)) - Error starting HiveServer2: could not
start ThriftBinaryCLIService
org.apache.thrift.transport.TTransportException: Could not create ServerSocket
on address 0.0.0.0/0.0.0.0:10000.
at
org.apache.thrift.transport.TServerSocket.<init>(TServerSocket.java:109)
at
org.apache.thrift.transport.TServerSocket.<init>(TServerSocket.java:91)
at
org.apache.thrift.transport.TServerSocket.<init>(TServerSocket.java:87)
at
org.apache.hive.service.auth.HiveAuthFactory.getServerSocket(HiveAuthFactory.java:241)
at
org.apache.hive.service.cli.thrift.ThriftBinaryCLIService.run(ThriftBinaryCLIService.java:66)
at java.lang.Thread.run(Thread.java:744)
{code}
and
{code}
2015-07-01 11:13:18,009 DEBUG [main]: util.Shell
(Shell.java:checkHadoopHome(320)) - Failed to detect a valid hadoop home
directory
java.io.IOException: HADOOP_HOME or hadoop.home.dir are not set.
at org.apache.hadoop.util.Shell.checkHadoopHome(Shell.java:302)
at org.apache.hadoop.util.Shell.<clinit>(Shell.java:327)
at
org.apache.hadoop.hive.conf.HiveConf$ConfVars.findHadoopBinary(HiveConf.java:2375)
at
org.apache.hadoop.hive.conf.HiveConf$ConfVars.<clinit>(HiveConf.java:366)
at org.apache.hadoop.hive.conf.HiveConf.<clinit>(HiveConf.java:105)
at
org.apache.hive.service.auth.TestCustomAuthentication.setUp(TestCustomAuthentication.java:45)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
{code}
> In DateWritable remove the use of LazyBinaryUtils
> -------------------------------------------------
>
> Key: HIVE-11137
> URL: https://issues.apache.org/jira/browse/HIVE-11137
> Project: Hive
> Issue Type: Sub-task
> Reporter: Owen O'Malley
> Assignee: Nishant Kelkar
> Attachments: HIVE-11137.1.patch
>
>
> Currently the DateWritable class uses LazyBinaryUtils, which has a lot of
> dependencies.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
