You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Bharath Vissapragada (Jira)" <ji...@apache.org> on 2021/01/25 16:39:00 UTC
[jira] [Resolved] (HBASE-25525) WALKey Extended Attributes don't
serialize to ReplicationSink
[ https://issues.apache.org/jira/browse/HBASE-25525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bharath Vissapragada resolved HBASE-25525.
------------------------------------------
Resolution: Fixed
Thanks [~gjacoby], looks like this is not needed in other branches, resolving.
> WALKey Extended Attributes don't serialize to ReplicationSink
> -------------------------------------------------------------
>
> Key: HBASE-25525
> URL: https://issues.apache.org/jira/browse/HBASE-25525
> Project: HBase
> Issue Type: Bug
> Components: Replication
> Affects Versions: 1.5.0, 1.6.0
> Reporter: Geoffrey Jacoby
> Assignee: Geoffrey Jacoby
> Priority: Major
> Fix For: 1.7.0
>
>
> HBASE-22622 introduced extended attributes on the WALKey object and protobuf, and HBASE-22623 created a coprocessor hook, preWALAppend, so that coprocessors can create and insert their own extended attributes.
> These attributes are readable on the source-side, such as in a custom ReplicationEndpoint. However, in branch-1 ReplicationProtbufUtil doesn't correctly populate the extended attributes on the WALKey protobuf. (In 2.1+, HBASE-20625 incidentally fixes this as part of a larger refactoring of WALCellCodec logic.)
> This means that a custom ReplicationSink can't read extended attributes on a WALKey.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)