You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by Johs Ensby <jo...@b2w.com> on 2018/07/05 07:10:32 UTC
Call for "Must-fix" issues
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 <wo...@apache.org> 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
Re: Call for "Must-fix" issues
Posted by Andrea Brancatelli <ab...@schema31.it>.
Well, mine is the lack for a working FreeBSD port for CouchDB 2.x...
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218844
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 <wo...@apache.org> 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
Re: Call for "Must-fix" issues
Posted by Jan Lehnardt <ja...@apache.org>.
> On 5. Jul 2018, at 13:54, Mad, Pink and Dangerous to Know <pi...@mad.pink> wrote:
>
> This isn't really a "fix" per se, but one of the reasons I still use
> CouchDB 1.x is the change log. I have a homemade local syncing library for
> Livecode that I use that is heavily dependent on the old _changes api. I've
> been working on changing it for 2.x, but it involves having to add my own
> version of the change log to documents as they are being written)
>
> I understand why it was changed, but it would be great if there were a
> similar system available in 2.x
This is a great point!
It is regrettable, that 1.x had undefined behaviour that we had to give up
for 2.x, that folks relied on early on. It is the main one of the very few API
design mistakes we’ve made (IMHO), but there is no way to add 1.x behaviour to
2.x (although q=1 and n=1 will get you close).
Best
Jan
—
>
> On Thu, Jul 5, 2018 at 3:10 AM Johs Ensby <jo...@b2w.com> 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 <wo...@apache.org> 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
>>
--
Professional Support for Apache CouchDB:
https://neighbourhood.ie/couchdb-support/
Re: Call for "Must-fix" issues
Posted by Jan Lehnardt <ja...@apache.org>.
> On 5. Jul 2018, at 13:54, Mad, Pink and Dangerous to Know <pi...@mad.pink> wrote:
>
> This isn't really a "fix" per se, but one of the reasons I still use
> CouchDB 1.x is the change log. I have a homemade local syncing library for
> Livecode that I use that is heavily dependent on the old _changes api. I've
> been working on changing it for 2.x, but it involves having to add my own
> version of the change log to documents as they are being written)
>
> I understand why it was changed, but it would be great if there were a
> similar system available in 2.x
This is a great point!
It is regrettable, that 1.x had undefined behaviour that we had to give up
for 2.x, that folks relied on early on. It is the main one of the very few API
design mistakes we’ve made (IMHO), but there is no way to add 1.x behaviour to
2.x (although q=1 and n=1 will get you close).
Best
Jan
—
>
> On Thu, Jul 5, 2018 at 3:10 AM Johs Ensby <jo...@b2w.com> 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 <wo...@apache.org> 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
>>
--
Professional Support for Apache CouchDB:
https://neighbourhood.ie/couchdb-support/
Re: Call for "Must-fix" issues
Posted by "Mad, Pink and Dangerous to Know" <pi...@mad.pink>.
This isn't really a "fix" per se, but one of the reasons I still use
CouchDB 1.x is the change log. I have a homemade local syncing library for
Livecode that I use that is heavily dependent on the old _changes api. I've
been working on changing it for 2.x, but it involves having to add my own
version of the change log to documents as they are being written)
I understand why it was changed, but it would be great if there were a
similar system available in 2.x
On Thu, Jul 5, 2018 at 3:10 AM Johs Ensby <jo...@b2w.com> 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 <wo...@apache.org> 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
>
Re: Call for "Must-fix" issues
Posted by Johs Ensby <jo...@b2w.com>.
Hi Harald,
how about starting a new thread on the topic, incuding dev@ and users@?
Compared to the https://db-engines.com/en/ranking_trend/system/CouchDB (auto collected web data)
the review service you linked to have a massive amount of reviews from MongoDB people.
Your question could motivate CouchDB users to summit reviews to g2crowd, and give detailed data in addition to the 44 people that did so already,
Johs:)
> On 5 Jul 2018, at 13:13, Harald Kisch <ha...@gmail.com> wrote:
>
> Previously I got a lot of recognition by using CouchDB 1.x
> Now I would be interested in the reasons why people prefer Mongo, Cassandra, Redis, HBase,..
> Is it the Quality of support only?
> https://www.g2crowd.com/categories/document-databases#highest_rated <https://www.g2crowd.com/categories/document-databases#highest_rated>
>
> harald
>
>> Am 05.07.2018 um 12:57 schrieb ermouth <er...@gmail.com>:
>>
>>> This is rather inaccurate
>>> A regrettable regression,
>>> but only a config issue
>>
>> Well enough to block upgrade. Anyway, as we see now those non-technical
>> issues of different nature improve the number of requests for paid support.
>> I wouldn’t account this fact as popularity, as Joan did, however hope it at
>> least sweetens regrets.
>>
>> ermouth
>
Re: Call for "Must-fix" issues
Posted by Harald Kisch <ha...@gmail.com>.
Previously I got a lot of recognition by using CouchDB 1.x
Now I would be interested in the reasons why people prefer Mongo, Cassandra, Redis, HBase,..
Is it the Quality of support only?
https://www.g2crowd.com/categories/document-databases#highest_rated <https://www.g2crowd.com/categories/document-databases#highest_rated>
harald
> Am 05.07.2018 um 12:57 schrieb ermouth <er...@gmail.com>:
>
>> This is rather inaccurate
>> A regrettable regression,
>> but only a config issue
>
> Well enough to block upgrade. Anyway, as we see now those non-technical
> issues of different nature improve the number of requests for paid support.
> I wouldn’t account this fact as popularity, as Joan did, however hope it at
> least sweetens regrets.
>
> ermouth
Re: Call for "Must-fix" issues
Posted by ermouth <er...@gmail.com>.
> This is rather inaccurate
> A regrettable regression,
> but only a config issue
Well enough to block upgrade. Anyway, as we see now those non-technical
issues of different nature improve the number of requests for paid support.
I wouldn’t account this fact as popularity, as Joan did, however hope it at
least sweetens regrets.
ermouth
Re: Call for "Must-fix" issues
Posted by Jan Lehnardt <ja...@apache.org>.
> On 5. Jul 2018, at 11:32, ermouth <er...@gmail.com> wrote:
>
>> convenience of one file on disk per database is gone, but is there
> anything else
>
> There were serious issues with single node shards (or whatever those pieces
> were) during upgrade from 2.1.0 to 2.1.1. I read only brief report, but
> remember it completely broken tests in some bizzare way, like inability to
> save docs with particular _id ranges.
This is rather inaccurate. The issue was a change of vm.args -name, that
made existing shards unreadable. A regrettable regression, but only a config
issue, that is a one line change to fix.
There was no technical issue here.
>
>> could you unveil this secret, please?
>
> There’s nothing secret here, theoretically you have to insert two oneliners
> into chttpd_auth and then rebuild. Obvious task for end user )
>
> -export([proxy_authentication_handler/1]).
> and
> proxy_authentication_handler(Req) ->
> couch_httpd_auth:proxy_authentication_handler(Req, chttpd_auth_cache).
>
> But as I can recollect it also finally broke things in some bizzare way.
>
>
> ermouth
>
> 2018-07-05 11:59 GMT+03:00 Johs Ensby <jo...@b2w.com>:
>
>>>>
>>>> Proxy authorization which is also in docs, but absent in 2.x.
>>>
>>> it is not absent, just not exposed by default. You can configure to
>> enable it (it’s just not documented ;)
>>
>> Hi Jan,
>> could you unveil this secret, please?
>> johs
>>
>>
>>
>>> On 5 Jul 2018, at 10:53, Jan Lehnardt <ja...@apache.org> wrote:
>>>
>>>
>>>
>>>> On 5. Jul 2018, at 10:20, ermouth <er...@gmail.com> wrote:
>>>>
>>>> Proxy authorization which is also in docs, but absent in 2.x.
>>>
>>> it is not absent, just not exposed by default. You can configure to
>> enable it (it’s just not documented ;)
>>>
>>>> Single-node install without shards.
>>>
>>> Both the /_setup_cluster endpoint and the Mac binaries already set q=1 &
>> n = 1 on setup. Everyone else can configure it.
>>>
>>> Best
>>> Jan
>>> —
>>>
>>>>
>>>> ermouth
>>>>
>>>> 2018-07-05 10:10 GMT+03:00 Johs Ensby <jo...@b2w.com>:
>>>>
>>>>> 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 <wo...@apache.org> 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
>>>>>
>>>
>>> --
>>> Professional Support for Apache CouchDB:
>>> https://neighbourhood.ie/couchdb-support/
>>>
>>
>> ………………………………………
>> Johannes Ensby
>>
>>
>> Business to Web AS
>> Tollbugata 8, N- 0152 Oslo, Norway
>> +47 611 00 006 (mobile)
>> +47 611 00 700 (switchboard)
>> johs@b2w.com
>> www.linkedin.com/in/ensby
>> www.b2w.com
>>
>>
--
Professional Support for Apache CouchDB:
https://neighbourhood.ie/couchdb-support/
Re: Call for "Must-fix" issues
Posted by ermouth <er...@gmail.com>.
> convenience of one file on disk per database is gone, but is there
anything else
There were serious issues with single node shards (or whatever those pieces
were) during upgrade from 2.1.0 to 2.1.1. I read only brief report, but
remember it completely broken tests in some bizzare way, like inability to
save docs with particular _id ranges.
> could you unveil this secret, please?
There’s nothing secret here, theoretically you have to insert two oneliners
into chttpd_auth and then rebuild. Obvious task for end user )
-export([proxy_authentication_handler/1]).
and
proxy_authentication_handler(Req) ->
couch_httpd_auth:proxy_authentication_handler(Req, chttpd_auth_cache).
But as I can recollect it also finally broke things in some bizzare way.
ermouth
2018-07-05 11:59 GMT+03:00 Johs Ensby <jo...@b2w.com>:
> >>
> >> Proxy authorization which is also in docs, but absent in 2.x.
> >
> > it is not absent, just not exposed by default. You can configure to
> enable it (it’s just not documented ;)
>
> Hi Jan,
> could you unveil this secret, please?
> johs
>
>
>
> > On 5 Jul 2018, at 10:53, Jan Lehnardt <ja...@apache.org> wrote:
> >
> >
> >
> >> On 5. Jul 2018, at 10:20, ermouth <er...@gmail.com> wrote:
> >>
> >> Proxy authorization which is also in docs, but absent in 2.x.
> >
> > it is not absent, just not exposed by default. You can configure to
> enable it (it’s just not documented ;)
> >
> >> Single-node install without shards.
> >
> > Both the /_setup_cluster endpoint and the Mac binaries already set q=1 &
> n = 1 on setup. Everyone else can configure it.
> >
> > Best
> > Jan
> > —
> >
> >>
> >> ermouth
> >>
> >> 2018-07-05 10:10 GMT+03:00 Johs Ensby <jo...@b2w.com>:
> >>
> >>> 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 <wo...@apache.org> 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
> >>>
> >
> > --
> > Professional Support for Apache CouchDB:
> > https://neighbourhood.ie/couchdb-support/
> >
>
> ………………………………………
> Johannes Ensby
>
>
> Business to Web AS
> Tollbugata 8, N- 0152 Oslo, Norway
> +47 611 00 006 (mobile)
> +47 611 00 700 (switchboard)
> johs@b2w.com
> www.linkedin.com/in/ensby
> www.b2w.com
>
>
Re: Call for "Must-fix" issues
Posted by Johs Ensby <jo...@b2w.com>.
>>
>> Proxy authorization which is also in docs, but absent in 2.x.
>
> it is not absent, just not exposed by default. You can configure to enable it (it’s just not documented ;)
Hi Jan,
could you unveil this secret, please?
johs
> On 5 Jul 2018, at 10:53, Jan Lehnardt <ja...@apache.org> wrote:
>
>
>
>> On 5. Jul 2018, at 10:20, ermouth <er...@gmail.com> wrote:
>>
>> Proxy authorization which is also in docs, but absent in 2.x.
>
> it is not absent, just not exposed by default. You can configure to enable it (it’s just not documented ;)
>
>> Single-node install without shards.
>
> Both the /_setup_cluster endpoint and the Mac binaries already set q=1 & n = 1 on setup. Everyone else can configure it.
>
> Best
> Jan
> —
>
>>
>> ermouth
>>
>> 2018-07-05 10:10 GMT+03:00 Johs Ensby <jo...@b2w.com>:
>>
>>> 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 <wo...@apache.org> 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
>>>
>
> --
> Professional Support for Apache CouchDB:
> https://neighbourhood.ie/couchdb-support/
>
………………………………………
Johannes Ensby
Business to Web AS
Tollbugata 8, N- 0152 Oslo, Norway
+47 611 00 006 (mobile)
+47 611 00 700 (switchboard)
johs@b2w.com
www.linkedin.com/in/ensby
www.b2w.com
Re: Call for "Must-fix" issues
Posted by Jan Lehnardt <ja...@apache.org>.
> On 5. Jul 2018, at 10:20, ermouth <er...@gmail.com> wrote:
>
> Proxy authorization which is also in docs, but absent in 2.x.
it is not absent, just not exposed by default. You can configure to enable it (it’s just not documented ;)
> Single-node install without shards.
Both the /_setup_cluster endpoint and the Mac binaries already set q=1 & n = 1 on setup. Everyone else can configure it.
Best
Jan
—
>
> ermouth
>
> 2018-07-05 10:10 GMT+03:00 Johs Ensby <jo...@b2w.com>:
>
>> 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 <wo...@apache.org> 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
>>
--
Professional Support for Apache CouchDB:
https://neighbourhood.ie/couchdb-support/
Re: Call for "Must-fix" issues
Posted by Johs Ensby <jo...@b2w.com>.
Thanks,
what is the issue related to Single-node install without shards?
(I noticed that the convenience of one file on disk per database is gone, but is there anything else?)
Johs
> On 5 Jul 2018, at 10:50, ermouth <er...@gmail.com> wrote:
>
> Single-node install without shards.
>
> ermouth
>
> 2018-07-05 11:20 GMT+03:00 ermouth <er...@gmail.com>:
>
>> Proxy authorization which is also in docs, but absent in 2.x.
>>
>> ermouth
>>
>> 2018-07-05 10:10 GMT+03:00 Johs Ensby <jo...@b2w.com>:
>>
>>> 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 <wo...@apache.org> 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
>>>
>>
>>
………………………………………
Johannes Ensby
Business to Web AS
Tollbugata 8, N- 0152 Oslo, Norway
+47 611 00 006 (mobile)
+47 611 00 700 (switchboard)
johs@b2w.com
www.linkedin.com/in/ensby
www.b2w.com
Re: Call for "Must-fix" issues
Posted by ermouth <er...@gmail.com>.
Single-node install without shards.
ermouth
2018-07-05 11:20 GMT+03:00 ermouth <er...@gmail.com>:
> Proxy authorization which is also in docs, but absent in 2.x.
>
> ermouth
>
> 2018-07-05 10:10 GMT+03:00 Johs Ensby <jo...@b2w.com>:
>
>> 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 <wo...@apache.org> 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
>>
>
>
Re: Call for "Must-fix" issues
Posted by ermouth <er...@gmail.com>.
Proxy authorization which is also in docs, but absent in 2.x.
ermouth
2018-07-05 10:10 GMT+03:00 Johs Ensby <jo...@b2w.com>:
> 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 <wo...@apache.org> 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
>
Re: Call for "Must-fix" issues
Posted by "Mad, Pink and Dangerous to Know" <pi...@mad.pink>.
This isn't really a "fix" per se, but one of the reasons I still use
CouchDB 1.x is the change log. I have a homemade local syncing library for
Livecode that I use that is heavily dependent on the old _changes api. I've
been working on changing it for 2.x, but it involves having to add my own
version of the change log to documents as they are being written)
I understand why it was changed, but it would be great if there were a
similar system available in 2.x
On Thu, Jul 5, 2018 at 3:10 AM Johs Ensby <jo...@b2w.com> 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 <wo...@apache.org> 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
>
Re: Call for "Must-fix" issues
Posted by Aurélien Bénel <au...@utt.fr>.
Hi Joan, hi Johs,
>> 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 « Views ETags » for HTTP caching (COUCHDB-2859).
https://github.com/apache/couchdb/pull/1237
Regards,
Aurélien
Re: Call for "Must-fix" issues
Posted by Aurélien Bénel <au...@utt.fr>.
Hi Joan, hi Johs,
>> 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 « Views ETags » for HTTP caching (COUCHDB-2859).
https://github.com/apache/couchdb/pull/1237
Regards,
Aurélien
Re: Call for "Must-fix" issues
Posted by ermouth <er...@gmail.com>.
I’m sorry to say, but:
— Fauxton is unable to show doc attachments list in any modern browser on
http connection
— Fauxton is still unable to make “Back” button working in _config section
— Fauxton doesn’t work on ~20% of browsers, polyfills for missing browser
features is still an unknown term for Fauxton
— Fauxton is still unable to validate at least JSON syntax on typing, I’m
not saying about Mango syntax
— Fauxton is still all about making as much UI noise as possible,
sacrificing data density
I discovered all this in first 2 minutes after install – just to check have
anything changed. You said tables?
I’m sorry to say, but tables is the least problem. Anyway, Fauxton is
absolutely on par with CouchDB 2 in terms of product quality. An you
enforce people to migrate on _this_? Are you kidding?
And, to prevent known spells: sorry, no bug reports and no pull requests,
all above problems were already reported.
ermouth
Re: Call for "Must-fix" issues
Posted by Garren Smith <ga...@apache.org>.
Hi Kai,
Fauxton now supports a table view which allows you to see many documents at
once as well as choosing which key values to see in the table. Its been out
for a while so I'm sure its in the current release but will definitely be
in the next.
Cheers
Garren
On Thu, Jul 5, 2018 at 9:32 AM, Kai Griffin <ka...@resourceandrevenue.com>
wrote:
> As developers who spend a lot of time in the CouchDB web interface, we
> have held back moving to CouchDB 2.x only because of the change from Futon
> to Fauxton. We feel that Fauxton simply does not meet the needs of
> developers as well as Futon did. It seems to be targeted more at non-devs:
> it’s very friendly-looking, modern & pretty, but is biased towards
> prettifying document JSON, at the expense of being able to scan through
> many unformatted documents, which Futon does by default.
>
> So, mainly comes down to the inability to properly see the contents of
> documents without opening up documents individually. We like to see the
> whole, unformatted document when viewing a list of documents (or, in the
> case of looking at a View, then whatever the map script outputs, but in an
> unformatted form, not prettified like Fauxton). Futon is more compact &
> developer friendly, even if to a non-dev, such views might look like a
> jumble of unformatted text. At very least, some kind of “classic mode”
> switch would be greatly welcomed, at least by us :-)
>
> Please note that it’s been awhile since I’ve looked at CouchDB 2.x, and
> the issue I brought up above might well have been addressed by someone in
> the meantime, so apologies if I’m dredging up old/non-relevant stuff (in
> which case we’ll happily jump onto 2.x!)
>
>
> On 5 July 2018 at 09:21:37, Andrea Brancatelli (abrancatelli@schema31.it)
> wrote:
>
> Well, mine is the lack for a working FreeBSD port for CouchDB 2.x...
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218844
>
> 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 <wo...@apache.org> 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
>
Re: Call for "Must-fix" issues
Posted by Garren Smith <ga...@apache.org>.
Hi Kai,
Fauxton now supports a table view which allows you to see many documents at
once as well as choosing which key values to see in the table. Its been out
for a while so I'm sure its in the current release but will definitely be
in the next.
Cheers
Garren
On Thu, Jul 5, 2018 at 9:32 AM, Kai Griffin <ka...@resourceandrevenue.com>
wrote:
> As developers who spend a lot of time in the CouchDB web interface, we
> have held back moving to CouchDB 2.x only because of the change from Futon
> to Fauxton. We feel that Fauxton simply does not meet the needs of
> developers as well as Futon did. It seems to be targeted more at non-devs:
> it’s very friendly-looking, modern & pretty, but is biased towards
> prettifying document JSON, at the expense of being able to scan through
> many unformatted documents, which Futon does by default.
>
> So, mainly comes down to the inability to properly see the contents of
> documents without opening up documents individually. We like to see the
> whole, unformatted document when viewing a list of documents (or, in the
> case of looking at a View, then whatever the map script outputs, but in an
> unformatted form, not prettified like Fauxton). Futon is more compact &
> developer friendly, even if to a non-dev, such views might look like a
> jumble of unformatted text. At very least, some kind of “classic mode”
> switch would be greatly welcomed, at least by us :-)
>
> Please note that it’s been awhile since I’ve looked at CouchDB 2.x, and
> the issue I brought up above might well have been addressed by someone in
> the meantime, so apologies if I’m dredging up old/non-relevant stuff (in
> which case we’ll happily jump onto 2.x!)
>
>
> On 5 July 2018 at 09:21:37, Andrea Brancatelli (abrancatelli@schema31.it)
> wrote:
>
> Well, mine is the lack for a working FreeBSD port for CouchDB 2.x...
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218844
>
> 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 <wo...@apache.org> 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
>
Re: Call for "Must-fix" issues
Posted by Garren Smith <ga...@apache.org>.
Hi Kai,
Fauxton now supports a table view which allows you to see many documents at
once as well as choosing which key values to see in the table. Its been out
for a while so I'm sure its in the current release but will definitely be
in the next.
Cheers
Garren
On Thu, Jul 5, 2018 at 9:32 AM, Kai Griffin <ka...@resourceandrevenue.com>
wrote:
> As developers who spend a lot of time in the CouchDB web interface, we
> have held back moving to CouchDB 2.x only because of the change from Futon
> to Fauxton. We feel that Fauxton simply does not meet the needs of
> developers as well as Futon did. It seems to be targeted more at non-devs:
> it’s very friendly-looking, modern & pretty, but is biased towards
> prettifying document JSON, at the expense of being able to scan through
> many unformatted documents, which Futon does by default.
>
> So, mainly comes down to the inability to properly see the contents of
> documents without opening up documents individually. We like to see the
> whole, unformatted document when viewing a list of documents (or, in the
> case of looking at a View, then whatever the map script outputs, but in an
> unformatted form, not prettified like Fauxton). Futon is more compact &
> developer friendly, even if to a non-dev, such views might look like a
> jumble of unformatted text. At very least, some kind of “classic mode”
> switch would be greatly welcomed, at least by us :-)
>
> Please note that it’s been awhile since I’ve looked at CouchDB 2.x, and
> the issue I brought up above might well have been addressed by someone in
> the meantime, so apologies if I’m dredging up old/non-relevant stuff (in
> which case we’ll happily jump onto 2.x!)
>
>
> On 5 July 2018 at 09:21:37, Andrea Brancatelli (abrancatelli@schema31.it)
> wrote:
>
> Well, mine is the lack for a working FreeBSD port for CouchDB 2.x...
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218844
>
> 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 <wo...@apache.org> 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
>
Re: Call for "Must-fix" issues
Posted by Martin Rudolph <m....@email.de>.
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 <wo...@apache.org> 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
Re: Call for "Must-fix" issues
Posted by Jan Lehnardt <ja...@apache.org>.
Heya Eli,
2.2.0 is imminent, two minor issues outstanding:
https://github.com/apache/couchdb/milestone/3
This took longer than it should have for various reasons, but we should be in shape to do more regular releases going forward.
Best
Jan
—
> On 16. Jul 2018, at 20:24, Eli Stevens (Gmail) <wi...@gmail.com> wrote:
>
> I was travelling, so missed this thread originally.
>
> My[1] organization is currently not using CouchDB 2.0 in production due to
> a series of regressions in all 2.x releases that have meant that 1.6.1 was
> the most stable for us. All of the currently-known issues are fixed on
> master, and we're currently evaluating a nightly build to verify. It would
> be really nice if there was a 2.2 release so that we could get those fixes
> in the form of a formal build (note that we sponsored some of the work on
> those fixes, hoping that a release would get turned around relatively
> quickly afterwards).
>
> A regular release cadence would be really nice.
>
> Cheers,
> Eli
>
> [1] - I should note that I've quit that company, so I'm no longer formally
> associated.
>
> On Fri, Jul 6, 2018 at 11:04 AM Joan Touzet <wo...@apache.org> wrote:
>
>> 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" <ig...@gmail.com>
>>> To: wohali@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.
>>
--
Professional Support for Apache CouchDB:
https://neighbourhood.ie/couchdb-support/
Re: Call for "Must-fix" issues
Posted by "Eli Stevens (Gmail)" <wi...@gmail.com>.
I was travelling, so missed this thread originally.
My[1] organization is currently not using CouchDB 2.0 in production due to
a series of regressions in all 2.x releases that have meant that 1.6.1 was
the most stable for us. All of the currently-known issues are fixed on
master, and we're currently evaluating a nightly build to verify. It would
be really nice if there was a 2.2 release so that we could get those fixes
in the form of a formal build (note that we sponsored some of the work on
those fixes, hoping that a release would get turned around relatively
quickly afterwards).
A regular release cadence would be really nice.
Cheers,
Eli
[1] - I should note that I've quit that company, so I'm no longer formally
associated.
On Fri, Jul 6, 2018 at 11:04 AM Joan Touzet <wo...@apache.org> wrote:
> 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" <ig...@gmail.com>
> > To: wohali@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.
>
Re: Call for "Must-fix" issues
Posted by Joan Touzet <wo...@apache.org>.
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" <ig...@gmail.com>
> To: wohali@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.
Re: Call for "Must-fix" issues
Posted by Igor Ievsiukov <ig...@gmail.com>.
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 <wo...@apache.org> 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" <ig...@gmail.com>
> *To: *user@couchdb.apache.org
> *Cc: *wohali@apache.org
> *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 <jo...@b2w.com> 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 <wo...@apache.org> 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 <wo...@apache.org> 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
>>
>>
>>
>
Re: Call for "Must-fix" issues
Posted by Joan Touzet <wo...@apache.org>.
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
----- Original Message -----
> From: "Igor Ievsiukov" <ig...@gmail.com>
> To: user@couchdb.apache.org
> Cc: wohali@apache.org
> 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 < johs@b2w.com > 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 < wohali@apache.org > 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 < wohali@apache.org >
> > >>>> 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
>
Re: Call for "Must-fix" issues
Posted by Igor Ievsiukov <ig...@gmail.com>.
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 <jo...@b2w.com> 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 <wo...@apache.org> 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 <wo...@apache.org> 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
>
>
>
Re: Call for "Must-fix" issues
Posted by Johs Ensby <jo...@b2w.com>.
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 <wo...@apache.org> 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 <wo...@apache.org> 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
Re: Call for "Must-fix" issues
Posted by Joan Touzet <wo...@apache.org>.
Thanks for the ideas, David!
I've logged these two requests with Fauxton here:
https://github.com/apache/couchdb-fauxton/issues/1099
https://github.com/apache/couchdb-fauxton/issues/1100
-Joan
----- Original Message -----
From: "David Alan Hjelle" <da...@thehjellejar.com>
To: user@couchdb.apache.org
Sent: Thursday, July 5, 2018 11:37:26 AM
Subject: Re: Call for "Must-fix" issues
While this hasn’t kept us back from upgrading to Couch 2, we have run into some similar challenges with Fauxton. I think they would be fairly simply fixed by adding in some UI for functionality already in the Ace editor.
Settings for code folding—it’d be nice (for us) to have the JSON documents folded by default. Even better would be the ability to set a preference as to how many levels should be unfolded by default, and saved in the browser’s local storage or something. That would help us a lot in navigating deeply nested JSON documents where the top levels usually have all the data we need when debugging.
Search functionality. It looks like the browser’s search doesn’t work, since Ace is probably doing virtual scrolling (i.e. only putting the text in the DOM that’s on the screen at the time. Ace appears to have some search functionality, but it would need some UI around it.
Again, they haven’t kept us back from upgrading, but they are some of the concerns I’ve heard from our developers when we *did* upgrade.
David Alan Hjelle
1 Corinthians 2:2
http://thehjellejar.com/ <http://thehjellejar.com/>
<http://thehjellejar.com/>See the church management software I build at Icon Systems, Inc. <http://iconcmo.com/>
Check out Rita’s spoons <http://jarofwood.com/>.
> On Jul 5, 2018, at 2:32 AM, Kai Griffin <ka...@resourceandrevenue.com> wrote:
>
> As developers who spend a lot of time in the CouchDB web interface, we have held back moving to CouchDB 2.x only because of the change from Futon to Fauxton. We feel that Fauxton simply does not meet the needs of developers as well as Futon did. It seems to be targeted more at non-devs: it’s very friendly-looking, modern & pretty, but is biased towards prettifying document JSON, at the expense of being able to scan through many unformatted documents, which Futon does by default.
>
> So, mainly comes down to the inability to properly see the contents of documents without opening up documents individually. We like to see the whole, unformatted document when viewing a list of documents (or, in the case of looking at a View, then whatever the map script outputs, but in an unformatted form, not prettified like Fauxton). Futon is more compact & developer friendly, even if to a non-dev, such views might look like a jumble of unformatted text. At very least, some kind of “classic mode” switch would be greatly welcomed, at least by us :-)
>
> Please note that it’s been awhile since I’ve looked at CouchDB 2.x, and the issue I brought up above might well have been addressed by someone in the meantime, so apologies if I’m dredging up old/non-relevant stuff (in which case we’ll happily jump onto 2.x!)
>
>
> On 5 July 2018 at 09:21:37, Andrea Brancatelli (abrancatelli@schema31.it) wrote:
>
> Well, mine is the lack for a working FreeBSD port for CouchDB 2.x...
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218844
>
> 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 <wo...@apache.org> 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
Re: Call for "Must-fix" issues
Posted by David Alan Hjelle <da...@thehjellejar.com>.
While this hasn’t kept us back from upgrading to Couch 2, we have run into some similar challenges with Fauxton. I think they would be fairly simply fixed by adding in some UI for functionality already in the Ace editor.
Settings for code folding—it’d be nice (for us) to have the JSON documents folded by default. Even better would be the ability to set a preference as to how many levels should be unfolded by default, and saved in the browser’s local storage or something. That would help us a lot in navigating deeply nested JSON documents where the top levels usually have all the data we need when debugging.
Search functionality. It looks like the browser’s search doesn’t work, since Ace is probably doing virtual scrolling (i.e. only putting the text in the DOM that’s on the screen at the time. Ace appears to have some search functionality, but it would need some UI around it.
Again, they haven’t kept us back from upgrading, but they are some of the concerns I’ve heard from our developers when we *did* upgrade.
David Alan Hjelle
1 Corinthians 2:2
http://thehjellejar.com/ <http://thehjellejar.com/>
<http://thehjellejar.com/>See the church management software I build at Icon Systems, Inc. <http://iconcmo.com/>
Check out Rita’s spoons <http://jarofwood.com/>.
> On Jul 5, 2018, at 2:32 AM, Kai Griffin <ka...@resourceandrevenue.com> wrote:
>
> As developers who spend a lot of time in the CouchDB web interface, we have held back moving to CouchDB 2.x only because of the change from Futon to Fauxton. We feel that Fauxton simply does not meet the needs of developers as well as Futon did. It seems to be targeted more at non-devs: it’s very friendly-looking, modern & pretty, but is biased towards prettifying document JSON, at the expense of being able to scan through many unformatted documents, which Futon does by default.
>
> So, mainly comes down to the inability to properly see the contents of documents without opening up documents individually. We like to see the whole, unformatted document when viewing a list of documents (or, in the case of looking at a View, then whatever the map script outputs, but in an unformatted form, not prettified like Fauxton). Futon is more compact & developer friendly, even if to a non-dev, such views might look like a jumble of unformatted text. At very least, some kind of “classic mode” switch would be greatly welcomed, at least by us :-)
>
> Please note that it’s been awhile since I’ve looked at CouchDB 2.x, and the issue I brought up above might well have been addressed by someone in the meantime, so apologies if I’m dredging up old/non-relevant stuff (in which case we’ll happily jump onto 2.x!)
>
>
> On 5 July 2018 at 09:21:37, Andrea Brancatelli (abrancatelli@schema31.it) wrote:
>
> Well, mine is the lack for a working FreeBSD port for CouchDB 2.x...
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218844
>
> 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 <wo...@apache.org> 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
Re: Call for "Must-fix" issues
Posted by Kai Griffin <ka...@resourceandrevenue.com>.
As developers who spend a lot of time in the CouchDB web interface, we have held back moving to CouchDB 2.x only because of the change from Futon to Fauxton. We feel that Fauxton simply does not meet the needs of developers as well as Futon did. It seems to be targeted more at non-devs: it’s very friendly-looking, modern & pretty, but is biased towards prettifying document JSON, at the expense of being able to scan through many unformatted documents, which Futon does by default.
So, mainly comes down to the inability to properly see the contents of documents without opening up documents individually. We like to see the whole, unformatted document when viewing a list of documents (or, in the case of looking at a View, then whatever the map script outputs, but in an unformatted form, not prettified like Fauxton). Futon is more compact & developer friendly, even if to a non-dev, such views might look like a jumble of unformatted text. At very least, some kind of “classic mode” switch would be greatly welcomed, at least by us :-)
Please note that it’s been awhile since I’ve looked at CouchDB 2.x, and the issue I brought up above might well have been addressed by someone in the meantime, so apologies if I’m dredging up old/non-relevant stuff (in which case we’ll happily jump onto 2.x!)
On 5 July 2018 at 09:21:37, Andrea Brancatelli (abrancatelli@schema31.it) wrote:
Well, mine is the lack for a working FreeBSD port for CouchDB 2.x...
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218844
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 <wo...@apache.org> 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
Re: Call for "Must-fix" issues
Posted by Kai Griffin <ka...@resourceandrevenue.com>.
As developers who spend a lot of time in the CouchDB web interface, we have held back moving to CouchDB 2.x only because of the change from Futon to Fauxton. We feel that Fauxton simply does not meet the needs of developers as well as Futon did. It seems to be targeted more at non-devs: it’s very friendly-looking, modern & pretty, but is biased towards prettifying document JSON, at the expense of being able to scan through many unformatted documents, which Futon does by default.
So, mainly comes down to the inability to properly see the contents of documents without opening up documents individually. We like to see the whole, unformatted document when viewing a list of documents (or, in the case of looking at a View, then whatever the map script outputs, but in an unformatted form, not prettified like Fauxton). Futon is more compact & developer friendly, even if to a non-dev, such views might look like a jumble of unformatted text. At very least, some kind of “classic mode” switch would be greatly welcomed, at least by us :-)
Please note that it’s been awhile since I’ve looked at CouchDB 2.x, and the issue I brought up above might well have been addressed by someone in the meantime, so apologies if I’m dredging up old/non-relevant stuff (in which case we’ll happily jump onto 2.x!)
On 5 July 2018 at 09:21:37, Andrea Brancatelli (abrancatelli@schema31.it) wrote:
Well, mine is the lack for a working FreeBSD port for CouchDB 2.x...
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218844
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 <wo...@apache.org> 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