phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ankit Singhal (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-4546) Projected table cannot be read through ProjectedColumnExpression
Date Wed, 07 Feb 2018 10:49:00 GMT


Ankit Singhal commented on PHOENIX-4546:

{quote}Is this an issue for 4.x too? 
 yes, this is an issue with 4.x too
{quote}Is it specific to local indexes?
No, it is not specific to local indexes, this is observed when deleting data from an Immutable
table having multiple immutable indexes.

During delete, maintenance of immutable indexes at client executes a select query by adding
all columns involved in all immutable indexes and projected table is created out of it, KeyValue
schema will be built considering the order of columns in projected table but TupleProjectorCompiler
doesn't maintain the order as per the SELECT projection, result in wrong ProjectedColumnExpression
used in IndexMaintainers to read the value of the columns. 

This is observed in this case only because others use RowProjector which take care of indexes
of the columns correctly and use the right ProjectedColumnExpression.


> Projected table cannot be read through ProjectedColumnExpression
> ----------------------------------------------------------------
>                 Key: PHOENIX-4546
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Romil Choksi
>            Assignee: Ankit Singhal
>            Priority: Major
>             Fix For: 5.0.0, 4.14.0
>         Attachments: PHOENIX-4546.patch, PHOENIX-4546_v1.patch, PHOENIX-4546_v2.patch,

This message was sent by Atlassian JIRA

View raw message