[jira] [Updated] (HIVE-28745) Introduce HiveOperation enum values for certain operations like: INSERT, DELETE, MERGE, UPDATE

["László Bodor (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HIVE-28745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

László Bodor updated HIVE-28745:
--------------------------------
    Summary: Introduce HiveOperation enum values for certain operations like: INSERT, DELETE, MERGE, UPDATE  (was: Introduce HiveOperation enum values for certain operations like: INSERT, IOW, DELETE, MERGE, UPDATE)

> Introduce HiveOperation enum values for certain operations like: INSERT, DELETE, MERGE, UPDATE
> ----------------------------------------------------------------------------------------------
>
>                 Key: HIVE-28745
>                 URL: https://issues.apache.org/jira/browse/HIVE-28745
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: László Bodor
>            Priority: Major
>
> HiveOperation enum values should be introduced for above-mentioned queries, which are currently considered as HiveOperation.QUERY. 
> Challenges: 
> 1. [HiveOperation contains auth and transactional information as well|https://github.com/apache/hive/blob/04c1102929b2253ad74272b7d5d8f9a01914620c/ql/src/java/org/apache/hadoop/hive/ql/plan/HiveOperation.java#L264], introducing new value should respect old behavior
> 2. queryState.getCommandType (which returns a HiveOperation) is printed in all q.out's, so changing this would break a lot of q.outs where we currently have
> {code}
> PREHOOK: type: QUERY
> POSTHOOK: type: QUERY
> {code}
> I don't want to break such things but QUERY is not sufficient for some query tracking purposes (like query history)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)