I don't think there is any performance benefit as such. From the
source code, it appears that the only use is to avoid accidentally
updating / mutating a table that you want to keep immutable.
So - setting the read only flag will prevent accidental updates to that table.
On Wed, Nov 2, 2011 at 11:25 AM, Homer Strong <[EMAIL PROTECTED]> wrote:
> Just out of curiosity, are there any performance benefits from setting
> READONLY to true on tables? I've checked out the HBase book and
> Definitive Guide and the API docs, but none of them go beyond a basic
> description of READONLY behavior (which seems to be pretty simple :)).