[
https://issues.apache.org/jira/browse/HIVE-21677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sankar Hariappan resolved HIVE-21677.
-------------------------------------
Resolution: Fixed
Assignee: Ashutosh Bapat
Fix Version/s: 4.0.0
> 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
> Assignee: Ashutosh Bapat
> Priority: Major
> Fix For: 4.0.0
>
>
> 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)
