hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexander Kolbasov <>
Subject Re: Getting access to hadoop output from Hive JDBC session
Date Wed, 13 Aug 2014 04:00:34 GMT
On 8/12/14, 7:45 PM, "Thejas Nair" <> wrote:

>you are running HS2 in embedded mode, I think you should be able to get
>hadoop output by setting the log4j settings appropriately.
>If you were using a remote HS2, then you need a getLog api call, which is
>work in progress in one of the jiras.

I do run it in embedded mode. I tried playing with log4j settings and it
didnĀ¹t affect anything.

- Alex

>On Tue, Aug 12, 2014 at 6:17 PM, Alexander Kolbasov <>
>> Cross-posted from
>> Hello,
>> I am switching from Hive 0.9 to Hive 0.12 and decided to start using
>> metadata server mode. As it turns out, Hive1 JDBC driver connected as
>> "jdbc:hive://" only works via direct access to the metastore database.
>> Hive2 driver connected as "jdbc:hive2://" does work with the remote Hive
>> metastore server, but there is another serious difference in behavior.
>> When I was using Hive1 driver I saw Hadoop output - the information
>> Hive job ID and the usual Hadoop output showing percentages of map and
>> reduce done. The Hive2 driver silently waited for map/reduce to complete
>> and just produced the result.
>> As I can see, both Hive itself and beeline are able to get the same
>> output as I was getting with Hive1 driver, so it should be somehow
>> possible but it isn't clear how they do this. Can someone suggest the
>> to get Hadoop output with Hive2 JDBC driver?
>> Thanks for any help!
>> - Alex
>NOTICE: This message is intended for the use of the individual or entity
>which it is addressed and may contain information that is confidential,
>privileged and exempt from disclosure under applicable law. If the reader
>of this message is not the intended recipient, you are hereby notified
>any printing, copying, dissemination, distribution, disclosure or
>forwarding of this communication is strictly prohibited. If you have
>received this communication in error, please contact the sender
>and delete it from your system. Thank You.

View raw message