[PHOENIX-6267] View Index PK Fixed Width Field Truncation

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 5.0.0, 4.15.0, 4.14.3
• Fix Version/s: 5.1.0, 4.16.0
• Assignee: Gokcen Iskender
• Reporter: Geoffrey Jacoby
• Created: 16/Dec/20 21:58
• Updated: 04/Jan/21 17:57
• Resolved: 22/Dec/20 21:44

Description

1. Create a table T
2. Create a view V that extends the PK of T, where the last field of the view's PK is a fixed width column C such as an INTEGER or BIGINT
3. Create a view index VI on V that does NOT contain C in its index key
4. Select C from the view with a query that runs against the view index

You will get the following error:

 java.sql.SQLException: ERROR 201 (22000): Illegal data. Expected length of at least 8 bytes, but had 7

giskender, kadir, tkhurana and I investigated. It appears the problem comes from
IndexMaintainer.buildRowKey:707-713

            int length = stream.size();
            int minLength = length - maxTrailingNulls;
            byte[] indexRowKey = stream.getBuffer();
            // Remove trailing nulls
            while (length > minLength && indexRowKey[length-1] == QueryConstants.SEPARATOR_BYTE) {
                length--;
            }

The logic to remove trailing separator bytes shouldn't run if the end of the index key (i.e the end of the base PK) is a fixed width column. Otherwise, we'll truncate whenever the last byte of the fixed width field happens to be \x00

 

This only happens for view indexes (mutitenant or not)

Issue Links

• Blocked: PHOENIX-6266 When reading from view index, ERROR 201 (22000): Illegal data. Expected length of at least 8 bytes, but had 7
• links to: GitHub Pull Request #1021