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

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

lucian has commented on the revision "HIVE-2870 [jira] Throw an error when a 
nonexistent partition is accessed in strict mode".

  > ...is the clarification that this is a "strict mode" restriction 
automatically included in the error message?

  No, but neither is it if for other strict-only errors:

  hive> select * from tmp_table_with_partitions;
  FAILED: Error in semantic analysis: No partition predicate found for Alias 
"tmp_table_with_partitions" Table "tmp_table_with_partitions"


  hive> select count(*) from tmp_table_with_partitions where ds="asdf";
  FAILED: Error in semantic analysis: No valid partition left after pruning for 
Alias "tmp_table_with_partitions" Table "tmp_table_with_partitions"

  I can change it, but I wanted to be consistent with that other one I tested.

REVISION DETAIL
  https://reviews.facebook.net/D2319

                
> 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

        

Reply via email to