[
https://issues.apache.org/jira/browse/HBASE-24409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17114261#comment-17114261
]
Andrew Kyle Purtell commented on HBASE-24409:
---------------------------------------------
Comments from the PR
{quote}
Why not do this at the target cluster?
And you are also free to implement your own ReplicationEndpoint, where you
could change the table name when generating the protobuf message.
We have already introduced addExtendedAttribute method in WALKey interface for
bringing customized data, so I'm -1 on introducing a setTableName method, it is
confusing to users.
{quote}
Will these alternatives suffice?
Given the veto on the PR, unless there is a strong technical justification to
override, we can close this.
> Expose a function in HBase WALKey to set the tablename
> ------------------------------------------------------
>
> Key: HBASE-24409
> URL: https://issues.apache.org/jira/browse/HBASE-24409
> Project: HBase
> Issue Type: Improvement
> Reporter: Sandeep Pal
> Assignee: Sandeep Pal
> Priority: Major
>
> Currently, table name in WALKey can not be changed once set. But exposing
> this function to change the table name can be very helpful for Customized WAL
> filters since they can flip the table name and make replication possible
> between different table names in source and sink clusters.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
