[
https://issues.apache.org/jira/browse/HIVE-16684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015276#comment-16015276
]
Sankar Hariappan commented on HIVE-16684:
-----------------------------------------
[~sushanth]
I totally agree with your modifications. I'll make these changes to my local
branch as well to view it in pull request.
Request [~thejas] to review the patch.
{quote}
a) I was wondering if checking for InvalidTableException was sufficient, and
what happens when individual partitions in a table are dropped, since they have
a similar problem. However, that issue is not as easy to fix, and might need a
separate jira for it - for that scenario, PartitionIterable might need to be
updated, so as to allow it to configurably "skip over" partitions if it does
not find them at batch-fetch time, and then, call that form of
PartitionIterable from EximUtil. Note that this is not to say that this patch
needs to be updated for it, merely that that is another open issue that needs
addressing that is similar to this.
{quote}
Yes, for partition's drop case should be handled in a separate JIRA. Raised
JIRA https://issues.apache.org/jira/browse/HIVE-16706 to track this.
> Bootstrap REPL DUMP shouldn't fail when table is dropped after fetching the
> table names.
> ----------------------------------------------------------------------------------------
>
> Key: HIVE-16684
> URL: https://issues.apache.org/jira/browse/HIVE-16684
> Project: Hive
> Issue Type: Sub-task
> Components: Hive, repl
> Affects Versions: 2.1.0
> Reporter: Sankar Hariappan
> Assignee: Sankar Hariappan
> Attachments: HIVE-16684.01.patch, HIVE-16684.02.patch
>
>
> Currently, bootstrap dump will fail if the table does't exist when try to
> dump. This shall occur when table is dropped after REPL DUMP fetched the
> table names.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
