[
https://issues.apache.org/jira/browse/HIVE-12727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068990#comment-15068990
]
Sergey Shelukhin commented on HIVE-12727:
-----------------------------------------
TPCDS is supposed to be representative of normal analytical queries. Simple
join with a small fact table, or a dimension table, triggers this condition.
This seems like it will break half of all the queries users might have in
production. This is very bad user experience.
order by without limit is also pretty common, and it's the type of query that
the users would run ad-hoc a lot. So the first thing that users will see when
trying Hive would be an error message that doesn't make any sense from any
previous SQL experience.
These are very different from e.g. unsafe compares, which is something else
this mode disables.
I think we should document this setting and allow users to set it to strict
manually; you already have to explicitly specify the settings specific to
production setup (e.g. memory sizes, limits etc.) so why not also this one?
Maybe we can also emit a warning by default when the "semi-safe" things are
used.
> 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)
