[HIVE-15148] disallow loading data into bucketed tables (by default)

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.3.0
• Labels: TODOC2.2
• Assignee: Sergey Shelukhin
• Reporter: Sergey Shelukhin
• Created: 08/Nov/16 01:58
• Updated: 21/Jul/17 18:26
• Resolved: 18/Nov/16 19:15

Description

A few q file tests still use the following, allowed, pattern:

CREATE TABLE bucket_small (key string, value string) partitioned by (ds string) CLUSTERED BY (key) INTO 2 BUCKETS STORED AS TEXTFILE;
load data local inpath '../../data/files/smallsrcsortbucket1outof4.txt' INTO TABLE bucket_small partition(ds='2008-04-08');
load data local inpath '../../data/files/smallsrcsortbucket2outof4.txt' INTO TABLE bucket_small partition(ds='2008-04-08');

This relies on the user to load the correct number of files with correctly hashed data and the correct order of file names; if there's some discrepancy in any of the above, the queries will fail or may produce incorrect results if some bucket-based optimizations kick in.
Additionally, even if the user does everything correctly, as far as I know some code derives bucket number from file name, which won't work in this case (as opposed to getting buckets based on the order of files, which will work here but won't work as per HIVE-14970... sigh).

Hive enforces bucketing in other cases (the check cannot even be disabled these days), so I suggest that we either prohibit the above outright, or at least add a safety config setting that would disallow it by default.

Issue Links

• relates to: HIVE-12727 refactor Hive strict checks to be more granular, allow order by no limit and no partition filter by default for now
• links to: RB