Re: Missing OpenSSL 3 in CouchDB 3.3.3-2 for MacOS

Thanks for the heads-up. I consider this a bug and will get it fixed shortly. Best Jan — Professional Support for Apache CouchDB: https://neighbourhood.ie/couchdb-support/ 24/7 Observation for your CouchDB Instances: https://opservatory.app SQL Queries for CouchDB:

Re: 3.3.3 packages update

I’ve also uploaded the Mac and Win packages. Thanks to Ronny for providing the Win build. Best Jan — Professional Support for Apache CouchDB: https://neighbourhood.ie/couchdb-support/ 24/7 Observation for your CouchDB Instances: https://opservatory.app SQL Queries for CouchDB:

Re: Older versions for OSX are not available for download

That’s a bug on my end it seems, I’ll get it seen to. Thanks for reporting. Best Jan > On 25. Dec 2023, at 17:59, Miroslav Rodic wrote: > > Hello, > > I’m trying to download CouchDB 3.2.0 for OSX > , but without > success. Only

[ANNOUNCE] Apache CouchDB 3.3.3 released

fline-first user-experience while maintaining high performance and strong reliability. CouchDB comes with a developer-friendly query language, and optionally MapReduce for simple, efficient, and comprehensive data retrieval. On behalf of the CouchDB PMC, Jan Lehnardt —

Introducing Structured Query Server, SQL Queries for CouchDB

Dear CouchDB user community, My company Neighbourhoodie is happy to announce Structured Query Server, a CouchDB companion application that gives you full-fidelity SQL query abilities for your CouchDB installations. See all infos, technical details and benchmarks on our product page:

Re: High CPU at startup and wake

Heya, The last time we fixed something along these lines was in 2019: https://github.com/apache/couchdb/pull/2195/files Which predates 3.1.0: https://blog.couchdb.org/2020/05/06/3-0-1-3-1-0/ Are you 100% sure about your version? A quick look does not suggest we have introduced this pattern

[ANNOUNCE] Apache CouchDB 3.3.2 released

of the configured hash algorithms from chttpd_auth/hash_algorithms to decode authentication tokens - Bump recon to 2.5.3 On behalf of the CouchDB PMC, Jan Lehnardt —

[ANNOUNCE] Apache CouchDB 3.2.3 released

://docs.couchdb.org/en/stable/whatsnew/3.2.html Release Notes highlights: - Fix for CVE-2023-26268, the details of which will be released in 7 days - Improve JavaScript process management - Fix quoting issue with `remsh` On behalf of the CouchDB PMC, Jan Lehnardt —

[ANNOUNCE] CouchDB Berlin User Group Meetup Wednesday March 15 (online)

Hey all, we're happy to invite you to our next online CouchDB Berlin Meetup on March 15th (this week!), 2022, 5:30 PM – 7:00 PM (CET) Talks by Alex Feyerke, Jan Johannes & your’s truly: Talk #1: Type safe access to CouchDB with PouchDB Talk #2: Zero Boilerplate Data Binding for Reactive and

Re: Some random user questions

Heya Vincent, apologies for taking so long to respond :) > On 14. Jan 2023, at 23:08, Vincent van der Leun wrote: > > Hello, > > I am a Dutch user of CouchDB for quite some time. I know I won't make > headlines, given that I only run a single-node CouchDB instance that runs on > a small

[ANNOUNCE] Apache CouchDB 3.3.1 released

. The community would like to thank all contributors for their part in making this release, from the smallest bug report or patch to major contributions in code, design, or marketing, we couldn’t have done it without you! On behalf of the CouchDB PMC, Jan Lehnardt —

Re: [RELEASE] Apache CouchDB 3.3.0 released

ps 3.4.0? Any info on this / timescales if so? > > R > >> On 3 Jan 2023, at 10:42, Jan Lehnardt wrote: >> >> Dear community, >> >> Apache CouchDB® 3.3.0 has been released and is available for download. It is >> a feature release, and was orig

[RELEASE] Apache CouchDB 3.3.0 released

