Disabling the table should not be needed. From the stripe compaction
perspective, deploying this in a disabled table versus in an online alter
table is not different at all. The "hbase.online.schema.update.enable"
property was fixing some possible race conditions that were fixed long time
ago.
We
Thanks Ted, I have seen that and I have had it set for to true for years
without issue. I was asking in this case because the docs for stripe
compaction explicitly say to disable the table. I will test in our QA
environment first, but would also appreciate input from anyone who has done
this
Have you seen the doc at the top
of ./hbase-shell/src/main/ruby/shell/commands/alter.rb ?
Alter a table. If the "hbase.online.schema.update.enable" property is set to
false, then the table must be disabled (see help 'disable'). If the
"hbase.online.schema.update.enable" property is set to true,
Hello,
We're running hbase 1.2.0-cdh5.7.0. According to the HBase book, in order
to enable stripe compactions on a table we need to first disable the table. We
basically can't disable tables in production. Is it possible to do this
without disabling the table? If not, are there any plans to make
