suggestion: be clear about 2.0 on the examples
hi,
Our team spent a full week trying to upload data to the couchbase 2.
unfortunately the information about changes in functionallity from version 1 to 2 are bad or wrong.
1) There is no a functional example that allows to say how to create a database , insert info , etc and access it.
2)there is no info about how to create a database or access it with passwords, or via curl
in 2.0, withsecurity.
yes , the apis you could say that is the way in 2.0 , but all are wrong in 2.0, a simple data like "one two" brokes the upload of info in couchbase 2.0 - in php, ruby, etc.
you say couchbase 2 api for access vbuckets, weinstalled, but it doesnt work...
2) The memcache change in 2.0 makes that all the information gets lost now when the last server goes down? -it seems that it is happening . is there a way to avoid it or should we look for another nosql solution?
we have to take a decision about the couchbase,
or to look for another nosql database.
but in a week none of the it persons (that they like couchbase 1) , none were able to create ,insert and access on couchbase 2.0 a simple record with simple content like "one" or "one two"
is there any way to solve that common questions about couchbase 2 ?
thank you
I think part of the confusion might also be that you are trying to use Couchbase Server as a replacement for CouchDB/Couchbase Single.
Putting data in via port 5984 will not update the caching layer...therefore you won't be able to access it. There is also a different DB structure under the hood of Couchbase Server (there is a separate database for each vbucket...currently 16)
If you're looking for something totally compatible with CouchDB, then Couchbase Single Server is the way to go. If you're looking for something that is highly and dynamically scalable, with an integrated caching layer...you need to go with Couchbase Server and use the memcached interface to put data in and get it out. The CouchDB style views are available through a scatter-gather proxy.
Perry
thank you,
yes, we were checking couchdb against couchbase server, and in futon it allowed us to insert fields with spaces,
you are rigth it could be the space that curl does not accept.
ah, ok, every bucket is a database, but how to access that specific bucket from the APIs?
about the server that lost the information when shutting down, we have set in crate default bucket/bucket settings/ bucket type: couchbase (and not memcached). with 1 replication, and first the replication server went down, and after that, this server went down, inserted simple info with the api, and when we restarted the machine there were not views nor info.
thank you
Alberto
Alberto, depending on your language, you have different options for accessing a specific bucket. Best to read up on the documentation at couchbase.org/code for your specific language (be sure to navigate to the "2.0 developer preview" section since there is still some legacy Membase information in there).
As for your last comment, it sounds like you tried to insert some data after the machine was already down? You'll need to ensure that at least some servers are still functioning when putting data in. You should have gotten an error back saying the data was not stored...
Also, be sure that you trigger a failover when a server goes down in order to activate the replica copies...otherwise that portion of data will still be unavailable.
Perry
1) Databases in COuchbase are referred to as buckets. In order to create one go log into the web ui (http://ip_address:8091), click the "Data Buckets" tab and then click "Create New Data Bucket". See the link below for more information:
http://docs.couchbase.org/couchbase-manual-2.0/couchbase-admin.html#couc...
2) When you click on the "Create New Data Bucket" you will want to create a bucket with SASL authentication. Just check the box for "Standard Port" access control and input a password for that bucket.
I think the reason your data is not getting put into Couchbase is because you have spaces in your id field. Couchbase doesn't allow spaces to be in the id field. I recommend changing each space to a '_'.
3) Can you check to make sure you have created a couchbase bucket. It sounds like you are using a memcached bucket and memcached buckets don't persist any data to disk. If you are using a memcached bucket then you will need to switch to a couchbase bucket in order for items to be persisted to disk.