You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Stamatis Zampetakis (Jira)" <ji...@apache.org> on 2022/09/28 11:35:00 UTC

[jira] [Commented] (HIVE-8739) handle Derby and Oracle errors with joins and filters in Direct SQL in a invalid-DB-specific path

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

Stamatis Zampetakis commented on HIVE-8739:
-------------------------------------------

The choice to introduce a CASE WHEN statement with additional conditions in order to avoid pushing the CAST below the joins (problem described under DERBY-6358) is incomplete.

As it can be seen by DERBY-7132 and HIVE-25965 the problem still exists with and without these changes.

> handle Derby and Oracle errors with joins and filters in Direct SQL in a invalid-DB-specific path
> -------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-8739
>                 URL: https://issues.apache.org/jira/browse/HIVE-8739
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>            Priority: Major
>             Fix For: 1.0.0
>
>         Attachments: HIVE-8739.01.patch, HIVE-8739.02.patch, HIVE-8739.patch, HIVE-8739.patch
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)