[
https://issues.apache.org/jira/browse/HIVE-29191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18019517#comment-18019517
]
Stamatis Zampetakis commented on HIVE-29191:
--------------------------------------------
Hi [~vikramahuja_], thanks for raising this ticket. Can you please add a
concrete example with a sample script that is causing the problem and the full
stacktrace of the exception that you are hitting.
> Gracefully Handle Removed Configuration Properties in Hive 4 to Avoid Job
> Failures
> ----------------------------------------------------------------------------------
>
> Key: HIVE-29191
> URL: https://issues.apache.org/jira/browse/HIVE-29191
> Project: Hive
> Issue Type: Improvement
> Reporter: Vikram Ahuja
> Assignee: Vikram Ahuja
> Priority: Major
> Labels: pull-request-available
>
> In Hive 4, certain configuration properties that existed in Hive 3 have been
> removed. Currently, if users run *HQL scripts* that still set these removed
> properties (via {{SET}} commands), Hive throws an *exception* as that config
> is no longer present, causing the job execution to abruptly fail.
> This behaviour can be disruptive for users migrating from Hive 3 to Hive 4,
> especially in automated workflows where HQL files are reused.
> *Proposed Improvement:*
> Introduce a *new Hive property* (e.g.,
> {{{}hive.ignore.removed.configs.list{}}}) that contains a *comma-separated
> list* of removed configuration keys.
>
> *Behavior:*
> * When Hive encounters a {{SET}} command for a property listed in
> {{{}hive.ignore.removed.configs.list{}}}, it {*}does not throw an
> exception{*}.
> * Instead, Hive {*}ignores the setting{*}, continues execution, and logs a
> *WARN* message in HiveServer2
> * This ensures backward compatibility for scripts without impacting
> execution flow.
>
> *Benefits:*
> # *Improved Migration Experience* – Users upgrading to Hive 4 can continue
> using their existing HQL scripts without immediate modifications.
> # *Reduced Job Failures* – Prevents abrupt termination due to removed
> properties, allowing smoother workflow execution.
> # *Better User Awareness* – WARN logs inform users about deprecated/removed
> configs without disrupting execution.
> # *Configurable Behaviour* – Admins can control which removed configs are
> ignored, allowing flexibility.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
