We are currently working on switching all our projects to CouchDB 2.x and facing many issues and problems that we have to fix/change on our side, but this is taking a lot of time. E.g.
In one project we are using OAuth 1.0 for authentication, that was pretty good integrated, but it is not available anymore. We know about the reasons for removing this feature, but to switch this on our project we will need time. In one project we are using Geocouch, I’m not sure if this is still working for CouchDB 2.x, perhaps someone can point here some information about this? We have faced some issues with proxy configuration for replications, see https://github.com/apache/couchdb/issues/1080 There seems to be a change in the Content-Security-Policy, which does not allow to evaluate code in the validate_doc_update.js anymore, this was also a blocker for us. But we where able to fix this. And then there is Fauxton. When it first was introduced I liked it pretty much and thought hey a new UI, finally. But now I’m not happy with it and missing some major functionalities: 1. Compact a Database 2. Adding just a field to a document. I know I can do this in JSON as well, but in many cases it was just easier and quicker, by using this functionality. 3. By the way, where is the fields view? It was pretty good to get an overview about a big document. 4. Why are the _users and _replicator databases not shown in Fauxton? Please do not see anything as criticism, CouchDB 2.x and Fauxton are great and the step in the right direction. We want and will switch to the new version, but there are several issues that needs to be fixed, on our side! Regards Martin > This thread reach out to CouchDB 1.x users to generate a list of > "must-fix" issues that is preventing users to upgrade to the latest > version of CouchDB. > > It is in response to Joan's comment below regarding the > non-technical proposal to make a project decision to terminate > official Apache support for CouchDB 1.x. > >> On 5 Jul 2018, at 06:31, Joan Touzet <[email protected]> wrote: >> >> As for things in 2.x that are "must fix" before people can upgrade, I >> too would like to see pull requests for those. Once again, your help is >> most welcome in this - both in identifying a definitive list of those >> must-fix issues, as well as code towards fixing them. If you'd like >> to help with this important work, please start a new thread. > > Mine is CouchDB as a proxy. > The feature described here is not working in 2.1.1 > http://docs.couchdb.org/en/2.1.1/config/proxying.html?highlight=_proxy > > Johs
