Re: [DISCUSS] HBase-2.0 SHOULD be rolling upgradable and wire-compatible with 1.x

+1 on both rolling upgradable and wire-compatible with 1.x. Requiring end users to upgrade hbase client means they have to restart their application, which is really miserable, not mentioning the coordination work required with different users... Best Regards, Yu On 22 June 2016 at 10:29, Heng

Re: [DISCUSS] HBase-2.0 SHOULD be rolling upgradable and wire-compatible with 1.x

bq. We should keep main data paths working between 1.x client and 2.0 cluster. It is fine if some admin operation does not work with older client. +1 2016-06-22 2:13 GMT+08:00 Enis Söztutar : > Agreed with above. We should keep main data paths working between 1.x > client and

Re: [DISCUSS] HBase-2.0 SHOULD be rolling upgradable and wire-compatible with 1.x

Agreed with above. We should keep main data paths working between 1.x client and 2.0 cluster. It is fine if some admin operation does not work with older client. Agreed on replication as well, it must work or we should have a dedicated replicator implementation. HBASE-16060 would have been fine

Re: [DISCUSS] HBase-2.0 SHOULD be rolling upgradable and wire-compatible with 1.x

Inline > On Jun 20, 2016, at 11:30 PM, Matteo Bertozzi wrote: > > I think everyone wants rolling upgrade. the discussion should probably be > around how much compatibility code do we want to keep around. > > using as example HBASE-16060, we need to decide how much are

Re: [DISCUSS] HBase-2.0 SHOULD be rolling upgradable and wire-compatible with 1.x

+1 on requiring upgrading to one of the latest 1.x.y before upgrading to 2.0. 2016-06-21 14:30 GMT+08:00 Matteo Bertozzi : > I think everyone wants rolling upgrade. the discussion should probably be > around how much compatibility code do we want to keep around. > >

Re: [DISCUSS] HBase-2.0 SHOULD be rolling upgradable and wire-compatible with 1.x

I think everyone wants rolling upgrade. the discussion should probably be around how much compatibility code do we want to keep around. using as example HBASE-16060, we need to decide how much are we rolling upgradable and from where. I'm not too convinced that we should have extra code in master

Re: [DISCUSS] HBase-2.0 SHOULD be rolling upgradable and wire-compatible with 1.x

If there’s no technical limitation, we should definitely do it. As you note, customers running in production hate when they have to shut down clusters and with some of the testing infrastructure being rolled out, this is definitely something we can set up automated testing for. +1 -Dima On Mon,

[DISCUSS] HBase-2.0 SHOULD be rolling upgradable and wire-compatible with 1.x

Time to formalize 2.0 rolling upgrade scenario? 0.94 -> 0.96 singularity was a real pain for operators and for our users. If possible we should not have the users suffer through the same thing unless there is a very compelling reason. For the current stuff in master, there is nothing that will