You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Caizhi Weng (Jira)" <ji...@apache.org> on 2021/09/10 10:58:00 UTC

[jira] [Updated] (FLINK-24251) Make default constructor of BinaryStringData construct empty binary string again

     [ https://issues.apache.org/jira/browse/FLINK-24251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Caizhi Weng updated FLINK-24251:
--------------------------------
    Summary: Make default constructor of BinaryStringData construct empty binary string again  (was: Make default constructor of BinaryStringData private)

> Make default constructor of BinaryStringData construct empty binary string again
> --------------------------------------------------------------------------------
>
>                 Key: FLINK-24251
>                 URL: https://issues.apache.org/jira/browse/FLINK-24251
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table SQL / Runtime
>            Reporter: Caizhi Weng
>            Priority: Minor
>
> In FLINK-23289 we add a not null checking for {{BinarySection}}. After the change the default constructor of {{BinaryStringData}} will now construct a {{BinaryStringData}} with {{null}} Java object and {{null}} {{BinarySection}}. This is different from the behavior before where the default constructor constructs an empty binary string.
> Although {{BinaryStringData}} is an internal class, it might confuse some developers (actually I myself have been confused) if they build their programs around this class. So we should make the default constructor construct an empty binary string again without breaking the not null checking.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)