hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phabricator (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-2870) Throw an error when a nonexistent partition is accessed in strict mode
Date Thu, 15 Mar 2012 18:15:40 GMT

    [ https://issues.apache.org/jira/browse/HIVE-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230383#comment-13230383
] 

Phabricator commented on HIVE-2870:
-----------------------------------

akramer has requested changes to the revision "HIVE-2870 [jira] Throw an error when a nonexistent
partition is accessed in strict mode".

  > I checked the error message list and I see other errors advertise the nonstrict mode
in case the user really wants to run the operation. I'll change the message.

  Thanks. It is always better to do something right than wrong. Consistency only matter when
there are multiple "right" things to do or no "right" thing to do.

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
>
>   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

        

Mime
View raw message