davisp commented on issue #2666: soft-deletion for database URL: https://github.com/apache/couchdb/pull/2666#issuecomment-608544648 So, apparently I'm the only one that's been assuming that this is a mirror of the `GET _dbs_info` API end point and working from that perspective. @mikerhodes I don't think the `_all_dbs` approach is very useful. When would you ever want just a list of database names that have soft deletions or just a list of timestamps? Its RESTy in all the bad ways that lead us to adding another API endpoint that dumps all of that information in a single response like we already had to do for `GET|POST /_dbs_info`. @ricellis If we stay with the `POST _deleted_dbs` then I don't think its a good idea to remove the `"undelete"` key as the API loses its self-documentation aspect. Plus we'd be hamstrung adding other operations in the future (not that I can think of any). If we want to revert to `POST _undelete` then I'd be fine dropping the JSON key. Consistency in the `"timestamp"` key is a good idea. I'd vote for `"timestamp"` since there's no target timestamp to disambiguate and `DELETE /_deleted_dbs/DbName?source_timestamp=foo` reads awkwardly. @jiangphcn I'm can't decide whether you're suggesting we support the `GET /_deleted_dbs/DbName/Timestamp` API or not. I don't think we should add alternative APIs for things that can be accomplished with a single view based API so I would vote against adding them. But you might also saying we don't need them, in which case we're in agreement and you can ignore me.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
