[
https://issues.apache.org/jira/browse/HBASE-22622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16871912#comment-16871912
]
Duo Zhang commented on HBASE-22622:
-----------------------------------
This does not make sense I'd say. Is a Phoenix view a table in HBase? Then how
do you make sure that the region for this table which you want to modify is on
the same region server?
> WALKey Extended Attributes
> --------------------------
>
> Key: HBASE-22622
> URL: https://issues.apache.org/jira/browse/HBASE-22622
> Project: HBase
> Issue Type: New Feature
> Components: wal
> Reporter: Geoffrey Jacoby
> Assignee: Geoffrey Jacoby
> Priority: Major
>
> It would be useful if the WAL protobuf and WALKey class included an optional
> map of extended key/value attributes. While standard HBase replication would
> not use them, custom replication endpoints could use the data to make
> filtering decisions or take actions.
> An example use case would be allowing a tool like Phoenix to annotate
> WAL.Entries to indicate that a given Entry is associated with a particular
> Phoenix view rather than the base table. A custom replication endpoint might
> choose to replicate some views but not others.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
