phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-5132) View indexes with different owners but of the same base table can be assigned same ViewIndexId
Date Tue, 09 Apr 2019 23:19:00 GMT


Hudson commented on PHOENIX-5132:

FAILURE: Integrated in Jenkins build Phoenix-4.x-HBase-1.4 #118 (See [])
PHOENIX-5138 - ViewIndexId sequences created after PHOENIX-5132 (gjacoby: rev 0e8322d21d66a918d34d622a4914eb5a0d3e058b)
* (edit) phoenix-core/src/it/java/org/apache/phoenix/end2end/
* (edit) phoenix-core/src/main/java/org/apache/phoenix/util/
* (edit) phoenix-core/src/main/java/org/apache/phoenix/coprocessor/
* (edit) phoenix-core/src/main/java/org/apache/phoenix/query/
* (edit) phoenix-core/src/main/java/org/apache/phoenix/util/
* (edit) phoenix-core/src/it/java/org/apache/phoenix/end2end/index/

> View indexes with different owners but of the same base table can be assigned same ViewIndexId
> ----------------------------------------------------------------------------------------------
>                 Key: PHOENIX-5132
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 5.0.0, 4.14.1
>            Reporter: Geoffrey Jacoby
>            Assignee: Geoffrey Jacoby
>            Priority: Critical
>             Fix For: 4.15.0, 5.1
>         Attachments: PHOENIX-5132-4.x-HBase-1.4.patch, PHOENIX-5132-4.x-HBase-1.4.v2.patch,
> All indexes on views for a particular base table are stored in the same physical HBase
table. Phoenix distinguishes them by prepending each row key with an encoded short or long
integer called a ViewIndexId. 
> The ViewIndexId is generated by using a sequence to guarantee that each view index id
is unique. Unfortunately, the sequence used follows a convention of [SaltByte, Tenant, Schema,
BaseTable] for its key, which means that there's a separate sequence for each tenant that
owns an index in the view index table. (See MetaDataUtil.getViewIndexSequenceKey) Since all
the sequences start at the same value, collisions are not only possible but likely. 
> I've written a test that confirms the ViewIndexId collision. This means it's very likely
that query results using one view index could mistakenly include rows from another index,
but I haven't confirmed this. 
> All view indexes for a base table, regardless of whether globally or tenant-owned, should
use the same sequence. 

This message was sent by Atlassian JIRA

View raw message