more in-depth discussion see this recording of the November Berlin CouchDB User Group online meetup: https://vi.to/hubs/couchdb-berlin/pages/state-of-the-couch-november-2022-jan-lehnardt-nov-16-2022?v=%2Fvideos%2F5904 (free signup required, no spam) • CouchDB is on Mastodon now: h

[RELEASE] PouchDB 8.0.0

Hey all. PouchDB 8.0.0 has been released: https://fosstodon.org/@pouchdb/109517906610488395 Best Jan — Professional Support for Apache CouchDB: https://neighbourhood.ie/couchdb-support/ *24/7 Observation for your CouchDB Instances: https://opservatory.app

[ANNOUNCE] (Virtual) CouchDB Usergroup Meetup on Wednesday, Nov 16, 5:30 CET)

Heya folks, We are running a @CouchDB u meetup next week (Wed 16th). It’s the Berlin user group organising, but it is entirely virtual. We have three nice talks lined up, you can sign up here for free, anybody is welcome: https://vi.to/hubs/couchdb-berlin Best Jan — Professional Support for

CVE-2022-24706: Apache CouchDB Remote Privilege Escalation

Description === An attacker can access an improperly secured default installation without authenticating and gain admin privileges. 1. CouchDB opens a random network port, bound to all available interfaces in anticipation of clustered operation and/or runtime introspection. A

[ANNOUNCE] Apache CouchDB 3.2.2 released

support for SpiderMonkey 91esr. On behalf of the CouchDB PMC, Jan Lehnardt —

Re: CouchDB 3.1.1 high disk utilization and degradation over time

Professional Support for Apache CouchDB: https://neighbourhood.ie/couchdb-support/ *24/7 Observation for your CouchDB Instances: https://opservatory.app > On 4. Apr 2022, at 18:21, Roberto Iglesias wrote: > > Hello. > > About 1 year ago, we had two CouchDB 2.3.1 instances running inside

Re: Post/Comment DB design: Postgresql v/s CouchDB

Hi Meeka, we don’t generally recommend a per-user database system unless you deal with replication with e.g. PouchDB where each database needs distinct user access. For just a regular blog app, you can use a single database. The CouchDB docs explain just that example in fact. You’ll be working

Re: CouchDB High Availablility deployment and ChangeFeed

Hi A, for your setup, we recommend using CouchDB Clustering to achieve high availability. But note that neither a single node nor a cluster _changes feed guarantees exactly-once-delivery. You have to solve that in your Spring-boot API. Best Jan — Professional Support for Apache CouchDB:

Re: Off-line sync by exchanging .couch files

Oh, and note that for 3.2.0 and CouchApps to work, you will have to change the default CSP headers: https://docs.couchdb.org/en/stable/cve/2021-38295.html / https://github.com/apache/couchdb/pull/3724 Best Jan — Professional Support for Apache CouchDB: https://neighbourhood.ie/couchdb-support/

Re: Off-line sync by exchanging .couch files

Hi Miroslav, that’s a nice application :) You should be able to do the same thing with CouchDB 3.2.0, but you need to do an extra step. In CouchDB 1.x, when opening a a database `foo`, it would open a file at `$database_dir/foo.couch`, very straightforward. In CouchDB 2.x and 3.x, the

Re: Upgrade CouchDB on Mac

You can quit the existing Apache CouchDB app by using the menu bar item and selecting “Quit Apache CouchDB”. Then you can overwritee the application and start it again. No other task required. Best Jan — Professional Support for Apache CouchDB: https://neighbourhood.ie/couchdb-support/ 24/7

[RELEASE] CouchDB 3.2.0

Dear community, Apache CouchDB 3.2.0 has been released and is available for download. https://couchdb.apache.org/#download * * * CouchDB 3.2.0 is a feature release and was originally published on 2021-10-12. See the official release notes document for an exhaustive list of all changes:

[RELEASE] CouchDB 3.1.2

Dear CouchDB community, Apache CouchDB® 3.1.2 has been released and is available for download. CouchDB 3.1.2 is a security release for a low severity security issue, and was originally published on 2021-10-05. Details for the security issue will be published one week after this release. See

