[
https://issues.apache.org/jira/browse/HIVE-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240090#comment-13240090
]
Phabricator commented on HIVE-2870:
-----------------------------------
kevinwilfong has requested changes to the revision "HIVE-2870 [jira] Throw an
error when a nonexistent partition is accessed in strict mode".
-1
Sorry to have to go back after accepting, but I spoke with Namit Jain
(another Hive committer) about this diff.
This diff has the potential to break queries which are otherwise working,
such as a union all where one of the partitions being unioned doesn't exist.
Particularly, if that partition is only sometimes generated and the query is
scripted.
To avoid this, could you change the exception to a warning which is printed
to the console. You could still use a variable which writes to the console in
strict mode, and logs to info in nonstrict mode, although it would be better to
create a new Hive configuration variable to do this, rather than reusing
HIVEMAPREDMODE which is used far too much.
REVISION DETAIL
https://reviews.facebook.net/D2319
BRANCH
HIVE-2870-dev-branch
> 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
>
> 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
