Hi Sreeram., HBase will not split a region withing a row. So if a row gets WAY to many columns, its size can grow higher than the configured max region size. Which, of course, is not recommended because your region will serve a single row. If you think your row will become bigger than 1% or your max regionsize, you are better to think about a tall design instead of a wide one.
JMS 2016-10-17 5:31 GMT-04:00 Sreeram <[email protected]>: > Hi All, > > Please let me know if the maximum size of a HBase row (in terms of storage > space) will be equal to the configured size of a region? > > I understand the parameter hbase.table.max.rowsize to be the maximum bytes > that can be transferred in a single get/scan operation and not related to > the actual size of row in HBase. > > Is my understanding correct? Kindly let me know. > > Regards, > Sreeram >
