Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 04-07-2017 06:38 PM
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?
Created 06-28-2017 09:14 AM
Try --hiveconf hive.session.id=appName
Created 05-09-2017 02:12 AM
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
Created 06-28-2017 09:14 AM
Try --hiveconf hive.session.id=appName
Created 06-28-2017 12:20 PM
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".
Created 06-29-2017 01:17 AM
I have not experienced any problem yet.
But, It is better be globally unique.