Check
https://community.hortonworks.com/questions/115159/hive-servers-in-same-cluster-use-different-hive-lo.html#answer-115162
On Fri, Jul 28, 2017 at 3:12 PM, Mungeol Heo <mungeol@gmail.com> wrote:
> Hello,
>
> Here are logs from two hiveserver2.log file.
>
> --- f
The answer for the second question is that they use different
hive-log4j.properties.
Check
https://community.hortonworks.com/questions/115159/hive-servers-in-same-cluster-use-different-hive-lo.html#answer-115162
On Fri, Jul 28, 2017 at 2:15 PM, Mungeol Heo <mungeol@gmail.com>
Hello,
Here are logs from two hiveserver2.log file.
--- first which is strange ---
2017-07-28 14:46:10,051 DEBUG [main]: server.HiveServer2
(HiveServer2.java:main(586)) -
Logging initialized using configuration in
ogging-level-of-the-hiveserver2log.html
On Fri, Jul 28, 2017 at 12:32 PM, Mungeol Heo <mungeol@gmail.com> wrote:
> Hello.
>
> As I mentioned at the title of this question, I wonder how to set the
> logging level of the hiveserver2.log file in HDP.
>
> And I am also cu
Hello.
As I mentioned at the title of this question, I wonder how to set the
logging level of the hiveserver2.log file in HDP.
And I am also curios about why one of my hiveserver2.log file's
logging level is debug while another is not.
--- First hiveserver2.log which has debug log ---
Hello.
I found the log addressed below in the hiveserver2.log file.
2017-07-10 23:35:02,389 DEBUG [IPC Client (1639759054) connection to
host.name/10.10.10.18:8020 from hdfs]: ipc.Client
(Client.java:run(1025)) - IPC Client (1639759054) connection to
host.name/10.10.10.18:8020 from hdfs:
Try --hiveconf hive.session.id=session_id_name.
Then, the job name will be HIVE-session_id_name.
AFAK, this is the best option for your request.
If there is a better way, please share here.
Hope it helps.
Thank you.
On Sat, Jan 21, 2017 at 6:56 AM, Gopal Vijayaraghavan wrote:
Hi, Appan.
you can just simply check the amount of data your query reads from the
table. or the number of the mapper for running that query.
then, you can know whether it filtering or scanning all table.
Of course, it is a lazy approach. but, you can give a try.
I think query 1 should work fine.