Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Naming Hive TEZ session (not individual DAG)

Solved Go to solution
Highlighted

Naming Hive TEZ session (not individual DAG)

New Contributor

Setting "hive.query.name" will influence the query name that is shown for an individual DAG on the TEZ UI.

But how do we influence the YARN application name of a complete TEZ session that is shown on the YARN UI?

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Naming Hive TEZ session (not individual DAG)

New Contributor

Try --hiveconf hive.session.id=appName

4 REPLIES 4

Re: Naming Hive TEZ session (not individual DAG)

Rising Star

Currently a query that spawns a yarn job cannot be influenced independently, like it is shown in DAG, reason being is that resources (appplication id) used by any given query, can be reused by a different one, so its not a 1:1 relation

Re: Naming Hive TEZ session (not individual DAG)

New Contributor

Try --hiveconf hive.session.id=appName

Re: Naming Hive TEZ session (not individual DAG)

New Contributor

Thanks a lot @mungeol heo - that setting does the trick.

Do you happen to know whether hive.session.id should be globally unique? On first tests, it seems to work to reuse the same hive.session.id across multiple yarn applications, but it feels a bit dangerous as the setting is named "id".

Re: Naming Hive TEZ session (not individual DAG)

New Contributor

I have not experienced any problem yet.

But, It is better be globally unique.

Don't have an account?
Coming from Hortonworks? Activate your account here