Mailing-List: contact issues-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Wed, 11 Oct 2017 14:53:00 +0000 (UTC)
From: "Wang Haihua (JIRA)" <jira@apache.org>
To: issues@hive.apache.org
Message-ID: <JIRA.12923650.1450754163000.28686.1507733580617@Atlassian.JIRA>
In-Reply-To: <JIRA.12923650.1450754163000@Atlassian.JIRA>
References: <JIRA.12923650.1450754163000@Atlassian.JIRA> <JIRA.12923650.1450754163769@jira-lw-us.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
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 11 Oct 2017 14:53:06 -0000


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

Wang Haihua edited comment on HIVE-12727 at 10/11/17 2:52 PM:
--------------------------------------------------------------

Hi [~xuefuz] [~sershe], 

should we follow the meaning of legacy default nonstrict value of {{hive.mapred.mode}}, which means that {{hive.strict.checks.cartesian.product }} should has default value of false?

I suppose this will be welcome to the legacy user for compatibility.

In my case, change {{hive.mapred.mode}} to null, will result in many SQL including cartesian product executed error.

Thanks!


was (Author: wanghaihua):
Hi, should we follow the meaning of legacy default nonstrict value of {{hive.mapred.mode}}, which means that {{hive.strict.checks.cartesian.product }} should has default value of false?

I suppose this will be welcome to the legacy user for compatibility.

In my case, change {{hive.mapred.mode}} to null, will result in many SQL including cartesian product executed error.

cc [~xuefuz] [~sershe]]


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