You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2014/12/17 18:27:14 UTC

[jira] [Commented] (HIVE-9074) add ability to force direct sql usage for perf reasons

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

Sergey Shelukhin commented on HIVE-9074:
----------------------------------------

[~ashutoshc] can you review? Thanks

> add ability to force direct sql usage for perf reasons
> ------------------------------------------------------
>
>                 Key: HIVE-9074
>                 URL: https://issues.apache.org/jira/browse/HIVE-9074
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Sergey Shelukhin
>         Attachments: HIVE-9074.patch
>
>
> Some people run direct SQL and hit failures (e.g. due to Oracle 1000-in-expressions stupidity, illegal cast "optimization" in Derby and Oracle, or some other Hive and DB bugs). Currently, it falls back to ORM for such cases, however that can have huge impact on perf, and some people would rather have it fail so they can see the problem.
> In addition to "off" and "on+fallback" modes, "on or fail" mode needs to be added. The default will remain the same.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)