ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stanilovsky Evgeny (Jira)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-13732) Incorrect inline suggestion.
Date Thu, 19 Nov 2020 07:14:00 GMT
Stanilovsky Evgeny created IGNITE-13732:

             Summary: 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

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,
{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

View raw message