[ https://issues.apache.org/jira/browse/HIVE-12727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124535#comment-15124535 ]
Lefty Leverenz commented on HIVE-12727: --------------------------------------- Doc note: This deprecates *hive.mapred.mode* in 2.0.0, changing its default value back to nonstrict after HIVE-12413 changed it to strict in the same release, and adds three new configuration parameters to replace *hive.mapred.mode* (*hive.strict.checks.large.query* with default false, *hive.strict.checks.type.safety* with default true, and *hive.strict.checks.cartesian.product* with default true), so I added a TODOC2.0 label. The parameter changes should be documented in the wiki here: * [Configuration Properties -- hive.mapred.mode | https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties#ConfigurationProperties-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, 2.1.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)