[
https://issues.apache.org/jira/browse/CALCITE-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16407776#comment-16407776
]
Eyal Segal commented on CALCITE-2211:
-------------------------------------
The <BIGINT> to the left is actually a "bigint(11)" column. The <OTHR> is the
"bigint(20) unsigned" that we're discussing.
Based on your CSV adapter, we didn't want to interfere with the type resolving.
So JDBC resolves to BigInteger, and the type factory fails to resolve that to
BIGINT.
In anyway our workaround was indeed to interfere with the resolving process, so
when the code sees BigInteger we cast it to Long.
> Type of BigInteger should be BIGINT
> -----------------------------------
>
> Key: CALCITE-2211
> URL: https://issues.apache.org/jira/browse/CALCITE-2211
> Project: Calcite
> Issue Type: Bug
> Affects Versions: 1.15.0
> Reporter: Eyal Segal
> Assignee: Julian Hyde
> Priority: Major
>
> Vertica DB returns BigInteger values as BigInteger. It seems thatÂ
> JavaToSqlTypeConversionRules doesn't support mapping between BigInteger to
> BIGINT.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
