You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Ashutosh Bapat (JIRA)" <ji...@apache.org> on 2019/05/02 09:54:00 UTC
[jira] [Updated] (HIVE-21677) Using strict managed tables for ACID
table testing (Replication tests)
[ https://issues.apache.org/jira/browse/HIVE-21677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ashutosh Bapat updated HIVE-21677:
----------------------------------
Description:
The replication tests which exclusively test ACID table replication are adding transactional properties to the create table/alter table statements when creating the table. Instead they should use hive.strict.managed.tables = true in those tests. Tests derived from BaseReplicationScenariosAcidTables, TestStatsReplicationScenariosACID, TestStatsReplicationScenariosACIDNoAutogather, TestStatsReplicationScenariosMM, TestStatsReplicationScenariosMMNoAutogather and TestReplicationScenariosIncrementalLoadAcidTables are examples of those. Change all such tests use hive.strict.managed.tables = true. Some of these tests create non-acid tables for testing, which will then require explicit 'transactional'=false set when creating the tables.
With this change we might see some test failures (See subtasks). Please create subtasks for those so that it can be tracked within this JIRA.
was:
The replication tests which exclusively test ACID table replication are adding transactional properties to the create table/alter table statements when creating the table. Instead they should use hive.strict.managed.tables = true in those tests. Tests derived from BaseReplicationScenariosAcidTables, and org.apache.hadoop.hive.ql.parse.TestReplicationScenariosIncrementalLoadAcidTables are examples of those. Change all such tests use hive.strict.managed.tables = true. Some of these tests create non-acid tables for testing, which will then require explicit 'transactional'=false set when creating the tables.
With this change we might see some test failures (See subtasks). Please create subtasks for those so that it can be tracked within this JIRA.
> Using strict managed tables for ACID table testing (Replication tests)
> ----------------------------------------------------------------------
>
> Key: HIVE-21677
> URL: https://issues.apache.org/jira/browse/HIVE-21677
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2, repl
> Affects Versions: 4.0.0
> Reporter: Ashutosh Bapat
> Priority: Major
>
> The replication tests which exclusively test ACID table replication are adding transactional properties to the create table/alter table statements when creating the table. Instead they should use hive.strict.managed.tables = true in those tests. Tests derived from BaseReplicationScenariosAcidTables, TestStatsReplicationScenariosACID, TestStatsReplicationScenariosACIDNoAutogather, TestStatsReplicationScenariosMM, TestStatsReplicationScenariosMMNoAutogather and TestReplicationScenariosIncrementalLoadAcidTables are examples of those. Change all such tests use hive.strict.managed.tables = true. Some of these tests create non-acid tables for testing, which will then require explicit 'transactional'=false set when creating the tables.
> With this change we might see some test failures (See subtasks). Please create subtasks for those so that it can be tracked within this JIRA.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)