[HIVE-18444] when creating transactional table make sure location has no data

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.0.0
• Component/s: Transactions
• Target Version/s: 4.0.0
• Assignee: Unassigned Assign to me
• Reporter: Eugene Koifman
• Created: 11/Jan/18 20:49
• Updated: 23/Aug/19 04:10

Description

if a user creates a new transactional table but sets a location to some place that already has data any number of things can break.

Data may not be in Acid format, it may have been written by another cluster and txnids won't make sense in current cluster. Once per table writeIDs (HIVE-18192) are there, if the data was written by another table, writeIDs won't match.

This could actually work if the data at the existing location was not written by an acid write but it would be safer/cleaner to just prevent this (at least at first).

Issue Links

• relates to: HIVE-18192 Introduce WriteID per table rather than using global transaction ID