couchdb icon indicating copy to clipboard operation
couchdb copied to clipboard

Seamless multi-master syncing database with an intuitive HTTP/JSON API, designed for reliability

Results 231 couchdb issues
Sort by recently updated
recently updated
newest added

I was trying to upgrade my database installation from CouchDB v2.3.1 to v3.1.1 and experienced about 6 time slower performance on particular view invocations. ## Description [NOTE]: # ( Describe...

bug

## Summary Currently the config warns, that if no roles or members are configured, the database will be publicly accessible. If you just PUT `{}` into `/_security`, the database will...

enhancement
needs-triage

Since supporting SpiderMonkey versions > 1.8.5 we compile design doc functions of the form `function(args) { /* impl */ }` into a form that is recognise by newer JS engines....

## Overview This is a cherry-pick of a https://github.com/apache/couchdb/commit/845f917e35005a84ee790cd9cb9918d0b5be25ef from `main` into `3.x`. ## Testing recommendations Usual `./configure && make` would be sufficient since this commit doesn't provide new functionality....

The Mango query language provides CRUD operations and basic selector syntax for document retrieval. There are no aggregation functions. Thus, Mango does currently not have an equivalent to 'reduce' and...

mango
roadmap

## Summary If anyone is interested in consolidating the elixir, elixir-only, and elixir-suite into a single target I'm all ears. The first two are identical save for the `MIX_ENV` and...

build
enhancement

## Description Tuesday afternoon, the Query Planner stopped automatically selecting indexes for our `_find` queries. This was confirmed by sending the same queries to the `_explain` endpoint. This appears to...

bug
needs-triage

Current CouchDB 2.x replication scheduler is capable of starting and stopping replication jobs according to various rules, putting paused jobs in "Pending" state. It would be super cool to be...

enhancement

While benchmarking the performance of mango selectors I stumbled upon an interesting behaviour: towards almost the end of the response, where there's 3 - 5 - 10 more changes expected...

performance