cloudant

When using the SDP to extract data from Cloudant and populate dashDB, I occasionally see error messages in the dashdb "XXXX_OVERFLOW" table that look like this: No matched schema for {"_id":"...","doc":{...} Questions What does this error mean? How can I fix it? Chris Snow There are two main phases to the SDP process: Schema analysis Data import In the schema analysis phase, the SDP analyses a sample of documents in Cloudant and uses the document structures of the sample to infer the target schema in dashDB. The above error is encountered when the SDP tries to import a document with a schema

So when a document is deleted, the metadata is actually preserved forever. For a hosted service like cloudant, where storage costs every month, I instead would like to completely purge the deleted documents. I read somewhere about a design pattern where you use dbcopy in a view to put the docs into a 'current' db then periodically delete the expired dbs. But I cant find the article, and I don't quite understand how database naming would work. How would the cloudant clients always know the 'current' database name? Cloudant does not expose the _purge endpoint (the loose consistency guarantees

I've been stuck on this far longer than I want to admit. I want to connect to cloudant/couchdb using WebSphere Liberty. I'm fairly new to Java app development, Liberty, Cloudant and Bluemix. I believe I need to add a SSL certificate for cloudant in a local trust store but the only way to do it seems to be by using the Websphere Application Server Integrated Solutions Console, which I can't run using Liberty? If anyone can guide me in the right direction I would appreciate it alot! [ERROR ] CWPKI0022E: SSL HANDSHAKE FAILURE: A signer with SubjectDN CN=*.cloudant.com, OU=Engineering, O="Cloudant

I'm getting set up with CouchDB on Cloudant, and I'm confused because Cloudant seems to do auth differently than regular CouchDB. Specifically, Cloudant seems to lack a _users database. I read the Cloudant auth FAQ here , and it provided the following instructions: Can I use CouchDB security features (_users database, security objects, validation functions) on Cloudant? Yes you can. If you want to use the _users database you must first turn off Cloudant's own security for the roles you want to manage via _users. To do this you need to PUT a JSON document like the following to the _security