4 ms·
I'm genuinely curious why you hold that opinion, especially in context of a thread that discusses a service that's available through the standard hbase api
by vgt 11y ago
I'm genuinely curious why you hold that opinion, especially in context of a thread that discusses a service that's available through the standard hbase api
- rodionos 11y agoWithout support for co-processors in BigTable I would hardly call it 'standard' API. Also the implementation of buffered mutation, a key attraction in HBase 1+ for fast non-blocking writes, is different enough in bigtable that you might have to change application code to work it consistently. It's nice though that bigtable API have references to HBase bugs :) > HBase 1.0.0 has a bug in it. It returns maxSize instead of the buffer size for > getWriteBufferSize. https://issues.apache.org/jira/browse/HBASE-13113 https://issues.apache.org/jira/browse/HBASE-13113