2.0 needs to support use couchbase for all the REST endpoints. (no membase)

"Part of membase -> couchbase transition is renaming of bucket type.

But because we also need to support mixed clusters for rebalance upgrade we'll have to handle both membase and couchbase bucket types internally. We won't upgrade membase -> couchbase during upgrade. But rather new buckets will be created with type couchbase.

Heres relevant parts from emails from 1.8 rebranding times:

From: Matt Ingenthron <matt@couchbase.com>
Date: Wed, 30 Nov 2011 14:41:44 -0800
To: Dipti Borkar <dipti@couchbase.com>, Aliaksey <alkondratenko@gmail.com>
Cc: Benjamin Young <benjamin@couchbase.com>, mgmt_dev <mgmt_dev@couchbase.com>, Frank Weigel <frank@couchbase.com>, Perry Krug <perry@couchbase.com>, Farshid Ghods <farshid@couchbase.com>, sdk_dev <sdk_dev@couchbase.com>, Steve Yen <steve@couchbase.com>, MC Brown <mc@couchbase.com>

Subject: Re: Renaming buckettype from membase to couchbase in 1.8.0

Alk brought up one other case which hasn't been considered though. What about mixed clusters?

I think the answer is that it should say ""couchbase"" from all nodes if possible. If that's too hard, it's okay for some to say ""membase"" and some to say ""couchbase"", but the key thing is that after rebalancing out all 1.8 nodes, it should say ""couchbase"".

Dipti: if you agree, please let Alk know.

(alk: this is in-line reply by Dipti)
Yes, agreed. ns_server needs to be able to handle both types to handle upgrades.

Thanks,

Matt

p.s.: I hope we're starting testing of upgrade from 1.8 to 2.0 early, so we can wring out any problems to avoid forcing people to take an incremental patch of 1.8 just so they can get to 2.0.

On 11/30/11 2:36 PM, ""Dipti Borkar"" <dipti@couchbase.com> wrote:

Frank, Matt and I talked about it today and agreed on the following.

For 1.8.0
UI reflects ""Couchbase"" as the bucket type â€" on the Manage data buckets page and on the Create bucket page
REST API
Post takes in both ""membase"" or ""couchbase"" as bucket type but internally, it is still stored as ""membase"" (most people will continue to use membase until they are forced to change it to 2.0
Get sends back ""membase"" as buckettype
Documentation section on deprecation will list buckettype ""membase"" as deprecated in 1.8.0
For 2.0
REST API
Post takes in both ""membase"" or ""couchbase"" as bucket type and is stored as ""couchbase""
Get sends back ""couchbase"" as buckettype
Documentation release notes will mention that buckettype ""membase"" was deprecated and ""couchbase"" is the new buckettype name

http://www.pivotaltracker.com/story/show/24607551