[
https://issues.apache.org/jira/browse/PHOENIX-5435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17250817#comment-17250817
]
Geoffrey Jacoby commented on PHOENIX-5435:
------------------------------------------
[~stoty] - yes, switching to default 1.5 was my intention. Been meaning to
bring up a discussion about this on the dev list, which I hope to do tomorrow,
to evaluate options.
The problem with defaulting to the lowest HBase version when doing test runs
(either locally or in Jenkins) is that there are now quite a few tests that
don't get exercised on earlier versions of HBase. (This is particularly true on
the master branch, where many secondary index tests no-op when run against
HBase 2.1 or 2.2.)
I made the switch as part of this JIRA because WAL annotations are only
supported in newer versions of branch-1 (1.5+ I think? and only 2.3 and up when
I port to master in the next few days), so the tests would never get executed
at default settings.
> 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)
