You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Hongze Zhang (JIRA)" <ji...@apache.org> on 2019/04/28 10:27:00 UTC
[jira] [Updated] (CALCITE-3029) Java-oriented field type is wrongly
forced to be NOT NULL after being converted to SQL-oriented
[ https://issues.apache.org/jira/browse/CALCITE-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hongze Zhang updated CALCITE-3029:
----------------------------------
Description: A Java-oriented field type loses its nullable constraint after calling method {{org.apache.calcite.jdbc.JavaTypeFactoryImpl#toSql(org.apache.calcite.rel.type.RelDataType)}}. (was: A Java-oriented field type loses its nullable constraint after calling method {{org.apache.calcite.jdbc.JavaTypeFactoryImpl#toSql(org.apache.calcite.rel.type.RelDataType)}}.
It seems that this issue is introduced by CALCITE-2464 fix.)
> 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
> Priority: Major
> Fix For: 1.20.0
>
>
> 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)