Re: Per subdomain DBs with Node

e instances are created in the same module that all other modules then use to get their instances from that one central module, so the “cache” can be module-global for us. Maybe that pattern also works for you. I hear people have strong opinions about global variables. Best Jan — > > Than

Re: Per subdomain DBs with Node

Hi Rick, your original implementation strikes me as better than the other one. Since storing something in Redis means serialising it, you won’t get the benefit of any sockets being kept open, and I’m not even sure you can make that work properly. If you are worried about having a db instance

Re: Proxying document updates with update handlers

Hi Aurélien, we generally recommend doing this kind of stuff outside of CouchDB, these days. A Node.js proxy that does this completely and reliably is maybe 50 lines of code and not a huge operational overhead, while granted not as neat as doing all this inside of CouchDB. As for getting the

Re: Changes to 'this' in update function are visible in validate_doc_update. Bug or Feature?

Hi Stefan, you absolutely should and can not rely on this behaviour, it might even not be available in setups with other (more modern) JS interpreters. Best Jan — Professional Support for Apache CouchDB: https://neighbourhood.ie/couchdb-support/ 24/7 Observation for your CouchDB Instances:

Re: Data backup in CouchDB cluster

Hi Simon, there are multiple aspects to backup, data safety and time to recovery (TTR). If your only goal is to have a separate copy of your data, backing up only one node of your database does the trick. However, if you want a short TTR, so your cluster is complete again as soon as possible,

Re: New CouchDB CLI tool

Heya Jonathan, this is really cool, congrats on getting this together! And thank you for sharing :) Best Jan — > On 27. Apr 2021, at 22:25, Jonathan Hall wrote: > > Good day everyone! > > I'd like to announce the "alpha" release of a new CLI tool for interacting > with CouchDB. The tool

Re: Upgrade 2.3.1 on Mac osx

ns > to trash bin and that is it? > > > > -----Original Message- > From: Jan Lehnardt > Sent: 14 April 2021 11:38 > To: user@couchdb.apache.org > Subject: Re: Upgrade 2.3.1 on Mac osx > > The 3.x binary will just load your existing > ~/Library/Preferences/couchdb2-local.ini

Re: Upgrade 2.3.1 on Mac osx

the data 3.1.1 will auto find it or > should I first replicate the data to 3.1.1 prior to decommissioning 2.3.1 > > Regards, > Jonathan > > > > -Original Message- > From: Jan Lehnardt > Sent: 14 April 2021 10:45 > To: user@couchdb.apache.org > Subject

Re: Upgrade 2.3.1 on Mac osx

Hi Jonathan, you can just install 3.1.1 and delete your 2.3.1 app. The 3.1.1 will automatically use your existing data. Note that you can’t just go back, only forward. Best Jan — > On 13. Apr 2021, at 21:48, Jonathan Aquilina > wrote: > > Good Evening, > > I have a quick question how does

Re: Single vs user db's

> On 8. Apr 2021, at 19:53, Olaf Krueger wrote: > > >> Also, I don’t quite get what “re-creating” a database would entail. > > Sorry, it seems to me that doesn't makes sense. > While I wrote this I had the docs in my mind [1]: > >> If your use case creates lots of deleted documents (for

Re: Single vs user db's

> On 8. Apr 2021, at 13:56, Olaf Krueger wrote: > > Hi, > >> ... I will be required to be able to delete all data for a departing >> customer > > Wouldn't it be a valid option to remove all documents which are related to a > particular customer from a single database and (if needed)

Re: Single vs user db's

Hi Sam, > On 8. Apr 2021, at 12:24, Sam Lown wrote: > > - create databases for data which will grow infinitely like calendar > entries or anything that has time as a primary key. Excellent additions, and one more point on this in particular: - database-per-time-unit (say one per month),

Re: Single vs user db's

Hi Kiril, first, this is a good question :) I’d like to add, that you are missing one more approach to consider: use a single database. Let’s first look at the other approaches, and I’ll start with database-per-type: - there is no real benefit of doing this, other than theoretical purity - it

Re: [Eventual consitency] Is the uniqness of the _id guaranteed across nodes within a cluster

