[
https://issues.apache.org/jira/browse/CALCITE-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16829015#comment-16829015
]
Hongze Zhang commented on CALCITE-3029:
---------------------------------------
Thanks [~rubenql] and [~zabetak]!
And the PR is currently just a patch for my personal use. Since I didn't dive
into the details of 2464, if there is any better solution you prefer to do or
be confident with, feel free to take the test cases and make your own changes.
:)
> Java-oriented field type is wrongly forced to be NOT NULL after being
> converted to SQL-oriented
> -----------------------------------------------------------------------------------------------
>
> Key: CALCITE-3029
> URL: https://issues.apache.org/jira/browse/CALCITE-3029
> Project: Calcite
> Issue Type: Bug
> Affects Versions: 1.19.0
> Reporter: Hongze Zhang
> Assignee: Hongze Zhang
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.20.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> A Java-oriented field type loses its nullable constraint after calling method
> {{org.apache.calcite.jdbc.JavaTypeFactoryImpl#toSql(org.apache.calcite.rel.type.RelDataType)}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
