I agree that this semantic change is an unfortunate problem in the 1.x to 2.x upgrade path and needs to be addressed.
It is irresponsible to tell users that a valid workaround is to use an insecure, untested, not-clustered and not-fully-functional port as the primary access to CouchDB. The consequences are worse than the workaround. -Joan ----- Original Message ----- > From: "Igor Ievsiukov" <igor.ievsiu...@gmail.com> > To: woh...@apache.org > Cc: user@couchdb.apache.org > Sent: Friday, July 6, 2018 12:15:26 PM > Subject: Re: Call for "Must-fix" issues > 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.
