Mujtaba Chohan created PHOENIX-3559:
---------------------------------------

             Summary: More disk space used with encoded column scheme with data 
in sparse columns
                 Key: PHOENIX-3559
                 URL: https://issues.apache.org/jira/browse/PHOENIX-3559
             Project: Phoenix
          Issue Type: Sub-task
            Reporter: Mujtaba Chohan


Schema with 5K columns
{noformat}
create table (k1 integer, k2 integer, c1 varchar ... c5000 varchar CONSTRAINT 
PK PRIMARY KEY (K1, K2)) 
VERSIONS=1, MULTI_TENANT=true, IMMUTABLE_ROWS=true
{noformat}

In this schema, only 100 random columns are filled with random 15 chars. Rest 
are nulls.

Data size is *6X* larger with encoded columns scheme compare to non-encoded. 
That is 12GB/1M rows encoded vs ~2GB/1M rows non-encoded.

When compressed GZ, size with encoded column scheme is still 35% higher.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to