[
https://issues.apache.org/jira/browse/HIVE-16727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025967#comment-16025967
]
anishek commented on HIVE-16727:
--------------------------------
[~sankarh]
* TestReplicationScenarios : The test case seems to test both partitioned and
unpartitioned cases in the same test case, It would be easier to spot errors if
they were split if into two tests cases one for partition and another for
unpartitioned tables, will also additionally make it more readable. Might be
possible to abstract most of the commands using the WarehouseInstance
representation.
* InsertEvent: get_table_core could be used since this is for internal hive
classes.
* There are unused Imports in most of the classes above.
> REPL DUMP for insert event should't fail if the table is already dropped.
> -------------------------------------------------------------------------
>
> Key: HIVE-16727
> URL: https://issues.apache.org/jira/browse/HIVE-16727
> Project: Hive
> Issue Type: Sub-task
> Components: Hive, repl
> Affects Versions: 2.1.0
> Reporter: Sankar Hariappan
> Assignee: Sankar Hariappan
> Labels: DR, replication
> Attachments: HIVE-16727.01.patch
>
>
> Currently, insert event doesn't log the table object as part of event
> notification message. During dump, the table object is obtained from
> metastore which can be null if the table is already dropped and hence REPL
> DUMP fails.
> Steps:
> 1. Bootstrap dump/load with a table.
> 2. Insert into the table.
> 3. Drop the table.
> 4. REPL DUMP (incremental).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
