Hi Joan, Thank you for additional explanations.
I myself know this rule very well, but imagine a scenario of a sysadmin in some company, not aware of this nuance, upgrading couchdb1x => 2x on their internal app that still uses the old repl doc seantics – the side-effect might not be visible at first, but the consequences will be very nasty and a very angry user in the end. - Igor Le ven. 6 juil. 2018 à 18:01, Joan Touzet <[email protected]> a écrit : > HI Igor, > > Just to call out: *Don't use the node-local port(5986) for any > replication other than migrating 1.x databases to 2.x* (as performed by > couchup). > > Also, do not use the node-local port for any other operations unless the > documentation explicitly directs you to do so. > > Port 5986 is deprecated for all other purposes in 2.x, and will be removed > in 3.x. > > -Joan > > ------------------------------ > > *From: *"Igor Ievsiukov" <[email protected]> > *To: *[email protected] > *Cc: *[email protected] > *Sent: *Friday, July 6, 2018 11:51:04 AM > *Subject: *Re: Call for "Must-fix" issues > > Hi everyone, > > +1 to view E-Tags > > my 2c: replication doc semantics compatibility > > couchdb1.x > { > "source": "db1", > "target": "http://user:pass@localhost/db2"; > } > ^ both db name and url supported > > couchdb2.x > { > "source": "http://user:pass@localhost/db1";, > "target": "http://user:pass@localhost/db2"; > } > ^ only url is supported; db name uses node-local port > > while not the biggest problem, still requires application refactoring > which is not always possible and could be a blocking point for some. > > - Igor > > Le ven. 6 juil. 2018 à 14:44, Johs Ensby <[email protected]> a écrit : > >> Hi, >> Here's a wrap-up of this from my side. >> Johs >> >> #### UPGRADE-BLOCKING >> ======================================================== >> Views ETags for HTTP caching >> -------------------------------------------------------------------------------------------------- >> >> (thanks to Aurélien) >> (COUCHDB-2859) >> https://github.com/apache/couchdb/pull/1237 >> >> ======================================================== >> Proxy authorization >> -------------------------------------------------------------------------------------------------- >> >> (thanks to emouth) >> -export([proxy_authentication_handler/1]) and >> proxy_authentication_handler(Req) -> >> couch_httpd_auth:proxy_authentication_handler(Req, chttpd_auth_cache). >> In docs, but absent in 2.x. >> >> ======================================================== >> CouchDB as a proxy >> -------------------------------------------------------------------------------------------------- >> >> https://github.com/apache/couchdb/issues/1407 >> In docs, but absent in 2.1.1 >> >> ======================================================== >> Fauxton >> -------------------------------------------------------------------------------------------------- >> >> (thanks to Kai) >> Productivity/UX issues >> As an slternative I recommend to https://github.com/ermouth/couch-photon >> >> PLATFORM-SPECIFC >> ======================================================== >> Lack for a working FreeBSD port >> -------------------------------------------------------------------------------------------------- >> >> (thanks to Andrea) >> >> >> #### ENHANCEMENT suggestions >> ======================================================== >> Fauxton >> -------------------------------------------------------------------------------------------------- >> >> (thanks to David) >> logged by Joan: >> https://github.com/apache/couchdb-fauxton/issues/1099 >> https://github.com/apache/couchdb-fauxton/issues/1100 >> >> -------------------------------------------------------------------------------------------------- >> >> >> >> I left aside reports of 1.x behaviour not possible to add to 2.x (ref >> Jans respons) >> >> > On 5 Jul 2018, at 17:46, Joan Touzet <[email protected]> wrote: >> > >> >> On 2018-07-05 09:10, Johs Ensby wrote: >> >> >> >>> 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 >> >> >> >
