[
https://issues.apache.org/jira/browse/PHOENIX-6120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17273306#comment-17273306
]
Istvan Toth commented on PHOENIX-6120:
--------------------------------------
[~yanxinyi][~giskender] The original patch is present in 4.16.0, but the it
doesn't have the license fix addendum.
We probably don't want to release 4.16 with licensing issues.
> Change IndexMaintainer for SINGLE_CELL_ARRAY_WITH_OFFSETS indexes. Currently
> it assumes data and index table having the same storage and encoding format.
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-6120
> URL: https://issues.apache.org/jira/browse/PHOENIX-6120
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: Gokcen Iskender
> Priority: Major
> Fix For: 5.1.0, 4.16.0
>
> Attachments: PHOENIX-6120-addendum.4.x.001.patch,
> PHOENIX-6120.4.x.001.patch
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> This Jira is a followup Jira of PHOENIX-5923 where data and index might have
> different storage and encoding formats. IndexMaintainer and protobuf needs to
> change to handle this. Right now, index maintainer assumes both index and
> data tables have the same format. The protobuf needs to be changed so that
> IndexMaintainer knows about the data table storage and encoding formats
> Repro:
> # Create a table with ONE_CELL_PER_COLUMN storage format
> # 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)
