hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasanth Jayachandran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-12727) allow full table queries in strict mode
Date Wed, 23 Dec 2015 00:40:46 GMT

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

Prasanth Jayachandran commented on HIVE-12727:
----------------------------------------------

I agree that the default mode should be "strict" similar to dynamic partition as user should
be aware of what they are doing and either rewrite the query or set the config explicitly.
As hive 2.0 already breaks compatibility this is no different. Also +1 for removing "mapred"
from the config as it's not tied to MR.

> allow full table queries in strict mode
> ---------------------------------------
>
>                 Key: HIVE-12727
>                 URL: https://issues.apache.org/jira/browse/HIVE-12727
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>            Priority: Blocker
>         Attachments: HIVE-12727.patch
>
>
> Making strict mode the default recently appears to have broken many normal queries, such
as some TPCDS benchmark queries, e.g. Q85:
> Response message: org.apache.hive.service.cli.HiveSQLException: Error while compiling
statement: FAILED: SemanticException [Error 10041]: No partition predicate found for Alias
"web_sales" Table "web_returns"
> We should remove this restriction from strict mode, or change the default back to non-strict.
Perhaps make a 3-value parameter, nonstrict, semistrict, and strict, for backward compat for
people who are relying on strict already.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message