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

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HIVE-21770?focusedWorklogId=442505&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-442505 ]

ASF GitHub Bot logged work on HIVE-21770:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 08/Jun/20 00:24
            Start Date: 08/Jun/20 00:24
    Worklog Time Spent: 10m 
      Work Description: github-actions[bot] commented on pull request #740:
URL: https://github.com/apache/hive/pull/740#issuecomment-640302943


   This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
   Feel free to reach out on the dev@hive.apache.org list if the patch is in need of reviews.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 442505)
    Time Spent: 0.5h  (was: 20m)

> 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
>             Fix For: 4.0.0
>
>         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.3.4#803005)