phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
Date Mon, 10 Jun 2019 18:00:00 GMT


Hadoop QA commented on PHOENIX-5156:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against 4.x-HBase-1.4 branch at commit 0e60a901a0615354c3ca021e395959aa530f6e06.
  ATTACHMENT ID: 12971359

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 3 new or modified

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output:

This message is automatically generated.

> 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.4.x-HBase-1.4.003.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, PHOENIX-5156.master.019.patch, PHOENIX-5156.master.020.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