[jira] [Updated] (IGNITE-17025) Remove the ability to manually set INLINE_SIZE for types with a fixed length

["Taras Ledkov (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-17025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Taras Ledkov updated IGNITE-17025:
----------------------------------
    Release Note: Improved adjustment inline size for fixed size index items.

> Remove the ability to manually set INLINE_SIZE for types with a fixed length
> ----------------------------------------------------------------------------
>
>                 Key: IGNITE-17025
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17025
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Luchnikov Alexander
>            Assignee: Nikolay Izhikov
>            Priority: Minor
>              Labels: ise
>             Fix For: 2.14
>
>         Attachments: InlineIndexTest1.patch
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The reproducer ( [^InlineIndexTest1.patch] ) shows index.bin size growing when INLINE_SIZE increases when creating indexes on fixed length fields.The negative point is that a place is reserved that does not carry any profit.
> As a solution. When trying to build an index on a field with a fixed length type, do not allow this. The value of INLINE_SIZE for such types is calculated automatically. And display a WARN level message about it.
> To see the size of index.bin, run the
> {code:java}
> du -sh IGNITE_HOME/db/node*/*INLINE*/* | grep index.bin" 
> {code}
> after running the reproducer.
> {code:java}
> 36K BIGINT_INLINE10/index.bin
> 320K BIGINT_INLINE100/index.bin
> 128K INT_INLINE10/index.bin
> 324K INT_INLINE100/index.bin
>  64K NUMBER_INLINE10/index.bin
>  64K NUMBER_INLINE100/index.bin
> 128K VARCHAR_INLINE10/index.bin
> 256K VARCHAR_INLINE100/index.bin
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)