Hi Olaf, > On 13. Dec 2020, at 11:13, Olaf Krueger wrote: > > Hi again, > > we're working on a booking app. > In order to prevent over booking of a particular slot (A slot can booked only > once), it's crucial to know if a slot is already booked or even not. > > We're using a cluster of 3

Re: Mulltiple gets on same databases

Hi Paul, this is usually a networking issue, not a CouchDB issue. What OS are you running this on? What are your open file ulimits for the requesting and the CouchDB process? Try running a netstat to see the state of open sockets during the benchmark progress Best Jan — > On 22. Sep 2020,

Announcing Opservatory: 24/7 CouchDB Observation and Analysis

Dear CouchDB Community, I’m happy to announce Opservatory https://opservatory.app, my company Neighbourhoodie’s latest product for monitoring your CouchDB instances. Opservatory knows CouchDB better than any single human could. We’ve put our combined multi-decade experience with supporting

Re: Local-First apps and CouchDB

I came to similar conclusions while reading the JSON CRDT paper by the same author. It closes with essentially “garbage collection is TBD”, which makes it also not feasible in practice for the same reasons ermouth outlines. Best Jan — > On 7. Aug 2020, at 03:08, ermouth wrote: > > Both CRDT

Re: Local-First apps and CouchDB

The author of this sadly has demonstrated multiple times that they don’t understand CouchDB very well, and despite my outreach, wasn’t open to learning any more. I’m not sure if this is a personal choice, or a reflection of few scientific papers existing around CouchDB, but it’s worth noting.

Re: Is this mailing list obsolete now?

> On 12. Jul 2020, at 22:07, Miles Fidelman wrote: > > Well, as a user, I kind of find that the move to a github discussion is not > at all helpful. Email lists are a time-proven mechanism - why break what > ain't broke. This mailing list isn’t going anywhere. Best Jan — > > Miles

Re: Fastest way to get a doc _rev

> it returns the header and the start of the body before its done any actual > work. I'm not 100% sure if that is the case when `key=` is used. You might > have to adjust your benchmark to check for the first `{` to signify the > start of a document. > > Cheers > Garren > &g

Fastest way to get a doc _rev

Hey all, based on a question in our new GitHub Discussion board, I got interested in what is faster: retrieve a doc _rev with a HEAD request or with an _all_docs?key=docid request. The results might be interesting for folks:

Re: Restriction of autocompaction to a time window not working

For posterity, this got resolved here: https://github.com/apache/couchdb/discussions/2997 Best Jan > On 10. Jul 2020, at 20:15, Cluxter wrote: > > Hi everyone > > I am using the official Docker image of CouchDB, v3.1.0. > > I created a couchdb.ini file in which I put my custom CouchDB

Re: Don’t rely on CouchDB’s auto-UUID generation?

Hi Olaf, > On 10. Jul 2020, at 14:03, Olaf Krüger wrote: > > Hi guys, > > before reading the docs I was afraid of creating custom _ids. > But the docs [1] even says that we shouldn't rely on the auto generated UUID. > > Our primary goal is to create more human readable _ids. > So, in order to

Re: couchdb 3.X partitioning

;> rest of the document ID. Replication can’t change document ID, but if the >>>> source database happens to fulfill that requirement for all of its >>>> documents (excluding _design documents), then you could create a >>>> partitioned database on the target

Re: couchdb 3.X partitioning

gt;> pretty unlikely coincidence. >> >> Switching to partitioned databases is unfortunately more likely to require >> an external ETL job. >> >> Adam >> >>> On Jul 7, 2020, at 8:30 AM, Jan Lehnardt wrote: >>> >>> Hi Sharath, >

Re: couchdb 3.X partitioning

Hi Sharath, > On 7. Jul 2020, at 14:17, Sharath wrote: > > Hi, > > Got couchdb 3.1 running and migrated my database (replicated) over. > > Read about partitioning and have the following questions: > > Can a partitioned database be created when replicating from another couchdb > instance? Do

Re: Compaction file still behind main file

