[
https://issues.apache.org/jira/browse/HIVE-17385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16144111#comment-16144111
]
Daniel Dai commented on HIVE-17385:
-----------------------------------
Yes, we shall use the same logic for both bootstrap and incremental dump, nice
catch. However, shall we simply skip non-native table instead of throw
exception? Also why do we do null check on ImportSemanticAnalyzer? Do you see a
case we load a null table?
> Fix incremental repl error for non-native tables
> ------------------------------------------------
>
> Key: HIVE-17385
> URL: https://issues.apache.org/jira/browse/HIVE-17385
> Project: Hive
> Issue Type: Bug
> Components: repl
> Reporter: Tao Li
> Assignee: Tao Li
> Attachments: HIVE-17385.1.patch, HIVE-17385.2.patch,
> HIVE-17385.3.patch, HIVE-17385.4.patch
>
>
> See below error with incremental replication for non-native (storage handler
> based) tables. The bug is that we are not checking a table should be
> dumped/exported or not during incremental dump.
> 2017-08-02T12:31:48,195 ERROR [HiveServer2-Background-Pool: Thread-8078]:
> exec.DDLTask (DDLTask.java:failed(632)) -
> org.apache.hadoop.hive.ql.metadata.HiveException:
> MetaException(message:LOCATION may not be specified for HBase.)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
