[
https://issues.apache.org/jira/browse/CALCITE-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406709#comment-16406709
]
Julian Hyde commented on CALCITE-2211:
--------------------------------------
As I'm sure you've figured out, it looks as if the main problem is the <OTHER>.
If you can change that to some numeric type -- by improving how the adapter
deduces types -- then the expression type inference (and implicit conversions
between numeric types) should just work.
I know you're fixing your own adapter, but I suspect that the changes you make
would also help the JDBC adapter. So, if your PR included a test for the JDBC
adapter that previously fails and now succeeds that would meet two objectives -
improve the JDBC adapter for everyone, and prevent regressions by proving
concretely that your fix solves the problem.
> 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)
