[ 
https://issues.apache.org/jira/browse/FLINK-19419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17202733#comment-17202733
 ] 

CaoZhen edited comment on FLINK-19419 at 9/28/20, 6:48 AM:
-----------------------------------------------------------

But this doesn't work for string type, because empty byte is also a valid 
value. 

-------

I think that if this is the case, then the "null" string read from Hbase should 
return the "null" string downstream instead of Java null


was (Author: caozhen1937):
But this doesn't work for string type, because empty byte is also a valid 
value. 

-------

I think that if this is the case, then the "null" string read from Hbase should 
return the "NULL" string downstream instead of Java NULL

> "null-string-literal" does not work  in HBaseSource decoder 
> ------------------------------------------------------------
>
>                 Key: FLINK-19419
>                 URL: https://issues.apache.org/jira/browse/FLINK-19419
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / HBase
>    Affects Versions: 1.11.0, 1.11.1, 1.11.2
>            Reporter: CaoZhen
>            Priority: Minor
>              Labels: pull-request-available
>         Attachments: image-2020-09-25-21-11-36-418.png
>
>
>  
> When using HBaseSoucre, it is found that "null-string-literal" does not work.
> The current decoder processing logic is shown below.
> `nullStringBytes` should be used when the `value` is null.
>  
> !image-2020-09-25-21-11-36-418.png!



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

Reply via email to