On Wed, Jun 21, 2017 at 11:11 PM, Phil Yang wrote:
> Hi Stack
> It seems there are only 21 slides here but we have 24 talks totally?
>
> Thanks Phil. AMZ and G don't want their slides posted. I didn't bother
posting the housekeeping slides.
S
> Thanks,
> Phil
>
>
> 2017-06-21 3:45 GMT+08:00 St
bq. HBase doesn't do well with more than 2-3 column families
The above is out of date - we have per column family flush which would
reduce the number of small hfiles.
bq. Why can't we just create several tables instead?
Currently hbase doesn't provide transaction across region boundary. This
mea
One use-case that applies to my tables is that I have a table with a set of
columns that have data that is always processed with MR jobs, but other rather
large columns
that are generally only accessed through a UI. By separating those into two
column families, MR jobs that do a full table scan on
Hi,
A general question regarding column families. It is said in the doc that
HBase doesn't do well with more than 2-3 column families because flushing
and compactions are done on a per region basis which should be addressed in
the future: http://hbase.apache.org/book.html#number.of.cfs
Is it stil
