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

Posted to issues@ignite.apache.org by "Yury Gerzhedovich (Jira)" <ji...@apache.org> on 2021/03/22 11:52:00 UTC

[jira] [Created] (IGNITE-14374) Optimize SQL inline indexes format for Ignite 3.0

Yury Gerzhedovich created IGNITE-14374:
------------------------------------------

             Summary: Optimize SQL inline indexes format for Ignite 3.0
                 Key: IGNITE-14374
                 URL: https://issues.apache.org/jira/browse/IGNITE-14374
             Project: Ignite
          Issue Type: Improvement
          Components: sql
            Reporter: Yury Gerzhedovich


As of now, we always use 1 extra byte per column to keep type. It adds significant effort to index size. We should rethink the format of store for Ignite 3.0.
At first glance, it could be a separate single byte to keep the null value for nullable types. In this case, we could inline not more than 8 columns that see as reasonable. May be index record format should be the same as we use for the data records.




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