Hi everyone,
Debian and RPM 3.3.3 packages were rebuilt and updated with the Erlang
version 24.3.4.15. That version fixes a memory leak
https://github.com/erlang/otp/issues/7834
There were no other CouchDB source changes. The updated deb package
has version 3.3.3-1 and the rpm one has version
Dear community,
The vote has now closed.
The results are:
+1 - 4 votes
+0 - votes
-0 - votes
-1 - votes
The vote passes.
Thank you to everyone who participated!
-Nick
se: ok
>
> env:
> - macOS/x86_64 14.1.1, Erlang 24.3.4.14, Elixir 1.15.7, Python 3.11.6,
> SpiderMonkey 91
> - macOS/x86_64 14.1.1, Erlang 25.3.2.7, Elixir 1.15.7, Python 3.11.6,
> SpiderMonkey 91
>
> Thanks for preparing the release!
>
>
> Jiahui Li (Jessica
Dear community,
I would like to propose that we release Apache CouchDB 3.3.3.
Candidate release notes:
https://github.com/apache/couchdb/blob/3.3.x/src/docs/src/whatsnew/3.3.rst
We encourage the whole community to download and test these release
artefacts so that any critical issues can be
Congratulations, Jessica!
On Thu, Aug 24, 2023 at 2:03 PM Ronny Berndt wrote:
>
> Dear community,
>
> I am pleased to announce that the CouchDB Project Management Committee has
> elected Jiahui Li as a CouchDB committer.
>
> Apache ID: jiahuili430
>
> Slack nick: Jessica Li
>
>
Welcome and congratulations, Gábor!
On Thu, Aug 24, 2023 at 1:58 PM Ronny Berndt wrote:
>
> Dear community,
>
> I am pleased to announce that the CouchDB Project Management Committee has
> elected Gábor Páli as a CouchDB committer.
>
> Apache ID: pgj
>
> Slack nick: pgj
>
> Committers
Looks great, and a nice way to use the Erlang diskmon functionality.
Would it make sense to allow writes which delete data to allow users
to recover some space. Technically it could be a "deleted" update with
a large body, but in most cases users would not do that and would
actually delete data.
Sunday would work. Thanks, Gavin!
Cheers,
-Nick
On Thu, Jun 1, 2023 at 2:23 AM Gavin McDonald wrote:
>
> Hi All,
>
> I would like to schedule downtime to upgrade Jenkins on ci-couchdb.a.o and
> to also update OS packages and do a reboot.
>
> Would Sunday at around 10am UTC be ok for that?
>
>
What do we think about moving to Erlang 24 as our minimum supported version?
24 has been the base version of our package releases for a while, and
we've also been running it at Cloudant for more than 6 months now
without any issues.
Besides speedier JIT, there are some handy-dandy maps
Dear community,
The vote has now closed.
Thank you to everyone who participated!
The results are:
+1 - 3 votes
+0 - 0 votes
-0 - 0 votes
-1 - 0 votes
The vote for 3.3.2 release passed.
Thank you,
-Nick
Dear community,
The vote has now closed.
Thank you to everyone who participated!
The results are:
+1 - 3 votes
+0 - 0 votes
-0 - 0 votes
-1 - 0 votes
The vote for 3.2.3 release passed.
Thanks,
-Nick
+1
Signature: ok
Checksums: match.
make check: pass
make release, fauxton "verify installation": works
env: macos x86_64, python 3.8.16, erlang 23.3.4.18, elixir 1.12.3
Thanks,
-Nick
On Sun, Apr 16, 2023 at 4:14 AM Nick Vatamaniuc wrote:
>
> Dear community,
>
> I would l
uot;: works
env: macos x86_64, python 3.10.7, erlang 24.3.4.9, elixir 1.13.4
Cheers,
-Nick
On Sun, Apr 16, 2023 at 4:06 AM Nick Vatamaniuc wrote:
>
> Dear community,
>
> I would like to propose that we release Apache CouchDB 3.3.0.
>
> Candidate release notes:
> https://github.com/
Dear community,
I would like to propose that we release Apache CouchDB 3.2.3.
Candidate release notes:
https://github.com/apache/couchdb/blob/3.2.3-docs/src/docs/src/whatsnew/3.2.rst
We encourage the whole community to download and test these release
artefacts so that any critical issues can be
Dear community,
I would like to propose that we release Apache CouchDB 3.3.0.
Candidate release notes:
https://github.com/apache/couchdb/blob/3.3.x/src/docs/src/whatsnew/3.3.rst
We encourage the whole community to download and test these release
artefacts so that any critical issues can be
in their ability to provide
oversight for the project.
Everybody, please join me in congratulating Ronny!
On behalf of the CouchDB PMC,
-Nick Vatamaniuc
That looks like a nice improvement, Mike. Thanks for making the RFC.
> One question I had on this is whether RFCs should be frozen once approved, or
> whether I should look to keep it up to date with changes in the code? The
> Bylaws don't really cover whether they are living documents or
+1
MacOS, x86-64, Erlang 23
sig: ok
checksums: ok
make check: ok
make release: ok
fauxton verify: ok
multiple fauxton replication working: ok
Cheers,
-Nick
On Fri, Jan 6, 2023 at 10:34 AM Jan Lehnardt wrote:
>
> Convenience macOS binaries are up for arm64 and x86_64:
>
>
Thanks for making the RC, Jan.
The signature, checksums and make check passed. However, I was playing
with Fauxton, creating multiple replications and noticed all except
one were starting but then not making progress. So I think we'll have
to -1 to include the
Dear community,
The vote has now closed with a passing result.
Thank you to everyone who participated. We got a total of 7 +1 votes,
including 3 +1 PMC votes, which officially makes this a passing vote.
Thank you,
-Nick
My own vote: +1
Ubuntu 22.04, x86-64, Erlang 23
Sig: ok
Checksums: ok
make check: pass
make release: works
Fauxton "Verify Installation": pass
I think we need one more PMC member +1 vote to make it official.
Thanks,
-Nick
On Fri, Dec 23, 2022 at 2:07 PM Nick Vatamaniuc wrote:
10 Pro / Version 22H2 / OS build 19045.2364
> > Erlang 24.3.4.6
> > Elixir 1.13.4
> > Spidermonkey 91
> >
> > sig: ok
> > checksums: ok
> > make check: ok (1 test fail at first run, see below)
> > make release: ok
> > build msi: ok
> > f
Dear community,
I would like to propose that we release Apache CouchDB 3.3.0.
Candidate release notes:
https://docs.couchdb.org/en/latest/whatsnew/3.3.html
Changes since RC1:
https://github.com/apache/couchdb/compare/3.3.0-RC1...3.3.0-RC2
We encourage the whole community to download and test
>
> PR here: https://github.com/apache/couchdb/pull/4320
>
> * * *
>
> Best
> Jan
> —
>
>
> > Johannes
> >
> >
> > --- Original Message ---
> > On Saturday, December 17th, 2022 at 07:04, Nick Vatamaniuc
> > wrote:
> >
> >
> >>
&
My own +1
Sig: ok
Checksums: ok
make check: passes
make release: works
Fauxton verify install: works
Creating database and docs in Fauxton: works
Tested on macos 12, x86-64, erlang 23, spidermonkey 1.8.5
Cheers,
-Nick
On Sat, Dec 17, 2022 at 12:16 AM Nick Vatamaniuc wrote:
>
> Dear com
Dear community,
I would like to propose that we release Apache CouchDB 3.3.0.
Candidate release notes:
https://docs.couchdb.org/en/latest/whatsnew/3.3.html
We encourage the whole community to download and test these release
artefacts so that any critical issues can be resolved before the
Dear community,
This is advance notice that we plan to do a 3.3 release this month.
Please use this time to review any outstanding changes to be made,
merging them in as necessary. The current list of changes we expect to
land for this release is here:
d
> b64url as good candidates
>
>
> vatamane
> 00:01 Uhr b64url is also being replaced by the otp base64 url + an
> urlsafe alphabet too, there is a good chance users would just pick that
>
> https://github.com/erlang/otp/commit/05e6
Apache CouchDB:
> https://neighbourhood.ie/couchdb-support/
>
> 24/7 Observation for your CouchDB Instances:
> https://opservatory.app
>
> > On 28. Sep 2022, at 21:32, Nick Vatamaniuc wrote:
> >
> > Hi everyone,
> >
> > What do we think about integrating couchdb-conf
Hi everyone,
What do we think about integrating couchdb-config into the main couchdb repo?
Currently it's a separate repo, with a different CI (Travis), which
takes quite a bit of time waiting to schedule runs, has a different
configuration file etc. Any updates to config needs a new tag and a
Hi everyone,
Just a quick announcement that CouchDB docs are now part of the main
CouchDB repo in src/docs as discussed in
https://lists.apache.org/thread/x4lc6vhthj1vkt2xpd0ox5osh959qsc4. The
other major change was upgrading to the latest Shinx 5.1.1 package.
The two relevant PRs are:
*
Thanks for sharing, Zach
I gave it a try and it worked as advertised.
Found that clicking on the "fringe" next to the code line
automatically sets a breakpoint so it doesn't need a manual M-x
dap-breakpoint-add!
Cheers,
-Nick
On Thu, Sep 1, 2022 at 9:36 PM Zach Lankton wrote:
>
> Hello Team,
If RCPs have all the functionality of RCNs, I think it makes sense to
deprecate RCNs.
On Tue, Aug 30, 2022 at 9:02 AM Ronny Berndt wrote:
>
> Overview
>
> In a JWT token it is possible to add an attribute for role claims.
> If the roles are presented as top-level attribute like
>
> {
>
Hi everyone,
I implemented _bulk_get support for the replicator in
https://github.com/apache/couchdb/pull/4144. I tried to make it as
backwards compatible as possible to replicate with older endpoints and
PouchDB. Some preliminary benchmarks showed a decent speedup of 30% or
so.
There is a silly
Hello everyone,
I'd like to propose making Erlang 23 the minimum supported Erlang
distribution. We have accumulated a lot of ifdefs and other cruft
supporting various APIs and syntactic constructs since Erlang 20. With
Erlang 25 just released it could be a good time to do some cleanup.
We could
) Replaced old 3.x branch with a single readme marker file
If you have any PRs against 3.x, rebase them on top of main
If you have any PRs against main, rebase them on top of fdbmain
Cheers,
-Nick
On Mon, Jun 6, 2022 at 12:07 PM Nick Vatamaniuc wrote:
>
> > I would like to suggest that w
quickly and skip the whole code
CI. This would be for pull requests CI only. The full CI, which runs
after the merge to main, already runs docs + fauxton + CI builds
anyway.
Regards,
-Nick
On Sat, Jun 4, 2022 at 2:07 PM Nick Vatamaniuc wrote:
>
> Looking at https://docs.readthedocs.io/e
lds, that might not be worth the hassle, but I’m also not stopping anyone
> from putting in the work :)
>
> [1]: ridiculously long name chosen to avoid getting distracted with
> bikeshedding.
>
> Best
> Jan
> —
> Professional Support for Apache CouchDB:
> https://neig
). Then, eventually, the trend
went back to having a single repo.
Regards,
-Nick
On Fri, Jun 3, 2022 at 8:04 AM Jonathan Hall wrote:
>
> On 6/2/22 21:40, Nick Vatamaniuc wrote:
>
> > 2. Move docs to the main repo.
> >
> > We noticed that the docs repo tags/b
Hi everyone,
In a #dev slack thread we were discussing improvements to how we tag
our documentation repo. There were two proposals to simplify the
development and release process, and we wanted to see what the rest of
the community thought about it. Those two ideas are:
1. Rename couchdb repo's
Congratulations, Ronny.
Welcome aboard!
On Fri, Apr 8, 2022 at 3:37 AM Jan Lehnardt wrote:
>
> Dear community,
>
> I am pleased to announce that the CouchDB Project Management Committee has
> elected Ronny Berndt as a CouchDB committer.
>
> Apache ID: ronny
>
> Slack nick: big-r
>
>
ho participated in the discussion! Let's continue
the review in the PR comments
Cheers,
-Nick
On Tue, Jan 25, 2022 at 10:15 AM Nick Vatamaniuc wrote:
>
> Good idea, Will, to return the current collator version in the
> `/_node/_local/_versions` output. We return the collation algori
to make it easier to check if dbs are
> going to be rebuilt after an update. Of course there are also other
> ways for an admin to examine the current runtime and workout versions
> so it is probably a question of how frequently it will come up.
>
> Thanks,
> Will
>
> A
thought
about it:
https://github.com/apache/couchdb/pull/3889#issuecomment-1020861208
Thanks,
-Nick
On Tue, Jan 11, 2022 at 1:06 PM Nick Vatamaniuc wrote:
>
> I threw together a draft PR https://github.com/apache/couchdb/pull/3889
>
> Would that work? There are two tricks there - re-u
e
> that could break this dependency chain and be able to disable intl and
> know what to do explicitly when icu really should be used. That would
> also make it easier to replace spidermonkey with a more minimalist JS
> interpreter.
>
> -Will
>
> Am Do., 13. Jan. 2022 um 17:38 Uhr
ry server, but I've never
> > seen instructions to set locales in relation the query server or do
> > anything to ensure a function is using the root collator, so I don't
> > think the build setup reflects an actual need for spidermonkey to be
> > truly in sync on aspects
ning in the erlang/nifs?
> Thanks,
> -Will
>
> Am Di., 11. Jan. 2022 um 19:06 Uhr schrieb Nick Vatamaniuc
> :
> >
> > I threw together a draft PR https://github.com/apache/couchdb/pull/3889
> >
> > Would that work? There are two tricks there - re-using a f
uld allow adding extra info to the views in the future
(custom collation tailorings?).
Thanks,
-Nick
On Sat, Nov 20, 2021 at 12:32 PM Nick Vatamaniuc wrote:
>
> Thanks, Adam. And thanks for the tip about the view header, Bob.
>
> Wonder if a disk version would make sense for views. N
Option 1 sounds good - picking a variety of OS and packaged SM
versions. For 91 we may have to add a new OS into the mix - Fedora 35.
I saw it was the only distro packaging mozjs91
(https://pkgs.org/search/?q=mozjs91)
-Nick
On Fri, Nov 26, 2021 at 12:38 PM Adam Kocoloski wrote:
>
> I see a
miliarity
> with rebar3 recently, and figured there would be a fair amount of common work
> involved in aligning our build system to either modern option.
>
> Cheers, Adam
>
> > On Nov 24, 2021, at 2:07 PM, Nick Vatamaniuc wrote:
> >
> > Good idea to try rebar3! I t
Good idea to try rebar3! I tried it a few years back and got stumped
at building some NIFs and a few other issues. Most of those can be
overcome with a bit of work.
I saw you used the pc compiler for NIFs, and I think rebar3 can set
overrides now too
) as there
> > is no version number in the header for them. You’d need to add it.
> >
> > B.
> >
> >> On 18 Nov 2021, at 07:12, Nick Vatamaniuc wrote:
> >>
> >> Thinking more about this issue I wonder if we can avoid resetting and
> >> rebuilding
ing exceptions and
applied them to 3.x, one was in couch_debug and one in chttpd module.
Thanks,
-Nick
On Thu, Nov 18, 2021 at 11:50 AM Nick Vatamaniuc wrote:
>
> Hi Jay,
>
> I don't really agree with many of the choices erlfmt makes either. I
> personally like emilio's [1] s
eal for the purpose of
> backporting/diffing, or do you feel it's necessary to reformat everything
> at once?
>
> Thanks,
> Jay
>
> On Wed, Nov 17, 2021 at 11:24 PM Nick Vatamaniuc wrote:
>
> > Hi all,
> >
> > I had noticed we had agreed to use erlfmt but onl
Hi all,
I had noticed we had agreed to use erlfmt but only ran it on main and
not 3.x. That makes it harder to port changes or diff-ing modules
sometimes. Would there be any objections to a pull request
reformatting 3.x?
The only issue is that we may have to avoid running erlfmt if we
detect
2021 at 7:01 PM Nick Vatamaniuc wrote:
>
> Hello everyone,
>
> CouchDB by default uses the libicu library to sort its view rows.
> When views are built, we do not record or track the version of the
> collation algorithm. The issue is that the ICU library may modify the
> colla
Nicely done, Adam!
+1 for most of the PR except one. Perhaps there is a way to push the
CI image to the couchdbdev account instead of your personal one.
As for voting for making these proper releases, I am not really
looking forward to the SVN pushes, signing, checksumming, and
collecting votes
9bbdb6ef2c51a50d1e2326fc1d5b
> >
> > Any questions, feel free to send me a note offlist.
> >
> > Cheers,
> > Joan "too busy for a pithy quote" Touzet
> >
> > On 02/11/2021 22:00, Nick Vatamaniuc wrote:
> >> Dear community,
> >> I would lik
e, checksums, `make check`, fauxton: all good
>
> macOS 11.6.1, OTP 23.3.4.8, SpiderMonkey 60
>
> Small nit on release notes:
> > there are less corner cases
> s/less/fewer/
>
> Very nice work, Nick!
>
>
> On Tue, Nov 2, 2021 at 7:00 PM Nick Vatamaniuc wrote:
>
My own vote: +1
sig: ok
checksums: ok
make check: ok
Fauxton self-check: ok
Ubuntu 20.04, Erlang 23, Spidermonkey 68
Cheers,
-Nick
On Tue, Nov 2, 2021 at 10:00 PM Nick Vatamaniuc wrote:
>
> Dear community,
>
> I would like to propose that we release Apache CouchDB 3.2.1
>
>
Dear community,
I would like to propose that we release Apache CouchDB 3.2.1
Candidate release notes:
https://docs.couchdb.org/en/latest/whatsnew/3.2.html#version-3-2-1
We encourage the whole community to download and test these release
artefacts so that any critical issues can be resolved
Hello everyone,
CouchDB by default uses the libicu library to sort its view rows.
When views are built, we do not record or track the version of the
collation algorithm. The issue is that the ICU library may modify the
collation order between major libicu versions, and when that happens,
views
Good idea, Adam. Some of those are pretty nice applications.
Technically there are difficulties around rebar3 compatibility for
NIFs. It might be easier to make them developer friendly after we
switched the whole CouchDB project to rebar3. The non-NIF apps can be
used already as source
gt; 163.)\n"],#{error_logger=>#{emulator=>true,tag=>error},gl=><0.0.0>,pid=><0.22.0>,time=>1633523875486343}}
>
>
> that can only be stopped with `kill -9 `
>
>
>
> > On 5. Oct 2021, at 21:30, Nick Vatamaniuc wrote:
&g
duler"],"vendor":{"name":"The
> Apache Software Foundation"}}
>
> git_sha matches the last checkin by nickva to bump the docs for 3.2.0-RC2.
>
> Fauxton Verify Installation button comes back with all checkmarks.
>
> +1 - and good work everyone!
>
&
Dear community,
I would like to propose that we release Apache CouchDB 3.2.0.
Candidate release notes:
https://docs.couchdb.org/en/latest/whatsnew/3.2.html
This is the RC2 round. Changes since last round:
https://github.com/apache/couchdb/compare/3.2.0-RC1...3.2.0-RC2
We encourage the
Thank you, all!
It looks like the vote passed and this will become the 3.1.2 release.
-Nick
On Tue, Sep 28, 2021 at 7:41 PM Joan Touzet wrote:
>
> On 28/09/2021 10:53, Nick Vatamaniuc wrote:
> > Thanks for taking a look, Joan
> >
> > I just highlighted th
/test/eunit/couch_prometheus_e2e_tests.erl#L109
-Nick
On Wed, Sep 29, 2021 at 11:45 AM Dave Cottlehuber wrote:
>
> On Mon, 27 Sep 2021, at 22:59, Nick Vatamaniuc wrote:
> > Dear community,
> >
> > I would like to propose that we release Apache CouchDB 3.2.0.
> &g
and Cloudant Sync for
> > Android test suites.
> >
> > Thanks!!
> >
> >
> > El mar, 28 sept 2021 a las 1:00, Nick Vatamaniuc ()
> > escribió:
> >
> >> Dear community,
> >>
> >> I would like to propose that we release Apache
t diff shows documentation only. Something seems wrong with
> this release.
>
> Recommend we hold the vote until this can be cleared up?
>
> -Joan
>
> On 27/09/2021 08:53, Nick Vatamaniuc wrote:
> > Dear community,
> >
> > I would like to propose that we relea
Dear community,
I would like to propose that we release Apache CouchDB 3.2.0.
Candidate release notes:
https://docs.couchdb.org/en/latest/whatsnew/3.2.html
We encourage the whole community to download and test these release
artefacts so that any critical issues can be resolved before the
My own vote:
Signature: Ok
Checksums: Ok
Tests (make check): Pass
+1
On Mon, Sep 27, 2021 at 8:53 AM Nick Vatamaniuc wrote:
>
> Dear community,
>
> I would like to propose that we release Apache CouchDB 3.1.2
>
> Changes since 3.1.1
>
>
> https://github.com/a
Dear community,
I would like to propose that we release Apache CouchDB 3.1.2
Changes since 3.1.1
https://github.com/apache/couchdb-documentation/compare/3.1.1...3.1.x?expand=1
This is a minor release where we backport a few features from the
pending 3.2 release to the 3.1.x branch.
We
Hi Farhan,
You can configure time windows during which compaction would take
place. See
https://docs.couchdb.org/en/stable/maintenance/compaction.html#scheduling-windows
Cheers,
-Nick
On Thu, Aug 12, 2021 at 5:05 AM Farhan Faiz wrote:
>
> Hi,
>
> I want to know when does Compaction occurs by
Good idea, Donát! Thanks for giving it a try.
Even though I personally think emilio has a better style, and I don't
agree with some of the choices erlfmt makes, I still think it would
still be a net benefit to having consistency if we get automated code
reformatting. So +1 overall.
If there are
lutely all the obsoleted, unreachable code as soon
> > as possible, then once the dust has settled we can see if there are obvious
> > gaps we should fill in before the 4.0 release.
> >
> > B.
> >
> > > On 12 Apr 2021, at 18:51, Nick Vatamaniuc wrote:
&g
th one major reservation:
>
> On 12/04/2021 12:25, Nick Vatamaniuc wrote:
> > * Some applications we want to have in main, but the way they are
> > implemented currently rely completely or mostly on 3.x code: purge
> > logic, couch_peruser, global_changes, setup. I am thinking
Hi all,
Currently we have a bunch of 3.x applications in the main branch which
are not functional. Some even start supervisors and expose HTTP
endpoints, like _reshard (mem3). Initially the idea was to keep those
applications there to make it easy to merge fixes back and forth, but
I wonder if it
es). To be applied to active_tasks output also. Defaulting to true for
> compatibility.
>
> > On 5 Apr 2021, at 17:17, Nick Vatamaniuc wrote:
> >
> > The "node" field can be helpful in determining where the background
> > task runs even if nodes are not con
I think that's a good compromise if we want to bring more users along
from 3.x to 4.x.
In respect to existing users I can see there being at least 4
different categories:
1. Users who know about the snapshotting behavior of 1.x-3.x, and
their applications rely on it for correctness.
2. Users who
The "node" field can be helpful in determining where the background
task runs even if nodes are not connected in a mesh. Nodes could still
be named something like replication_node_1, replication_node_2, etc.
Even in 3.x, the replicator doesn't rely on the nodes being meshed all
that much, the jobs
I am +1 to lowering as it's better than infinity.
But I also see Eric's point. I was surprised a while back just like
Eric that I could successfully upload >1GB-sized files. So why not
0.5GB or 2GB? I am thinking 2GB was (is?) a common limit on some OSes
and file systems (FAT32) since they use
I created an RFC based on the discussion above:
https://github.com/apache/couchdb-documentation/pull/617
-Nick
On Sun, Jan 17, 2021 at 12:22 AM Nick Vatamaniuc wrote:
>
> On Fri, Jan 15, 2021 at 6:41 PM Joan Touzet wrote:
> >
> > On 15/01/2021 17:51, Nick Vatamaniuc wrote:&
+1 on dropping Erlang 19
It's been a best-effort support for it anyway, if I remember the last
discussion about it correctly.
I looked at the failure in the CI and it looks like we're failing on
the ceil/1 function in couch_emsort.erl. We already shipped 3.1.1 with
that change and the commit is
On Fri, Jan 15, 2021 at 6:41 PM Joan Touzet wrote:
>
> On 15/01/2021 17:51, Nick Vatamaniuc wrote:> You're absolutely right.
> There are two places where job priority comes
> > into play: one is when jobs are started, and then the other is when
> > they are stopped.
On Thu, Jan 14, 2021 at 4:51 PM Joan Touzet wrote:
>
> On 2021-01-12 12:55 p.m., Nick Vatamaniuc wrote:
> > Hello everyone
>
> Hi (Dr.) Nick! ;)
"One quick application of Spiffy and we got ourselves a better scheduler!"
I had to look up the Simpson reference as I ha
Congrats Donat and welcome!
-Nick
On Thu, Jan 14, 2021 at 3:55 PM Joan Touzet wrote:
>
> Congratulations Bessenyei! Do you have a nickname (other than bessbd)?
>
> -Joan
>
> On 2021-01-14 3:48 p.m., Robert Newson wrote:
> > Dear community,
> >
> > I am pleased to announce that the CouchDB
Hello everyone
I wanted to see what we thought about adding a scheduling improvement
to the replicator. Specifically adding round-robin fairness amongst
different _replicator dbs.
Currently, the scheduler runs all the jobs in the system fairly. It
does it by using the jobs' "last started"
> I withdraw my vote until I can get a clearer view. Nick would you mind
re-stating?
Not at all! The longer version and other considerations was stated in
my last reply to the discussion thread so I assumed that was accepted
as a consensus since nobody replied arguing otherwise.
Disable custom reduce functions by default, but don't deprecate them.
> >
> >
> >
> >> On 13 Oct 2020, at 21:16, Nick Vatamaniuc wrote:
> >>
> >> In case of _sum, like Joan mentioned, we can emit objects or arrays
> >> and the built-in _sum w
nctions by default, but don't deprecate them.
>
>
>
> > On 13 Oct 2020, at 21:16, Nick Vatamaniuc wrote:
> >
> > In case of _sum, like Joan mentioned, we can emit objects or arrays
> > and the built-in _sum will add the values of the fields together:
> >
> > S
In case of _sum, like Joan mentioned, we can emit objects or arrays
and the built-in _sum will add the values of the fields together:
So {"map": 'function(d){ emit(d._id, {"bar":1, "foo":2, "baz":3});
}', "reduce" : '_sum' } for 10 docs would produce {"bar": 10, "baz":
30, "foo": 20}.
As for
That looks great. Good call to archive and remove some of those repositories.
On Wed, Sep 16, 2020 at 11:52 AM Paul Davis wrote:
>
> I'll create the branches on all of the appropriate repositories today
> and start looking at Jenkins requirements. I'll hold off on filing the
> infra ticket until
Environment:
Ubuntu 18.04.5, x86_64
$ asdf current
elixir 1.9.4-otp-22
erlang 22.2.3
$ cat /etc/apt/sources.list.d/couchdb-bintray.list
deb https://apache.bintray.com/couchdb-deb bionic main
Sig: ok
Checksums: ok
Configure, make & make check: ok
Build release, add
Congrats, Glynn!
-Nick
On 9/14/20 10:07 PM, Joan Touzet wrote:
Congratulations Glynn - and welcome!
-Joan
On 2020-09-14 12:22 p.m., Michelle P wrote:
Dear community,
I am delighted to announce that Glynn Bird joins the Apache CouchDB
Project Management Committee today.
Glynn has made
+1
This conversation kind of spilled into the other thread about merging,
so I replied there as well about main vs master and rebasing. Sorry
about the confusion.
On Wed, Sep 9, 2020 at 2:05 PM Robert Samuel Newson wrote:
>
> I'm +1 in favour of renaming to 'main'.
>
>
>
> > On 9 Sep 2020, at
That looks really nice, Jan. Thanks for sharing!
On Wed, Sep 9, 2020 at 1:29 PM Alessio 'Blaster' Biancalana
wrote:
>
> Wow, that's _amazing_. I'm glad seeing this kind of effort in an ecosystem
> like the one of CouchDB, cool stuff!
>
> Alessio
>
> On Wed, Sep 9, 2020 at 6:03 PM Jan Lehnardt
Could we rename prototype/fdb-layer to main and it will be the base of
4.x? There might be a few things we could bring in from master into
main like elixir test improvements, tooling, but it would be a smaller
diff than bringing everything from prototype/fdb-layer into master.
Then master can be
eleted state".
> >>
> >> On Tue, Sep 1, 2020 at 3:26 PM Jonathan Hall wrote:
> >>>
> >>> Isn't compatibility required to support replication of deleted
> >> documents? Or does creation of a deleted document work with
> >> new
Hi everyone,
While running PouchDB replication unit tests against the CouchDB 4
replicator PR branch (thanks to Garren Smith, who helped set up the
tests), we had noticed a doc update API incompatibility between
CouchDB 3.x/PouchDB and the prototype/fdb-layer branch: CouchDB
3.x/PouchDB allow
1 - 100 of 202 matches
Mail list logo
