[HIVE-21677] Using strict managed tables for ACID table testing (Replication tests)

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.0.0
• Fix Version/s: 4.0.0-alpha-1
• Component/s: HiveServer2, repl
• Assignee: Ashutosh Bapat
• Reporter: Ashutosh Bapat
• Created: 02/May/19 09:29
• Updated: 17/Nov/22 08:51
• Resolved: 09/May/19 05:41

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.

Sub-Tasks

• CTAS creating a Full ACID partitioned table fails because of no writeId.: Resolved
• Replicating a CTAS event creating an MM table fails.: Closed
• Replication scenarios should be tested with hive.strict.managed.tables set to true.: Patch Available
• CMV creating a Full ACID partitioned table fails because of no writeId: Closed