Is there a way to efficiently clean up a WIDE reivision tree where there are a lot of conflicting branches? /open_rev=all takes forever to return and when you delete all revisions except current, also takes forever. Just interested in cleaning up the revision tree and keep current ONLY. Is there a quick and dirty way to achieve this besides purge and recreate doc?
@jens one complication is that this strategy doesn’t play well with the messed up clients? Won’t they just push the garbage revisions back to the server? All the purges would have to be coordinated with the clients as well right?
Maybe the strategy should be recreate the document with all the garbage revisions tombstoned? Not sure quite how the signature of the _revisions property on PUT /doc works. Can you just specify the tombstoned revisions in the “ids” array?