[CALCITE-3029] Java-oriented field type is wrongly forced to be NOT NULL after being converted to SQL-oriented - ASF JIRA

Voters

Watch issue

Watchers

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Bug
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: 1.19.0
Fix Version/s: 1.20.0
Component/s: None
Labels:
- pull-request-available

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).

Attachments

Issue Links

Add Link

links to

GitHub Pull Request #1187

Delete this link

Activity

Comment

This comment will be Viewable by All Users Viewable by All Users

Cancel

People

Assignee:: Hongze Zhang

Reporter:: Hongze Zhang

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: 28/Apr/19 10:19

Updated:: 24/Jun/19 15:02

Resolved:: 30/Apr/19 08:25

Time Tracking

Estimated:

Not Specified

Remaining:

Logged:

Java-oriented field type is wrongly forced to be NOT NULL after being converted to SQL-oriented