[
https://issues.apache.org/jira/browse/PHOENIX-5435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17241944#comment-17241944
]
ASF GitHub Bot commented on PHOENIX-5435:
-----------------------------------------
gjacoby126 commented on pull request #913:
URL: https://github.com/apache/phoenix/pull/913#issuecomment-736887345
In this latest revision:
1. I added a new boolean flag, CHANGE_DETECTION_ENABLED to System.Catalog
which is configured via property on table or view creation. It can be changed
via ALTER. Adding it to an index will fail. Only tables and views with this
flag set to true (it defaults false) will have their changes annotated into the
WAL. Future JIRAs (such as PHOENIX-6227, and the main CDC code which will go in
phoenix-connectors) will also use this flag.
2. Indexes are no longer annotated.
3. Shifted WALAnnotationIT to use the SchemaBuilder API introduced with
Phoenix TTL
I believe the one remaining request left to do is @kadirozde 's suggestion
to do a perf test. I will do this over the next couple of days.
@ChinmaySKulkarni , @kadirozde , fyi.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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
> 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)
