[
https://issues.apache.org/jira/browse/HIVE-12727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201086#comment-16201086
]
Sergey Shelukhin commented on HIVE-12727:
-----------------------------------------
The legacy mode is actually more restrictive than the new mode. The cartesian
product check used to be true in the strict mode (the default), and false, with
all the other checks, in nonstrict.
The new configs only apply in new versions; if you set hive.mapred.mode to null
on older versions, it assumes the default value of "strict", applying all the
checks.
Otherwise please describe the scenario (the old value, old version of Hive, new
version of Hive, and what changes were made to this setting) that you are
encountering, afaik it should have no upgrade ases where it changes the
behavior in a manner that breaks the previous user-specific setting, or makes
the checks more restrictive if the setting was not set.
> 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.4.14#64029)
