You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Maksim Timonin (Jira)" <ji...@apache.org> on 2021/10/05 09:12:00 UTC

[jira] [Updated] (IGNITE-15679) InlineIndex should store enum as int and not as POJO

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

Maksim Timonin updated IGNITE-15679:
------------------------------------
    Summary: InlineIndex should store enum as int and not as POJO  (was: Inline should store enum as int and not as POJO)

> InlineIndex should store enum as int and not as POJO
> ----------------------------------------------------
>
>                 Key: IGNITE-15679
>                 URL: https://issues.apache.org/jira/browse/IGNITE-15679
>             Project: Ignite
>          Issue Type: New Feature
>            Reporter: Maksim Timonin
>            Assignee: Maksim Timonin
>            Priority: Major
>
> Investigate opportunity for optimal storing enum in inlines for faster comparison.
> Currently enum stores as POJO, and equal elements compares with comparing BinaryObject arrays (also, it looks like the comparison doesn't use intrinsics).
> Looks like we can easily can store it as int using Enum.ordering(). 
>  
> BUT, H2 supports enum, but Ignite doesn't use it for some reason. Investigate why. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)