[jira] [Updated] (FLINK-5177) Improve nullability handling
[ https://issues.apache.org/jira/browse/FLINK-5177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-5177: -- Labels: auto-deprioritized-major auto-deprioritized-minor auto-unassigned (was: auto-deprioritized-major auto-unassigned stale-minor) Priority: Not a Priority (was: Minor) This issue was labeled "stale-minor" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Minor, please raise the priority and ask a committer to assign you the issue or revive the public discussion. > Improve nullability handling > - > > Key: FLINK-5177 > URL: https://issues.apache.org/jira/browse/FLINK-5177 > Project: Flink > Issue Type: Improvement > Components: Table SQL / API >Reporter: Timo Walther >Priority: Not a Priority > Labels: auto-deprioritized-major, auto-deprioritized-minor, > auto-unassigned > > Currently, all fields of the Table API are marked as nullable by default. A > lot of null checking could be avoided if we would properly handle > nullability. Fields of tuples and POJOs with primitive fields can not be > null. Elements of primitive arrays too. It also includes parameters and > return types of user-defined scalar, table, and aggregate functions. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (FLINK-5177) Improve nullability handling
[ https://issues.apache.org/jira/browse/FLINK-5177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-5177: -- Labels: auto-deprioritized-major auto-unassigned stale-minor (was: auto-deprioritized-major auto-unassigned) I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > Improve nullability handling > - > > Key: FLINK-5177 > URL: https://issues.apache.org/jira/browse/FLINK-5177 > Project: Flink > Issue Type: Improvement > Components: Table SQL / API >Reporter: Timo Walther >Priority: Minor > Labels: auto-deprioritized-major, auto-unassigned, stale-minor > > Currently, all fields of the Table API are marked as nullable by default. A > lot of null checking could be avoided if we would properly handle > nullability. Fields of tuples and POJOs with primitive fields can not be > null. Elements of primitive arrays too. It also includes parameters and > return types of user-defined scalar, table, and aggregate functions. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (FLINK-5177) Improve nullability handling
[ https://issues.apache.org/jira/browse/FLINK-5177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-5177: -- Labels: auto-deprioritized-major auto-unassigned (was: auto-unassigned stale-major) Priority: Minor (was: Major) This issue was labeled "stale-major" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Major, please raise the priority and ask a committer to assign you the issue or revive the public discussion. > Improve nullability handling > - > > Key: FLINK-5177 > URL: https://issues.apache.org/jira/browse/FLINK-5177 > Project: Flink > Issue Type: Improvement > Components: Table SQL / API >Reporter: Timo Walther >Priority: Minor > Labels: auto-deprioritized-major, auto-unassigned > > Currently, all fields of the Table API are marked as nullable by default. A > lot of null checking could be avoided if we would properly handle > nullability. Fields of tuples and POJOs with primitive fields can not be > null. Elements of primitive arrays too. It also includes parameters and > return types of user-defined scalar, table, and aggregate functions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-5177) Improve nullability handling
[ https://issues.apache.org/jira/browse/FLINK-5177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-5177: -- Labels: auto-unassigned stale-major (was: auto-unassigned) I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 30 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > Improve nullability handling > - > > Key: FLINK-5177 > URL: https://issues.apache.org/jira/browse/FLINK-5177 > Project: Flink > Issue Type: Improvement > Components: Table SQL / API >Reporter: Timo Walther >Priority: Major > Labels: auto-unassigned, stale-major > > Currently, all fields of the Table API are marked as nullable by default. A > lot of null checking could be avoided if we would properly handle > nullability. Fields of tuples and POJOs with primitive fields can not be > null. Elements of primitive arrays too. It also includes parameters and > return types of user-defined scalar, table, and aggregate functions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-5177) Improve nullability handling
[ https://issues.apache.org/jira/browse/FLINK-5177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-5177: -- Labels: auto-unassigned (was: stale-assigned) > Improve nullability handling > - > > Key: FLINK-5177 > URL: https://issues.apache.org/jira/browse/FLINK-5177 > Project: Flink > Issue Type: Improvement > Components: Table SQL / API >Reporter: Timo Walther >Assignee: Timo Walther >Priority: Major > Labels: auto-unassigned > > Currently, all fields of the Table API are marked as nullable by default. A > lot of null checking could be avoided if we would properly handle > nullability. Fields of tuples and POJOs with primitive fields can not be > null. Elements of primitive arrays too. It also includes parameters and > return types of user-defined scalar, table, and aggregate functions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-5177) Improve nullability handling
[ https://issues.apache.org/jira/browse/FLINK-5177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-5177: -- Labels: stale-assigned (was: ) > Improve nullability handling > - > > Key: FLINK-5177 > URL: https://issues.apache.org/jira/browse/FLINK-5177 > Project: Flink > Issue Type: Improvement > Components: Table SQL / API >Reporter: Timo Walther >Assignee: Timo Walther >Priority: Major > Labels: stale-assigned > > Currently, all fields of the Table API are marked as nullable by default. A > lot of null checking could be avoided if we would properly handle > nullability. Fields of tuples and POJOs with primitive fields can not be > null. Elements of primitive arrays too. It also includes parameters and > return types of user-defined scalar, table, and aggregate functions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-5177) Improve nullability handling
[ https://issues.apache.org/jira/browse/FLINK-5177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timo Walther updated FLINK-5177: Description: Currently, all fields of the Table API are marked as nullable by default. A lot of null checking could be avoided if we would properly handle nullability. Fields of tuples and POJOs with primitive fields can not be null. Elements of primitive arrays too. It also includes parameters and return types of user-defined scalar, table, and aggregate functions. (was: Currently, all fields of the Table API are marked as nullable by default. A lot of null checking could be avoided if we would properly handle nullability. Fields of tuples and POJOs with primitive fields can not be null. Elements of primitive arrays too. ) > Improve nullability handling > - > > Key: FLINK-5177 > URL: https://issues.apache.org/jira/browse/FLINK-5177 > Project: Flink > Issue Type: Improvement > Components: Table API & SQL >Reporter: Timo Walther > > Currently, all fields of the Table API are marked as nullable by default. A > lot of null checking could be avoided if we would properly handle > nullability. Fields of tuples and POJOs with primitive fields can not be > null. Elements of primitive arrays too. It also includes parameters and > return types of user-defined scalar, table, and aggregate functions. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
