[
https://issues.apache.org/jira/browse/HBASE-8959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13709877#comment-13709877
]
Max Lapan commented on HBASE-8959:
----------------------------------
When such update performed by a client, there is a chance of concurrent update.
One task can set one bit, other update another in the same byte and the whole
result is unpredictable. If bit operations are in KeyValues, there is no such
problem - both clients put two KeyValues which update different bits. On nexct
compact, RS will combine them into correct value.
> 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
