[
https://issues.apache.org/jira/browse/HBASE-8959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Max Lapan updated HBASE-8959:
-----------------------------
Description:
I think it would be useful to natively support bitmasks in hbase columns with
ability to check/set/clear/toggle individual bits in byte[] for any column.
Now, we forced to store lots of feature flags as separate, 1-byte values, which
is a waste of space. Compression helps, I guess, but anyway, not ideal.
I see this as a set of new KeyValue.Type, which describes needed
bit-operations. Operations itself performed on compaction or scan process.
Similiar things a performed for KeyValue.Minimum and KeyValue.Maximum.
What do you think about this feature? Maybe, I'm missing something and it is
much harder to implement than I think?
was:
I think it would be useful to natively support bitmasks in hbase columns with
ability to check/set/clear/toggle individual bits in byte[] for any column.
Now, we forced to store lots of feature flags as separate, 1-byte values, which
is a waste of space. Compression helps, I guess, but anyway, not ideal.
I see this as a set of new KeyValue.Type, which describes needed
bit-operations. Operations itself performed on compaction or scan process.
Similiar things a performed for KeyValue.Minimum and KeyValue.Maximum.
What do you think about this feature? Maybe, I missing something and it is much
harder to implement than I imagine?
> Bitmasks handling
> -----------------
>
> Key: HBASE-8959
> URL: https://issues.apache.org/jira/browse/HBASE-8959
> Project: HBase
> Issue Type: New Feature
> Reporter: Max Lapan
> Priority: Minor
>
> I think it would be useful to natively support bitmasks in hbase columns with
> ability to check/set/clear/toggle individual bits in byte[] for any column.
> Now, we forced to store lots of feature flags as separate, 1-byte values,
> which is a waste of space. Compression helps, I guess, but anyway, not ideal.
> I see this as a set of new KeyValue.Type, which describes needed
> bit-operations. Operations itself performed on compaction or scan process.
> Similiar things a performed for KeyValue.Minimum and KeyValue.Maximum.
> What do you think about this feature? Maybe, I'm missing something and it is
> much harder to implement than I think?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
