[jira] [Updated] (HIVE-21770) Support extraction of replication spec from notification event.

["Stamatis Zampetakis (Jira)" <ji...@apache.org>]

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

Stamatis Zampetakis updated HIVE-21770:
---------------------------------------
    Fix Version/s:     (was: 4.0.0)

I cleared the fixVersion field since this ticket is not resolved. Please review this ticket and if the fix is already committed to a specific version please set the version accordingly and mark the ticket as RESOLVED.

According to the JIRA guidelines (https://cwiki.apache.org/confluence/display/Hive/HowToContribute) the fixVersion should be set only when the issue is resolved/closed.

> Support extraction of replication spec from notification event. 
> ----------------------------------------------------------------
>
>                 Key: HIVE-21770
>                 URL: https://issues.apache.org/jira/browse/HIVE-21770
>             Project: Hive
>          Issue Type: Sub-task
>          Components: HiveServer2, repl
>    Affects Versions: 4.0.0
>            Reporter: mahesh kumar behera
>            Assignee: mahesh kumar behera
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: HIVE-21770.01.patch
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The notification event structure currently does not have the partition spec. Events which can span across multiple databases and tables, the database and table info can not be obtained from the event structure. To know the event is added for which partition, the event message has to be deserialized and the partition information can be obtained from it. 
>  * Each event handler has to expose a static API.
>  * The API should take the event as input and return the list of db name, table name and partition spec from it.
>  * If database name, table name or partition name is present in the event structure, then return it. If all these info are present then no need to deserialize the message. Later if these info are added to the event structure then it will be useful. 
>  * Deserialize the message and create the list of name and return through a partition info class object.
>  * If the table is not partitioned or is table level event, then set the partition info as null. Same for table info incase of db level events.



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