Originally from the User Slack
@Aleksandr_Udovenko: Hello i have table like this:
CREATE TABLE items (
itemID bigint,
offset bigint,
props1 bigint,
props2 bigint,
PRIMARY KEY( (itemID), offset) );
I will have non NULL
values for props1
, props2
very rare, only when offset
==0. Does scylla optimize store props1
,props2
if it will be NULL
in 99% ? (in my real DB i have many props
)
@Felipe_Cardeneti_Mendes: Storage wise, yes - null is… well null 
If you are wondering how NULL handling works see https://github.com/scylladb/scylladb/blob/6d7cb68aabea41024fac925aebc014139f4e5568/docs/cql/cql-extensions.md#null
GitHub: scylladb/docs/cql/cql-extensions.md at 6d7cb68aabea41024fac925aebc014139f4e5568 · scylladb/scylladb
@Aleksandr_Udovenko: NULL from point CQL it is intresting, but i need to undertand it from storage side)