[jira] [Assigned] (IMPALA-14131) Add flag to configure the default value of "impala.disableHmsSync"

["Sai Hemanth Gantasala (Jira)" <ji...@apache.org>]

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

Sai Hemanth Gantasala reassigned IMPALA-14131:
----------------------------------------------

    Assignee: Sai Hemanth Gantasala

> Add flag to configure the default value of "impala.disableHmsSync"
> ------------------------------------------------------------------
>
>                 Key: IMPALA-14131
>                 URL: https://issues.apache.org/jira/browse/IMPALA-14131
>             Project: IMPALA
>          Issue Type: New Feature
>          Components: Catalog
>            Reporter: Quanlong Huang
>            Assignee: Sai Hemanth Gantasala
>            Priority: Major
>
> Users might want to roll out EventProcessor job by job and turn it off on all db/tables by default. It's tedious to set "impala.disableHmsSync" to "true" on all dbs. If a db has some tables that want to turn event processing on, users should set "impala.disableHmsSync" to "true" on all other tables in that db, which is also tedious.
> We need a catalogd startup flag like disable_hms_sync_by_default which is the default value of "impala.disableHmsSync" when it's missing in db/table properties. It's independent to hms_event_polling_interval_s that catalogds will still poll HMS events based on hms_event_polling_interval_s, but if disable_hms_sync_by_default is true, events on all db/tables will be skipped unless the db/table has property "impala.disableHmsSync"="false".
> CC [~hemanth619], [~VenuReddy] 



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org