[jira] [Commented] (PHOENIX-6083) View index creation does a checkAndPut on an incorrect row key

["Chinmay Kulkarni (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PHOENIX-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17179994#comment-17179994 ] 

Chinmay Kulkarni commented on PHOENIX-6083:
-------------------------------------------

We should fix this before releasing 4.16 [~yanxinyi] [~jisaac]. FYI [~tdsilva]

> View index creation does a checkAndPut on an incorrect row key
> --------------------------------------------------------------
>
>                 Key: PHOENIX-6083
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6083
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 5.0.0, 4.15.0
>            Reporter: Chinmay Kulkarni
>            Priority: Critical
>              Labels: phoenix-hardening, quality-improvement
>             Fix For: 5.1.0, 4.16.0
>
>         Attachments: image-2020-08-18-11-09-35-080.png, image-2020-08-18-11-09-53-816.png
>
>
> When creating a view index, we "lock" on the indexed and included columns by doing a checkAndPut on the cell: 
> (<physical parent's schema name>, <physical parent's table name>, <name of the indexed/included column>)
> This is done to prevent another client from concurrently dropping any of the indexed/included columns. This however, is not working as expected since the indexed column naming convention is different (<column family>:<column name>) rather than just <column name>. 
> Thus, concurrent dropping of the column is not prevented and this leads to failure in view index creation with either an NPE or IllegalArgumentException.
> !image-2020-08-18-11-09-35-080.png!
> !image-2020-08-18-11-09-53-816.png!
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)