hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Shelukhin (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HIVE-12727) refactor Hive strict checks to be more granular, allow order by no limit and no partition filter by default for now
Date Tue, 26 Jul 2016 01:17:20 GMT

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

Sergey Shelukhin edited comment on HIVE-12727 at 7/26/16 1:17 AM:
------------------------------------------------------------------

Yeah, that was the intent... maintaining backward compat for mapred mode. The new configs
are used only when mapred.mode is not set (hence getting it with the null-default).


was (Author: sershe):
Yeah, that was the intent... maintaining backward compat for strict mode.

> refactor Hive strict checks to be more granular, allow order by no limit and no partition
filter by default for now
> -------------------------------------------------------------------------------------------------------------------
>
>                 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
>              Labels: TODOC2.0
>             Fix For: 2.0.0
>
>         Attachments: HIVE-12727.01.patch, HIVE-12727.02.patch, HIVE-12727.03.patch, HIVE-12727.04.patch,
HIVE-12727.05.patch, HIVE-12727.06.patch, HIVE-12727.07.patch, 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