[IGNITE-13732] Incorrect inline suggestion.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.9
• Component/s: sql
• Release Note: current implementation seems correct, _pk size additionally used while we have a deal with insert operations.
• Assignee: Evgeny Stanilovsky
• Reporter: Evgeny Stanilovsky
• Created: 19/Nov/20 07:13
• Updated: 19/Nov/20 15:17
• Resolved: 19/Nov/20 15:17

Description

I found that inline size suggestions are incorrect, check for example :

Indexed columns of a row cannot be fully inlined into index what may lead to slowdown due to additional data page reads, increase index inline size if needed (use INLINE_SIZE option for CREATE INDEX command, QuerySqlField.inlineSize for annotated classes, or QueryIndex.inlineSize for explicit QueryEntity configuration) [cacheName=myCache, tableName=myTable, idxName=SOME_IDX_NAME, idxCols=[PAYMENTDATE, STATUS, _KEY], idxTypes=[0, 13, 19], curSize=10, idxType=SECONDARY, recommendedInlineSize=96]

but why ? If PAYMENTDATE - long and STATUS is boolean, i believe it need to be calculated like:
5 bytes for BO header + 8 (long) + 4? (boolean) = 17, and i don`t understand why "_KEY" presented here, no need to append inner field size here.