hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tao Li (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-17422) Don't dump non-native/temporary tables during incremental dump
Date Tue, 12 Sep 2017 19:47:00 GMT

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

Tao Li updated HIVE-17422:
--------------------------
    Description: 
Currently during incremental dump, the non-native/temporary table info is partially dumped
in metadata file and will be ignored later by the repl load. We can optimize it by moving
the check (whether the table should be exported or not) earlier so that we don't save any
info to dump file for such types of tables. CreateTableHandler already has this optimization,
so we just need to apply similar logic to other scenarios.

The change is to apply the EximUtil.shouldExportTable check to all scenarios (e.g. alter table)
that calls into the common dump method. 

  was:Currently during incremental dump, the non-native/temporary table info is partially
dumped in metadata file and will be ignored later by the repl load. We can optimize it by
moving the check (whether the table should be exported or not) earlier so that we don't save
any info to dump file for such types of tables. CreateTableHandler already has this optimization,
so we just need to apply similar logic to other scenarios.


> Don't dump non-native/temporary tables during incremental dump
> --------------------------------------------------------------
>
>                 Key: HIVE-17422
>                 URL: https://issues.apache.org/jira/browse/HIVE-17422
>             Project: Hive
>          Issue Type: Improvement
>          Components: repl
>            Reporter: Tao Li
>            Assignee: Tao Li
>
> Currently during incremental dump, the non-native/temporary table info is partially dumped
in metadata file and will be ignored later by the repl load. We can optimize it by moving
the check (whether the table should be exported or not) earlier so that we don't save any
info to dump file for such types of tables. CreateTableHandler already has this optimization,
so we just need to apply similar logic to other scenarios.
> The change is to apply the EximUtil.shouldExportTable check to all scenarios (e.g. alter
table) that calls into the common dump method. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message