When row size exceeds region size, the row would stay in one region. Cheers
> On Apr 25, 2017, at 2:28 AM, schausson <[email protected]> wrote: > > OK, so this is not supported for now... > > Additional questions related to region size : > > If I set "versions" to high value (several millions for instance), the size > of a row may exceed the region size...What will happen in such case ? > > And if I consider another design, like saving versions in additional > colmumns (column id could be concatenated with history timestamp), the same > question raises up : if we save millions of columns, what is the behavior > when row size exceeds the region size ? > > Thanks again for your help > > > > > > -- > View this message in context: > http://apache-hbase.679495.n3.nabble.com/Unlimited-number-of-versions-for-a-column-family-tp4087673p4087677.html > Sent from the HBase User mailing list archive at Nabble.com.
