[
https://issues.apache.org/jira/browse/HIVE-20095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16542339#comment-16542339
]
Jesus Camacho Rodriguez commented on HIVE-20095:
------------------------------------------------
[~daijy], the motivation for that is that currently we can generate complex SQL
statement for the part of the query that we push to the storage handler
automatically from Calcite. Hence, the types for that TableScan should be
coming from the output of that query rather than from the Table schema. I think
an easy fix would be that if query has been generated by Hive, then we could
use ResultSet to determine the schema; otherwise we fallback to using table
schema, which is what [~msydoron] did.
Since the number of dialects supported from Calcite will be limited, this means
we should also include a map for the types in those databases towards Hive. We
can do that later on. Does it make sense?
[~msydoron], there seem to be be some test failures still.
> Fix jdbc external table feature
> -------------------------------
>
> Key: HIVE-20095
> URL: https://issues.apache.org/jira/browse/HIVE-20095
> Project: Hive
> Issue Type: Bug
> Reporter: Jonathan Doron
> Assignee: Jonathan Doron
> Priority: Major
> Attachments: HIVE-20095.1.patch, HIVE-20095.2.patch,
> HIVE-20095.3.patch
>
>
> It seems like the committed code for HIVE-19161
> (7584b3276bebf64aa006eaa162c0a6264d8fcb56) reverted some of HIVE-18423
> updates, and therefore some of the external table queries are not working
> correctly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