On 6. Jul 2020, at 10:26, Alan Malta wrote: > > Dear experts, > > apologies if I'm asking something that has already been asked here, if > so, I'm happy to have just a link to a previous discussion. > > Coming to the problem, over the last week, one of my couch instances > went twice from

Re: X-Content-Type-Options and strict-transport-security

> On 3. Jul 2020, at 08:53, Sebastien wrote: > > Given that CouchDB exposes its functionality over HTTP through a RESTful > API, IMHO it should allow to define such important http headers for > security directly. This is a fair point and a patch/PR to that effect is going to be

Re: Way to disable the management GUI

Hi Darshan, Fauxton, the management GUI is just a web app that uses the CouchDB API that your application uses as well. The way to secure CouchDB is to secure who has access to the API. Whether or not the management GUI is present makes no difference. For example, if you have an CouchDB API

Re: CouchDB and Rust blogs

Congrats Garren, this is really cool! :) One related question: have you pondered embedding a JS engine into Erlang itself as well? Best Jan — > On 24. Jun 2020, at 16:21, Garren Smith wrote: > > Hi All, > > I've been playing around with the rust language quite a bit recently and > using it

Re: Newsfeed IFRAME in Fauxton and IP collection

Thanks ermouth, I’m surprised my proposal made it through without discussion. I have the same question ;D FWIW, this “leaks” the browser connection to the internet, not necessarily CouchDB instance data. For a production version of this, I would at least expect an opt-in button on that page,

Re: Attempting to update legacy view in logs

Hi Milko, there is nothing broken here so there is nothing to fix. CouchDB occasionally updates internal data formats and when that happens, it migrates any existing data from the old format to the new format. That’s what’s happening here and there is nothing to worry about. Best Jan — --

Re: design document with no name

Heya Andrea, Which version of CouchDB is this? Best Jan _ > On 15. Jun 2020, at 14:54, Andrea Brancatelli > wrote: > > Sorry the attachment got lost along the way: > > http://storage.gcloud.schema31.it/obj/9d6870890a00-1608-ae11-70fa-57153e15 > > --- > > Andrea Brancatelli > Schema31

Re: Announcing GitHub Discussions for Apache CouchDB [Beta]

Discussions, which means we can't mirror activity there to our user@ >>>> mailing lists. We've been told this will arrive around the time >>>> Discussions leaves private beta. >>>> >>>> The other: Please remember that all discussion of project *directi

Re: couchdb file corruption

Hi Sharath, the error you are seeing originates in CouchDB’s file checksumming feature[1]. When writing a block of data to disk, in either a database or a view index, CouchDB also stores a checksum of the block. When reading the block later, it checks if the stored checksum and the newly read

Re: Option request for user access to the /_all_dbs endpoint (old behavior)

Hi Erik, there is: https://github.com/apache/couchdb/blob/master/rel/overlay/etc/default.ini#L140-L141 It is also mentioned in the accompanying blog post:

Re: scaling?

> On 24. May 2020, at 17:32, Miles Fidelman wrote: > > Thanks Jan, and a follow-up, below: > > On 5/24/20 4:51 AM, Jan Lehnardt wrote: >> >>> On 23. May 2020, at 18:57, Miles Fidelman >>> wrote: >>> >>> On 5/23/20 12:29 PM, Jan Le

Re: scaling?

> On 23. May 2020, at 18:57, Miles Fidelman wrote: > > On 5/23/20 12:29 PM, Jan Lehnardt wrote: > >> >>> On 23. May 2020, at 16:28, Miles Fidelman >>> wrote: >>> >>> >>> On 5/22/20 11:13 AM, Jan Lehnardt wrote: >

Re: scaling?

> On 23. May 2020, at 16:28, Miles Fidelman wrote: > > > On 5/22/20 11:13 AM, Jan Lehnardt wrote: > >> >>> On 22. May 2020, at 15:06, Miles Fidelman >>> wrote: >>> >>> Hi Jan, >>> >>> On 5/22/20 6:17 AM,

Re: scaling?

