Robert Newson

for sure, that indicates a bug here. It took 8 runs locally to get an internal_server_error so this will be fun to track down, but it needs to be found

I recommend building a map-reduce view directly (queried via `_view` not `_find`). This is an actual index (on the emitted key), and any query you can do to `_view` will...

https://github.com/apache/couchdb/blob/aca60ddf147811547b11cf5e8fd10bcfbe3c053e/src/couch_mrview/include/couch_mrview.hrl#L57 https://github.com/apache/couchdb/blob/aca60ddf147811547b11cf5e8fd10bcfbe3c053e/src/couch_mrview/include/couch_mrview.hrl#L72 You may need to paginate, or pass a larger `?limit=` query parameter.

You can get your desired behaviour by putting each view in a separate design document, the optimisations from putting multiple views in the same design document come at this (considerable)...

hi, this looks like data corruption to me. The binary in question is a `kp_node` but it is somehow truncated or otherwise invalid.

That image contains CouchDB 3.3.2.

so I think this is data corruption somehow, you'll need to try earlier backups until something works but we're very curious as to how this might have happened. If you...

CouchDB is built as a "crash only" system, meaning that the couchdb process is always ready to be killed, there's no shutdown code, no need to call `sync` manually, etc....

hm, odd. I definitely expect exact lookup to work for a key that is a json object. It worked for me locally and is definitely intentionally supported. The collation specification...

Caching is vital to couchdb as is the processing we do when opening databases and indexes, it doesn't make sense to me for couchdb to start on demand.