phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kadir OZDEMIR (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-5156) Consistent Global Indexes for Non-Transactional Tables
Date Sun, 24 Feb 2019 00:30:00 GMT


Kadir OZDEMIR commented on PHOENIX-5156:

[~giacomotaylor], [~elserj], [~lhofhansl], [~vincentpoon], [~gjacoby], please see the design
doc at [|]. I
have discussed the solution described in the design doc with [] who has
suggested to create this JIRA. I have updated the design details section based on his feedback.

[~lhofhansl] and [~vincentpoon], I have discussed with you two proposals before on the same
issue and greatly benefitted from these discussions. The solution in this doc is a hybrid
of these proposals.  It turned out that this solution can be implemented quickly as far as
I can see.

If I do not have a hole in the design, this will greatly improve the correctness of global
indexes. It is a very short document and should not take much of your time. I am looking forward
to your feedback.

> Consistent Global Indexes for Non-Transactional Tables
> ------------------------------------------------------
>                 Key: PHOENIX-5156
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1
>            Reporter: Kadir OZDEMIR
>            Assignee: Kadir OZDEMIR
>            Priority: Major
> Without transactional tables, the global indexes can get easily out of sync with their
data tables in Phoenix. Transactional tables require a separate transaction manager, have
some restrictions and performance penalties. This issue is to have consistent global indexes
without the need for using transactional tables.

This message was sent by Atlassian JIRA

View raw message