I would bias towards ecosystem integrations, e.g. a metrics exporter for
Prometheus (I think one is in the works), or a Debezium connector for the
_changes feed (I haven’t seen any movement here). I suppose the Debezium
connector would ideally be part of the Debezium project itself, but that fe
Proposed. Mix and match:
- Any expected behaviors dropped or changed from pre-existing API
versions are available only when API v4 is specified.
- Any existing behaviors, unchanged in couchdb 4, work the same whether
API v4 is specified, or not
- Any new endpoints created in couchd
Thanks for bubbling this thread back up to the top Donat.
I think a “cleaner slate” v4 API has a lot going for it, but if we go that
route without also supporting the v3 API at the same time we’ll be sunk. Python
succeeded in spite of the 2->3 transition, but it was a long and painful road
as
On 2021-03-30 2:35 p.m., Bessenyei Balázs Donát wrote:
>> It'd be like a Python 2 -> 3 transition
>
> I think the simile is spot on.
> But that shouldn't be a problem, it's more like evolution.
>
>> your user base plummet
>
> Looking at [1] and for lack of a better idea for reference [2], the
> It'd be like a Python 2 -> 3 transition
I think the simile is spot on.
But that shouldn't be a problem, it's more like evolution.
> your user base plummet
Looking at [1] and for lack of a better idea for reference [2], the
user base issues are not obvious to me.
Having said that, I'm okay wit
On 30/03/2021 12:57, Bessenyei Balázs Donát wrote:
> If we are bumping major anyways, can we just go "clean slate" and
> promise replication compatibility only?
Basically: watch your user base plummet. It'd be like a Python 2 -> 3
transition, or a Perl 5 -> 6 one. It would take years of concert
If we are bumping major anyways, can we just go "clean slate" and
promise replication compatibility only?
All that while we'd publish a migration guide that explains the
differences and helps users adjust their implementations, but this way
we'd get rid of some potential complexity.
If we do want
Wow, I didn't realize we are that far into the timeline.
I actually don't have a well-scoped idea for GSoC this year.
Does anyone have good candidates for a project?
Donat
On Mon, Mar 29, 2021 at 6:23 PM Joan Touzet wrote:
>
> https://community.apache.org/gsoc.html might be of help.
>
> If you