> On 22. May 2020, at 15:06, Miles Fidelman wrote: > > Hi Jan, > > On 5/22/20 6:17 AM, Jan Lehnardt wrote: >> Hi Miles, >> >> I wanted to reply for a while, but struggled to find a good angle. I think I >> finally figured out what I missed. I’

Re: scaling?

Hi Miles, I wanted to reply for a while, but struggled to find a good angle. I think I finally figured out what I missed. I’m not sure I understand your deployment scenario. When I think conference app, I think folks having that on their mobile phones, or tablets. Given that, you’d be using

[CVE-2020-1955] Apache CouchDB Remote Privilege Escalation

it enabled can either disable it again, or upgrade to CouchDB versions 3.0.1[1] and 3.1.0[2]. [1]: https://docs.couchdb.org/en/stable/whatsnew/3.0.html#version-3-0-1 [2]: https://docs.couchdb.org/en/stable/whatsnew/3.1.html#version-3-1-0 On behalf of the CouchDB Security Team, Jan Lehnardt —

Re: [External] CouchDB 2.1.1 - Unable to setup replication

FWIW, I filed a quick issue on Fauxton. This would make a nice first contribution for someone :) https://github.com/apache/couchdb-fauxton/issues/1278 Best Jan — > On 16. May 2020, at 10:28, Jan Lehnardt wrote: > > One of the docs in the test is a design document[1], those

Re: [External] Re: CouchDB 2.1.1 - Unable to setup replication

ication check > with an error saying "Replication failed, expected 4 docs got 3". Attached is > the screen shot. > > > Thank You, > Sajan Gone > Senior Database Engineer > LBrands | Mast Global Technologies > Mobile #:517-990-5282 > Office #:   614-5

Re: CouchDB 2.1.1 - Unable to setup replication

Do you mean local as in `dbname` or as in `https://thelocalcluster/dbname`? If it is the former, that just doesn’t work. You need full URLs for source and target. Best Jan — > On 15. May 2020, at 17:28, Gone, Sajan wrote: > > Hi All, > > I am relatively new to CouchDB, we just started

Re: [ANNOUNCE] Apache CouchDB 3.0.1 and 3.1.0 released

