Re: [DISCUSSION] Rename 3.x branch to main and include docs in the main repo

On 6/2/22 21:40, Nick Vatamaniuc wrote: 2. Move docs to the main repo. We noticed that the docs repo tags/branches can get out-of-sync with the main couchdb repo. We have been merging features in main when they apply only to 3.2.x and it requires care to keep track of what gets merged and

Re: [DISCUSS] Deprecate custom reduce functions

good demand for custom functions, and it is annoying for users to have to enable it, we could revert it back to enabled by default or like it was discussed, or, try to add more built-in reducers. Cheers, -Nick On Tue, Oct 13, 2020 at 3:38 PM Jonathan Hall wrote: So looking through the code

Re: [DISCUSS] Deprecate custom reduce functions

]); } reduce: _sum this will sum each of the fields and return a 3-item array. On 13 Oct 2020, at 20:37, Jonathan Hall wrote: So looking through the code that uses this, it looks like the main use I've had for custom reduce functions is summing multiple values at once. A rough equivalent

Re: [DISCUSS] Deprecate custom reduce functions

referring to, the javascript reduce function. I'm curious what you do with custom reduce that isn't covered by the built-in reduces? I also think if custom reduce was disabled by default that we would be motivated to expand this set of built-in reduce functions. B. On 13 Oct 2020, at 17:06, Jonathan

Re: [DISCUSS] Deprecate custom reduce functions

To be clear, by "custom reduce functions" you mean this (https://docs.couchdb.org/en/stable/ddocs/ddocs.html#reduce-and-rereduce-functions)? So by default, only built-in reduce functions could be used (https://docs.couchdb.org/en/stable/ddocs/ddocs.html#built-in-reduce-functions)? If my

Re: [DISCUSS] Creating new deleted documents in CouchDB 4

ity. Its not a significant amount of work to >implement the behavior and we can always deprecate it in the future to >remove the weird edge case of "document that has never existed can be >created in a deleted state". > >On Tue, Sep 1, 2020 at 3:26 PM Jonathan Hall wrote: &g

Re: [DISCUSS] Creating new deleted documents in CouchDB 4

Isn't compatibility required to support replication of deleted documents? Or does creation of a deleted document work with new_edits=false? On Sep 1, 2020, 10:16 PM, at 10:16 PM, Nick Vatamaniuc wrote: >Hi everyone, > >While running PouchDB replication unit tests against the CouchDB 4

Re: [PROPOSAL] Future security announcement policy

An alternative, if we think this is somehow too revealing, would be to include a generic "This may contain security-related fixes" blurb in _every_ release announcement, to serve as a constant reminder that upgrading to the latest patch version is always wise. That said, I'm in favor of the

Re: [VOTE]: Deprecate _update Endpoint

+1 On 5/6/20 1:57 PM, Jan Lehnardt wrote: Hey all, it appears we missed an item in our 3.0 deprecations list and we should clear this up. We have as of yet failed to capture consensus here about the deprecation of the _update endpoint. I think we *have* consensus here, but we didn’t make it

Re: _all_docs collation

Would changing _all_docs, but keeping raw collation as an option, really simplify anything anyway? Or are you proposing removing the raw collation option entirely? Or maybe you're proposing this more as a UX change, than a technical simplification? Jonathan On 3/26/20 11:18 AM, Garren

Re: [ANNOUNCE] Jonathan Hall joins the PMC

Thanks everyone for the warm (re)welcome! Jonathan On 2/10/20 3:57 PM, Joan Touzet wrote: Dear community, I am delighted to announce that Jonathan Hall joins the Apache CouchDB Project Management Committee today. Jonathan has made outstanding, sustained contributions to the project

Re: CouchDB and future

Does the number and type of disks affect the ideal q value? On spinning disks, I might imagine a performance gain by putting each shard on a separate spindle, in which case the ideal performance might be something like q = # of cores = # of spindles. (Although I don't believe it's trivial to

Re: [PROPOSAL] Disable auto-renew of _session cookies

The behavior you request is actually the default behavior. I ran into this when I was expressly seeking the behavior you're trying to disable, and made a feature request, only to learn that it is indeed configurable. See this issue: https://github.com/apache/couchdb/issues/1598 In short, I

Re: [VOTE] Release Apache CouchDB 2.1.1-RC1

As I just noted in this GitHub Issue ( https://github.com/apache/couchdb-documentation/issues/181 ), the docs for the new max_document_size behavior are in a state of minor disarray.  If another 2.1.1-rc is rolled, I'd like to get those docs updated first. If anyone can help answer the

Re: CouchDB 2.1.0 Docker image

There is an issue tracking this: https://github.com/apache/couchdb-docker/issues/23 TL;DR; It's on the way, but no definite time frame. Volunteers no doubt welcome :) -- Jonathan On 08/22/2017 04:04 PM, Carlos Alonso wrote: Hi all. First of all many thanks and congratulations everyone

Re: [DISCUSSION] Moving CouchDB off of Facebook React

One other random thought. It's admittedly ugly, but I think worth bringing up just the same: What effort would be involved in making the old Futon interface usable in CouchDB 2, possibly even without exposing all the features? Would that be less effort/faster than porting Fauxton? I know

Re: [DISCUSSION] Moving CouchDB off of Facebook React

Has an effort been made, or otherwise ruled out, at contacting the authors/publishers of the other React libraries in use, to see if a re-licensing or dual-licensing favorable to the ASF might be negotiated? On August 19, 2017 12:50:42 PM GMT+02:00, Jan Lehnardt wrote:

CouchDB 2.1.0rc1 Docker image anywhere?

Is there a Docker image (or instructions to build one) available for CouchDB 2.1.0rc1? If not, any ETA on when it might be?

Re: 2.1

I tend to agree with the sentiment expressed here. If failing tests are disabled, I have to wonder about the value of the tests in the first place. On May 21, 2017 4:17:47 AM GMT+02:00, "Eli Stevens (Gmail)" wrote: >Please take this as a single data point from an end

Re: [ANNOUNCE] Jonathan Hall elected as CouchDB committer

Thanks everyone for the warm welcome! On 05/09/2017 11:34 PM, Michelle Phung wrote: Yay congrats! - Michelle On May 9, 2017, at 4:54 PM, Joan Touzet <woh...@apache.org> wrote: Dear community, I am pleased to announce that the CouchDB Project Management Committee has elected Jonatha

CouchDB Documentation guidelines

In the last month I've been reading through a lot of CouchDB documentation, as I'm writing a CouchDB Client API library. As such, I've had a lot of opportunity to submit documentation update PRs. But I find myself wishing for greater guidance than can be found simply by reading the existing