[
https://issues.apache.org/jira/browse/FLINK-25330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17460396#comment-17460396
]
Wenlong Lyu commented on FLINK-25330:
-------------------------------------
hi, [~Bruce Wong] I have a concern on deleting all of the version when receive
a retract message.
IMO, users who uses HBase in production track changes by enabling
multi-version, so it maybe not actually needed by users to delete all of the
version when receiving a retract message, instead, they may want to translate
the retract message to a flag column such as is_deleted or set all columns to
be empty. WDYT?
> Flink SQL doesn't retract all versions of Hbase data
> ----------------------------------------------------
>
> Key: FLINK-25330
> URL: https://issues.apache.org/jira/browse/FLINK-25330
> Project: Flink
> Issue Type: Bug
> Components: Connectors / HBase
> Affects Versions: 1.14.0
> Reporter: Bruce Wong
> Priority: Critical
> Labels: pull-request-available
> Attachments: image-2021-12-15-20-05-18-236.png
>
>
> h2. Background
> When we use CDC to synchronize mysql data to HBase, we find that HBase
> deletes only the last version of the specified rowkey when deleting mysql
> data. The data of the old version still exists. You end up using the wrong
> data. And I think its a bug of HBase connector.
> The following figure shows Hbase data changes before and after mysql data is
> deleted.
> !image-2021-12-15-20-05-18-236.png|width=910,height=669!
>
> h2.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