> On 6. May 2020, at 20:15, Damjan Georgievski wrote: > > On Wed, 6 May 2020 at 16:40, Robert Samuel Newson wrote: >> >> Make an issue (https://github.com/apache/couchdb/issues) >> >> At first blush, I don't see why not, though I thought there was value in >> Authorization: Bearer from

Re: [Ticket ID: 975818] [ANNOUNCE] Apache CouchDB 3.0.1 and 3.1.0 released

Apparently I didn’t ;D It looks like I’m not a moderator for this list. Can any one of you help? Best Jan — > On 6. May 2020, at 13:05, Jan Lehnardt wrote: > > FYI: I have removed this email address. > >> On 6. May 2020, at 13:03, IdeaStack Support wrote: >> &g

Re: [Ticket ID: 975818] [ANNOUNCE] Apache CouchDB 3.0.1 and 3.1.0 released

> On 6. May 2020, at 14:31, Joel Jucá wrote: > > QQ: it mentions support for Java Web Tokens, but what I understand of JWT > is that it means JSON Web Tokens. Is it a typo or I'm confusing two > conflicting acronyms? It’s a running gag :) Best Jan — > > On Wed, May 6

Re: [Ticket ID: 975818] Re: [ANNOUNCE] Apache CouchDB 3.0.1 and 3.1.0 released

FYI: I have removed this email address. > On 6. May 2020, at 13:03, IdeaStack Support wrote: > > user@couchdb.apache.org, > > Thank you for contacting our support team. A support ticket has now been > opened for your request. You will be notified when a response is made by > email. The

Re: [ANNOUNCE] Apache CouchDB 3.0.1 and 3.1.0 released

> On 6. May 2020, at 12:55, Sebastien wrote: > > Awesome news, thanks to everyone involved! > > A quick question about the JWT authentication support (greatest news in > this release for my project). Are there plans for Couch to support > extracting JWT tokens from a cookie? > In some

Re: What happens when I combine the view query params sorted=false with startkey & endkey?

Heya Thilo, startkey and endkey are applied first, so you are guaranteed to get all results within your specified range, but you are not guaranteed to get it in the sorted order defined by the second link you sent. Imagine a sharded database. When making a view query, CouchDB makes an internal

Re: SpiderMonkey 60 in CouchDB 3.x

Hi Joel, > On 25. Mar 2020, at 18:29, Joel Jucá wrote: > > Hello community! > > I saw the announcement of CouchDB 3 with great enthusiasm when there was a > mention of the updated JavaScript engine, SpiderMonkey version 60. It seems > to fully support ES6, so it would be possible to write

Re: CouchDB 2.3.1 - Really Big Document Breaks View

You also need to raise the os_process_timeout Cheers Jan — > On 9. Apr 2020, at 22:29, Mantell, Christopher Arthur > wrote: > > Hi, > > One document in our database is really big (1.2 million lines) and it causes > an OS_process_error when we access it. I've tried increasing the >

Re: [DISCUSS] moving email lists to Discourse

> On 12. Mar 2020, at 16:21, Paul Davis wrote: > > I'm not against anything of that nature, but if memory serves the > email lists are dictated by ASF policy. If you remember when we did the GitHub transition, as long as we can make sure messages end up on a mailing list, we should be fine

Re: Problem with unauthorized CouchDb 3.0 and ssl

Heya Marcus, Newly created databases are admin-only by default in 3.0 (which is different from 2.x): https://blog.couchdb.org/2020/02/26/the-road-to-couchdb-3-0-security/ So you’ll have to make an authenticated request

[ANNOUNCE] Apache CouchDB 3.0.0 released

of the CouchDB PMC, Jan Lehnardt —

Re: Re: Re: Backup Question on Version 2.2.0

ts is prohibited. If you have received this communication in error, > please notify the sender immediately by email or telephone and destroy all > copies of this communication and any attachments. > > > Proprietary > > -Original Message- > From: Jan Lehnardt &

Re: Re: Backup Question on Version 2.2.0

18 10:16 > metadata_dictionary_faq.1550175781.couch > -rw-r--r-- 1 couchdb couchdb 12473 Jan 30 2019 > pjk_rep_test.1539891783.couch > -rw-r--r-- 1 couchdb couchdb 49340 Jul 9 09:22 > _replicator.1539344313.couch > -rw-r--r-- 1 couchdb couchdb 37049 Jan 29 2019 _us

Re: Backup Question on Version 2.2.0

Hi Peter, The documentation page on Backups explains how to backup sharded database files: http://docs.couchdb.org/en/stable/maintenance/backups.html Best Jan -- Professional Support for Apache CouchDB: https://neighbourhood.ie/couchdb-support/ > On 18. Nov 2019, at 15:50, Krawetzky, Peter J

Apache CouchDB at Kubecon and FDB Summit: Free FoundationDB Summit Tickets Available

Hey all, IBM are giving away free tickets to the FoundationDB Summit during Kubecon San Diego: https://blog.couchdb.org/2019/10/10/apache-couchdb-at-kubecon-and-fdb-summit-free-foundationdb-summit-tickets-available/ Best Jan -- Professional Support for Apache CouchDB:

[ANNOUNCE] CouchDB Meetup in Berlin around ApacheCon EU, October 21st.

Dear CouchDB users and developers, I’m happy to announce our CouchDB meetup in Berlin just before ApacheCon EU: https://www.meetup.com/couchberlin/events/263966219/ There’s going to be CouchDB Committers, PMC members as well as a number of users form Berlin and all over Europe. We’re

Re: CouchDB 3.0 features?

Hi Brian, this reflects our current thinking: https://github.com/apache/couchdb/projects/1 It is not too late to pitch in ;) Best Jan -- Professional Support for Apache CouchDB: https://neighbourhood.ie/couchdb-support/ > On 2. Aug 2019, at 20:51, Brian Cottingham wrote: > > I read the

Re: Bind to localhost without require valid user

Only other admins can see admin's credentials in relocation docs. Regular users can only see their own replication docs. Cheers Jan — > On 29. Jul 2019, at 15:11, Dilushan Delgoda wrote: > > Hi. > > Thank you very much for your reply. > > I'm trying to replicate a database by putting a

Re: can't get couchdb installed (on a fresh 18.04 ubuntu)

Jut a quick note that the official install instructions are here: http://docs.couchdb.org/en/stable/install/index.html And I saw this issue fly by which might be related? https://github.com/apache/couchdb-pkg/issues/44 Best Jan — > On 24. Jun 2019, at 10:55, Rene Veerman wrote: > > i

Re: Need help with replication

And don’t replicate _global_changes! :) > On 17. May 2019, at 00:35, Mark Richter wrote: > > Third time - the image is here: > https://drive.google.com/open?id=1pU3GL9cbhtLuFdqfl9kyEw5lVAwPhCjJ > > Thanks (in advance). > > From: Mark Richter > Sent: Thursday, May 16, 2019 3:30 PM > To:

