Hi Hive devs, I’m writing to understand the removal of ATSHook in Hive 4 and to ask for guidance on the recommended path forward.
Context * We had been using ATSHook primarily so that Tez View (Tez UI) could display richer Hive-related metadata alongside Tez DAGs. * After upgrading to Hive 4, we noticed ATSHook class is no longer available. Tez’s own ATS history logging still shows DAGs in Tez View, but we appear to be missing the Hive-specific annotations that ATSHook used to publish. Questions 1. Rationale: Could you share the reasoning behind removing ATSHook in Hive 4? I found a JIRA ticket, but it did not have much information regarding the same(https://issues.apache.org/jira/browse/HIVE-20078). 2. Tez View impact: Was the expectation that Tez View should rely solely on Tez’s history logging to ATS, without any Hive-published context? Is there a supported way in Hive 4 to restore the extra Hive query metadata that ATSHook used to send to ATS/Tez View? Or Use Tez’s ATS history logging alone and accept the loss of Hive annotations? 3. Replacement: Is there a 1:1 replacement for ATSHook, or an officially recommended alternative? 4. Guidance/docs: Are there migration notes or documentation for clusters that previously depended on ATSHook for Tez View integration? Any pointers, best practices, or documentation would be greatly appreciated. Thanks in advance for your help and for all the work on Hive 4. Best regards, Vikram Ahuja
