[
https://issues.apache.org/jira/browse/HIVE-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phabricator updated HIVE-2870:
------------------------------
Attachment: HIVE-2870.D2319.5.patch
lucian updated the revision "HIVE-2870 [jira] Throw an error when a nonexistent
partition is accessed in strict mode".
Reviewers: JIRA, njain, kevinwilfong, akramer
add new confvar, throw exception or log message
REVISION DETAIL
https://reviews.facebook.net/D2319
AFFECTED FILES
common/src/java/org/apache/hadoop/hive/conf/HiveConf.java
ql/src/java/org/apache/hadoop/hive/ql/optimizer/ppr/PartitionPruner.java
ql/src/java/org/apache/hadoop/hive/ql/parse/DDLSemanticAnalyzer.java
ql/src/java/org/apache/hadoop/hive/ql/parse/ErrorMsg.java
ql/src/test/queries/clientnegative/nopart_after_pruning.q
ql/src/test/queries/clientpositive/nopart_after_pruning.q
ql/src/test/results/clientnegative/nopart_after_pruning.q.out
ql/src/test/results/clientpositive/nopart_after_pruning.q.out
> Throw an error when a nonexistent partition is accessed in strict mode
> ----------------------------------------------------------------------
>
> Key: HIVE-2870
> URL: https://issues.apache.org/jira/browse/HIVE-2870
> Project: Hive
> Issue Type: Improvement
> Components: Query Processor
> Reporter: Lucian Adrian Grijincu
> Priority: Minor
> Attachments: HIVE-2870.D2319.1.patch, HIVE-2870.D2319.2.patch,
> HIVE-2870.D2319.3.patch, HIVE-2870.D2319.4.patch, HIVE-2870.D2319.5.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> When a table does not exist and someone tries to read from it in a query,
> Hive throws an error.
> But if a partition is directly accessed that does not exist, an error is not
> thrown. This is inconsistent and also leads to a lot of confused users who
> get no output.
> This task is to cause Hive to throw an error when the partition pruner for a
> query eliminates ALL existing partitions for some table when running in
> strict mode.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
