Hi All,

I'd like to get views on whether we should preserve the _partition endpoints in 
CouchDB 4.0 or remove them. In CouchDB 4.0 all _view and _find queries will 
automatically benefit from the same performance boost that the "partitioned 
database" feature brings, by virtue of FoundationDB.

If we're preserving it, are we also deprecating it (so it's gone in 5.0)?

If we're ditching it, what will the endpoint return instead (404 Not Found, 410 
Gone?)

Thoughts welcome.

B.

Reply via email to