[
https://issues.apache.org/jira/browse/HIVE-12727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201523#comment-16201523
]
Wang Haihua commented on HIVE-12727:
------------------------------------
thanks for your reply [~sershe].
Our version is 2.1.1 (i suppose what happened is same with 2.0.0)
{{hive.mapred.mode}}(A) default value is "nonstrict" (i just noticed default
value become "strict" and return to "nonstrict" again in 2.0.0), so means
cartesian product is {{enabled}}.
This week i want to use three new configuration to control more accurately (In
my case, i just wanna forbidden query without specifying partitions. Query with
cartesian product should perform as usual), so just apply this path HIVE-14346
which set default value of {{hive.mapred.mode}} to "null", and set
{{hive.strict.checks.large.query}} to true in hive-site.xml.
But Incident occurred, because many queries with cartesian product failed
also. The reason is i had not noticed default value of
{{hive.strict.checks.cartesian.product}} is true...
So i suppose for smooth upgrade, should we consider default value of
{{hive.strict.checks.cartesian.product}}, {{hive.strict.checks.large.query}}
and other related configuration item have same semantic with legacy item
{{hive.mapred.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.4.14#64029)
