[
https://issues.apache.org/jira/browse/PHOENIX-6120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17196577#comment-17196577
]
Lars Hofhansl commented on PHOENIX-6120:
----------------------------------------
[~giskender] and I discussed this today.
The tests don't apply since this is scenario that cannot occur without
PHOENIX-5923 (namely the main table and the index being stored in a different
format.)
We also discussed the detection logic (using immutableRows) to detect when the
index encoding was changes (since there are no main table that are mutable
*and* use SINGLE_CELL encoding is clever, but is not future proof. Instead it's
better to add the main table's encoding the protobufs for IndexMaintainer and
assume the formats are the same when that encoding is absent.
In also cases old clients would fail with indexes created that way.
> Covered columns of indexes that have SINGLE_CELL_ARRAY_WITH_OFFSETS storage
> doesn't handle those columns
> --------------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-6120
> URL: https://issues.apache.org/jira/browse/PHOENIX-6120
> Project: Phoenix
> Issue Type: Bug
> Reporter: Gokcen Iskender
> Priority: Major
> Attachments: PHOENIX-6120.master.001.patch,
> PHOENIX-6120.master.002.patch
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Repro:
> # Create an index that has covered columns and the IMMUTABLE_STORAGE_SCHEME
> is SINGLE_CELL_ARRAY_WITH_OFFSETS
> # Upsert rows to data table
> # Query the covered column using index --> Null value is returned even
> though there is a value.
> IndexMaintainer has a 4 year old code that doesn't return a value for covered
> columns,
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
