[
https://issues.apache.org/jira/browse/FLINK-19419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17202623#comment-17202623
]
Jark Wu commented on FLINK-19419:
---------------------------------
This has been explained in the docs:
https://ci.apache.org/projects/flink/flink-docs-release-1.11/dev/table/connectors/hbase.html#null-string-literal
The value of {{null-string-literal}} is a representation of null values, that
means encode null values to {{null-string-literal}} string when writing data
into HBase. HBase source and sink encodes/decodes empty bytes as null values by
default. But this doesn't work for string type, because empty byte is also a
valid value. That's why we have such configuration.
> "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)
