[
https://issues.apache.org/jira/browse/HIVE-12727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068841#comment-15068841
]
Ashutosh Chauhan commented on HIVE-12727:
-----------------------------------------
If TPCDS query set is your benchmark then I think you will get failure even
with SEMI strict because of cartesian product. You probably want to allow even
those as it can be argued they are also *valid* queries. Even for comparison
queries they can be argued to consider *valid*. It seems to me that we should
just revert default to nonstrict.
Fact that there is a flag means that different settings exists for different
use cases. My thinking for changing default to strict was assumption that we
want Hive to be geared for production use cases and not for
pocs/benchmarks/ease-of-use. Assumption is before deploying to production,
user will first test their queries and then during that testing throwing
exception will force user to reconsider queries they are writing and force them
to make a conscious choice to set flag to false if they think they still want
it. Assumption was you want flag to be strict *always* in production and have
set to nonstrict selectively for limited query set where you absolutely want
other way. Since, no one thinks the way I am : ), I guess we should just set
flag to non-strict, instead of adding level of strictness.
Also, consider renaming config variable to hive.exec.mode (or some such) Having
mapred in the name is going to be confusing to user as they may think this is
not applicable to tez/spark/llap which isnt the case.
> allow full table queries in strict mode
> ---------------------------------------
>
> 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
> Attachments: 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)