Re: can´t install couchdb?

on} > Release' does not have a Release file. > N: Updating from such a repository can't be done securely, and is therefore > disabled by default. > N: See apt-secure(8) manpage for repository creation and user configuration > details. > > > On Thu, May 16, 2019

Re: can´t install couchdb?

looks like you skipped this step: http://docs.couchdb.org/en/stable/install/unix.html#enabling-the-apache-couchdb-package-repository Best Jan — > On 16. May 2019, at 15:39, Rene Veerman wrote: > > ubuntu 18.04, installed, updated, then : > > root@albatross:~# curl -L

Re: Shards-directory still big after deleting big database in Fauxton

Glad this worked out. Quick tip then, unless you run this on an 8-core (or more) machine, you might want to look into reducing your q for this database. q=2 or $num_cores is a good rule of thumb. You can use our couch-continuum tool to migrate an existing db: https://npmjs.com/couch-continuum

Re: CouchDB & PouchDB Meetup #14, Thursday, May 9, 2019 Amsterdam

I’ll be there, thanks for putting this on :) Best Jan — > On 16. Apr 2019, at 14:34, Andy Wenk wrote: > > Dear CouchDB Community, > > I would like to invite you to the CouchDB & PouchDB Meetup #14 in Amsterdam. > It will be at Thursday, May 9 this year. Please RSVP for the event here: > >

Re: Leaking memory in logger process couch 2.3.1

In particular, of you have views, each design doc will cause a full database scan to be dumped into the logs. Cheers Jan — > On 21. Mar 2019, at 19:40, Robert Newson wrote: > > Hi, > > Eek. This queue should never get this big, it indicates that there is far too > much logging traffic

Re: Getting an error "all_dbs_active" running a CouchDB 2.3 cluster

Heya Jake, what is your q value for your databases on the source and target clusters? The default is 8, so 8*90 gives us 720 potential open dbs. It could just be that under normal operation, your 2.0 cluster never has to open all shards at the same time, but now that you are running a

[ANNOUNCE] CouchDB 2.3.1

. #1799: Restrict _purge to server admin. #1803: Use the same salt for admin passwords on cluster setup. #1053: Fix python2 compatibility for couchup. #1905: Fix python3 compatibility for couchup. On behalf of the CouchDB PMC, Jan Lehnardt —

Re: r and w parameters in couch2.x

Specifically, n is the number of copies of your data, not the number of nodes in the system. You can tweak read concurrency performance by increasing a database’s number of shards (q) and adding more nodes for those shards to live on, at the expense of view, all_docs and changes requests

Re: nano: UnhandledPromiseRejectionWarning: Error: connect ENOBUFS

Hi Stephan, welcome to CouchDB and asynchronous programming :) Let’s annotate your code to see what’s happening: const nano = require('nano')("http://localhost:5984”); # get a a nano instance, all good const larch = nano.db.use('larch’);# tell nano which db to use, all

CouchDB Inspection Raffle

Heya Everyone, you may or may not know that company Neighbourhoodie offers professional CouchDB services. One of these services is what we call a CouchDB Inspection, which gives you a detailed analysis of all the things that might be wrong with your CouchDB installation. See

  1   2   3   4   5   6   7   8   >