You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Geoffrey Jacoby (JIRA)" <ji...@apache.org> on 2019/06/25 05:52:00 UTC
[jira] [Updated] (HBASE-22622) WALKey Extended Attributes

     [ https://issues.apache.org/jira/browse/HBASE-22622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Geoffrey Jacoby updated HBASE-22622:
------------------------------------
    Description: 
It would be useful if the WAL protobuf and WALKey class included an optional map of extended key/value attributes that downstream coprocessors could use to annotate WAL Entries. 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 Phoenix table. (Multiple logical views in Phoenix can map to the same physical HBase table.) A custom replication endpoint might choose to replicate some views but not others. 

  was:
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. 


> 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 that downstream coprocessors could use to annotate WAL Entries. 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 Phoenix table. (Multiple logical views in Phoenix can map to the same physical HBase 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)