[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

["Lefty Leverenz (JIRA)" <ji...@apache.org>]

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

Lefty Leverenz edited comment on HIVE-12727 at 12/12/17 3:41 AM:
-----------------------------------------------------------------

HIVE-15148 changes the description of *hive.strict.checks.cartesian.product* in release 2.2.0.

Edit 11/Dec/17:  HIVE-18251 changes the default value of *hive.strict.checks.cartesian.product* to false in release 3.0.0.


was (Author: lefty@hortonworks.com):
HIVE-15148 changes the description of *hive.strict.checks.cartesian.product* in release 2.2.0.

> 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)