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 Mutable Global Indexes for Non-Transactional Tables
Date Fri, 07 Jun 2019 20:03:00 GMT


Kadir OZDEMIR commented on PHOENIX-5156:

[~gjacoby], the patches (PHOENIX-5156.master.018.patch and PHOENIX-5156.4.x-HBase-1.4.002.patch)
are ready to merge.  PHOENIX-5156.4.x-HBase-1.4.002.patch also cleanly merges to 4.14-HBase-1.4.

> Consistent Mutable 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
>         Attachments: PHOENIX-5156.4.x-HBase-1.4.001.patch, PHOENIX-5156.4.x-HBase-1.4.002.patch,
PHOENIX-5156.master.001.patch, PHOENIX-5156.master.002.patch, PHOENIX-5156.master.003.patch,
PHOENIX-5156.master.004.patch, PHOENIX-5156.master.005.patch, PHOENIX-5156.master.006.patch,
PHOENIX-5156.master.007.patch, PHOENIX-5156.master.008.patch, PHOENIX-5156.master.009.patch,
PHOENIX-5156.master.010.patch, PHOENIX-5156.master.011.patch, PHOENIX-5156.master.012.patch,
PHOENIX-5156.master.013.patch, PHOENIX-5156.master.014.patch, PHOENIX-5156.master.015.patch,
PHOENIX-5156.master.016.patch, PHOENIX-5156.master.017.patch, PHOENIX-5156.master.018.patch
>          Time Spent: 31h
>  Remaining Estimate: 0h
> Without transactional tables, the mutable 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 mutable
global indexes without the need for using transactional tables.

This message was sent by Atlassian JIRA

View raw message