phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chinmay Kulkarni (Jira)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-5435) Annotate HBase WALs with Phoenix Metadata
Date Wed, 16 Dec 2020 19:17:00 GMT

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

Chinmay Kulkarni updated PHOENIX-5435:
--------------------------------------
    Fix Version/s: 4.16.0
                   5.1.0

> Annotate HBase WALs with Phoenix Metadata
> -----------------------------------------
>
>                 Key: PHOENIX-5435
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5435
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Geoffrey Jacoby
>            Assignee: Geoffrey Jacoby
>            Priority: Major
>             Fix For: 5.1.0, 4.16.0
>
>         Attachments: PHOENIX-5435-4.x.patch
>
>
> HBase write-ahead-logs (WALs) drive not only failure recovery, but HBase replication
and some HBase backup frameworks. The WALs contain HBase-level metadata such as table and
region, but lack Phoenix-level metadata. That means that it's quite difficult to build correct
logic that needs to know about Phoenix-level constructs such as multi-tenancy, views, or indexes.

> HBASE-22622 and HBASE-22623 add the capacity for coprocessors to annotate extra key/value
pairs of metadata into the HBase WAL. We should have the option to annotate the tuple <tenant_id,
table-or-view-name, timestamp>, or some hashed way to reconstruct that tuple into the WAL.
It should have a feature toggle so operators who don't need it don't bear the slight extra
storage cost. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message