You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Xuefu Zhang (JIRA)" <ji...@apache.org> on 2016/04/27 00:55:12 UTC
[jira] [Updated] (HIVE-13611) add jar causes beeline not to output
log messages
[ https://issues.apache.org/jira/browse/HIVE-13611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xuefu Zhang updated HIVE-13611:
-------------------------------
Description:
After adding a jar in beeline warning messages and job log ouptut are no longer shown. This only occurs if you use short connection strings (e.g. jdbc:hive2://). Example below:
{code}
0: jdbc:hive2://nightly55-1.gce.cloudera.com:> !connect jdbc:hive2://
Connecting to jdbc:hive2://
Enter username for jdbc:hive2://: hive
Enter password for jdbc:hive2://: ****
Connected to: Apache Hive (version 1.1.0-cdh5.5.4)
Driver: Hive JDBC (version 1.1.0-cdh5.5.4)
Transaction isolation: TRANSACTION_REPEATABLE_READ
1: jdbc:hive2://> select count(*) from sample_07 limit 1;
INFO : Number of reduce tasks determined at compile time: 1
INFO : In order to change the average load for a reducer (in bytes):
INFO : set hive.exec.reducers.bytes.per.reducer=<number>
INFO : In order to limit the maximum number of reducers:
INFO : set hive.exec.reducers.max=<number>
INFO : In order to set a constant number of reducers:
INFO : set mapreduce.job.reduces=<number>
INFO : number of splits:1
INFO : Submitting tokens for job: job_1461621650734_0020
INFO : The url to track the job: http://nightly55-1.gce.cloudera.com:8088/proxy/application_1461621650734_0020/
INFO : Starting Job = job_1461621650734_0020, Tracking URL = http://nightly55-1.gce.cloudera.com:8088/proxy/application_1461621650734_0020/
INFO : Kill Command = /usr/lib/hadoop/bin/hadoop job -kill job_1461621650734_0020
INFO : Hadoop job information for Stage-1: number of mappers: 1; number of reducers: 1
INFO : 2016-04-26 01:36:04,297 Stage-1 map = 0%, reduce = 0%
INFO : 2016-04-26 01:36:11,802 Stage-1 map = 100%, reduce = 0%, Cumulative CPU 1.52 sec
INFO : 2016-04-26 01:36:19,419 Stage-1 map = 100%, reduce = 100%, Cumulative CPU 3.25 sec
INFO : MapReduce Total cumulative CPU time: 3 seconds 250 msec
INFO : Ended Job = job_1461621650734_0020
+------+--+
| _c0 |
+------+--+
| 823 |
+------+--+
1 row selected (25.908 seconds)
1: jdbc:hive2://> add jar hdfs://some_nn.com/tmp/somedir/some_jar.jar
1: jdbc:hive2://> ;
converting to local hdfs://some_nn.com/tmp/somedir/some_jar.jar
Added [/tmp/93ca63a2-5019-4f37-b9b4-75f1740b53c8_resources/some_jar.jar] to class path
Added resources: [hdfs://some_nn.com/tmp/somedir/some_jar.jar]
No rows affected (0.179 seconds)
1: jdbc:hive2://> select count(*) from sample_07 limit 1;
+------+--+
| _c0 |
+------+--+
| 823 |
+------+--+
1: jdbc:hive2://>
{code}
was:
After adding a jar in beeline warning messages and job log ouptut are no longer shown. This only occurs if you use short connection strings (e.g. jdbc:hive2://). Example below:
0: jdbc:hive2://nightly55-1.gce.cloudera.com:> !connect jdbc:hive2://
Connecting to jdbc:hive2://
Enter username for jdbc:hive2://: hive
Enter password for jdbc:hive2://: ****
Connected to: Apache Hive (version 1.1.0-cdh5.5.4)
Driver: Hive JDBC (version 1.1.0-cdh5.5.4)
Transaction isolation: TRANSACTION_REPEATABLE_READ
1: jdbc:hive2://> select count(*) from sample_07 limit 1;
INFO : Number of reduce tasks determined at compile time: 1
INFO : In order to change the average load for a reducer (in bytes):
INFO : set hive.exec.reducers.bytes.per.reducer=<number>
INFO : In order to limit the maximum number of reducers:
INFO : set hive.exec.reducers.max=<number>
INFO : In order to set a constant number of reducers:
INFO : set mapreduce.job.reduces=<number>
INFO : number of splits:1
INFO : Submitting tokens for job: job_1461621650734_0020
INFO : The url to track the job: http://nightly55-1.gce.cloudera.com:8088/proxy/application_1461621650734_0020/
INFO : Starting Job = job_1461621650734_0020, Tracking URL = http://nightly55-1.gce.cloudera.com:8088/proxy/application_1461621650734_0020/
INFO : Kill Command = /usr/lib/hadoop/bin/hadoop job -kill job_1461621650734_0020
INFO : Hadoop job information for Stage-1: number of mappers: 1; number of reducers: 1
INFO : 2016-04-26 01:36:04,297 Stage-1 map = 0%, reduce = 0%
INFO : 2016-04-26 01:36:11,802 Stage-1 map = 100%, reduce = 0%, Cumulative CPU 1.52 sec
INFO : 2016-04-26 01:36:19,419 Stage-1 map = 100%, reduce = 100%, Cumulative CPU 3.25 sec
INFO : MapReduce Total cumulative CPU time: 3 seconds 250 msec
INFO : Ended Job = job_1461621650734_0020
+------+--+
| _c0 |
+------+--+
| 823 |
+------+--+
1 row selected (25.908 seconds)
1: jdbc:hive2://> add jar hdfs://some_nn.com/tmp/somedir/some_jar.jar
1: jdbc:hive2://> ;
converting to local hdfs://some_nn.com/tmp/somedir/some_jar.jar
Added [/tmp/93ca63a2-5019-4f37-b9b4-75f1740b53c8_resources/some_jar.jar] to class path
Added resources: [hdfs://some_nn.com/tmp/somedir/some_jar.jar]
No rows affected (0.179 seconds)
1: jdbc:hive2://> select count(*) from sample_07 limit 1;
+------+--+
| _c0 |
+------+--+
| 823 |
+------+--+
1: jdbc:hive2://>
> add jar causes beeline not to output log messages
> -------------------------------------------------
>
> Key: HIVE-13611
> URL: https://issues.apache.org/jira/browse/HIVE-13611
> Project: Hive
> Issue Type: Bug
> Components: Beeline
> Affects Versions: 1.1.0
> Reporter: Thomas Scott
> Priority: Minor
>
> After adding a jar in beeline warning messages and job log ouptut are no longer shown. This only occurs if you use short connection strings (e.g. jdbc:hive2://). Example below:
> {code}
> 0: jdbc:hive2://nightly55-1.gce.cloudera.com:> !connect jdbc:hive2://
> Connecting to jdbc:hive2://
> Enter username for jdbc:hive2://: hive
> Enter password for jdbc:hive2://: ****
> Connected to: Apache Hive (version 1.1.0-cdh5.5.4)
> Driver: Hive JDBC (version 1.1.0-cdh5.5.4)
> Transaction isolation: TRANSACTION_REPEATABLE_READ
> 1: jdbc:hive2://> select count(*) from sample_07 limit 1;
> INFO : Number of reduce tasks determined at compile time: 1
> INFO : In order to change the average load for a reducer (in bytes):
> INFO : set hive.exec.reducers.bytes.per.reducer=<number>
> INFO : In order to limit the maximum number of reducers:
> INFO : set hive.exec.reducers.max=<number>
> INFO : In order to set a constant number of reducers:
> INFO : set mapreduce.job.reduces=<number>
> INFO : number of splits:1
> INFO : Submitting tokens for job: job_1461621650734_0020
> INFO : The url to track the job: http://nightly55-1.gce.cloudera.com:8088/proxy/application_1461621650734_0020/
> INFO : Starting Job = job_1461621650734_0020, Tracking URL = http://nightly55-1.gce.cloudera.com:8088/proxy/application_1461621650734_0020/
> INFO : Kill Command = /usr/lib/hadoop/bin/hadoop job -kill job_1461621650734_0020
> INFO : Hadoop job information for Stage-1: number of mappers: 1; number of reducers: 1
> INFO : 2016-04-26 01:36:04,297 Stage-1 map = 0%, reduce = 0%
> INFO : 2016-04-26 01:36:11,802 Stage-1 map = 100%, reduce = 0%, Cumulative CPU 1.52 sec
> INFO : 2016-04-26 01:36:19,419 Stage-1 map = 100%, reduce = 100%, Cumulative CPU 3.25 sec
> INFO : MapReduce Total cumulative CPU time: 3 seconds 250 msec
> INFO : Ended Job = job_1461621650734_0020
> +------+--+
> | _c0 |
> +------+--+
> | 823 |
> +------+--+
> 1 row selected (25.908 seconds)
> 1: jdbc:hive2://> add jar hdfs://some_nn.com/tmp/somedir/some_jar.jar
> 1: jdbc:hive2://> ;
> converting to local hdfs://some_nn.com/tmp/somedir/some_jar.jar
> Added [/tmp/93ca63a2-5019-4f37-b9b4-75f1740b53c8_resources/some_jar.jar] to class path
> Added resources: [hdfs://some_nn.com/tmp/somedir/some_jar.jar]
> No rows affected (0.179 seconds)
> 1: jdbc:hive2://> select count(*) from sample_07 limit 1;
> +------+--+
> | _c0 |
> +------+--+
> | 823 |
> +------+--+
> 1: jdbc:hive2://>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)