[
https://issues.apache.org/jira/browse/IGNITE-13732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stanilovsky Evgeny resolved IGNITE-13732.
-----------------------------------------
Release Note: current implementation seems correct, _pk size additionally
used while we have a deal with insert operations.
Resolution: Won't Fix
> Incorrect inline suggestion.
> ----------------------------
>
> Key: IGNITE-13732
> URL: https://issues.apache.org/jira/browse/IGNITE-13732
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Affects Versions: 2.9
> Reporter: Stanilovsky Evgeny
> Assignee: Stanilovsky Evgeny
> Priority: Major
>
> I found that inline size suggestions are incorrect, check for example :
> {noformat}
> 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]
> {noformat} 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
