[KUDU-382] Add coverage for and fix concurrent AlterSchema

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: M4.5
• Component/s: tablet
• Labels: alter-table roadmap-candidate
• Target Version/s: Feature Complete
• Assignee: Todd Lipcon
• Reporter: Todd Lipcon
• Created: 01/Jul/14 18:49
• Updated: 18/Jun/19 13:02
• Resolved: 15/Jul/15 15:57

Description

Our lack of good unit tests for AlterSchema was hiding the fact that its design has some major deficiencies. This is about writing better tests and designing a better solution.

Issue Links

• is related to: KUDU-181 Adding a column without a write default breaks TS restart
• is related to: KUDU-304 Support ALTER_TABLE transactions in consensus replicas
• relates to: KUDU-363 Need test coverage of alter + major delta compaction
• relates to: KUDU-391 TSAN failure in alter_table-test
• relates to: KUDU-461 Alter Table might re-use column IDs after drop/add column
• relates to: KUDU-462 TS wont restart after alter table which drops a column
• relates to: KUDU-457 Alter tablet fails when concurrent with a flush
• relates to: KUDU-273 client-test deadlocks if run in many iterations
• relates to: KUDU-384 heap-use-after-free in AlterTableTest.TestShutdownWithPendingTasks
• relates to: KUDU-464 client-test: Not implemented: AlterSchema not supported by MemRowSet

Sub-Tasks

• Write more unit tests for alter schema: Resolved
• Devise a solution for AlterSchema: Resolved
• Implement the new solution for AlterSchema: Resolved