Conflicting revision bodies are not removed after resolution

Description

Discovered today while investigating that, when a conflict is resolved, the "losing" revision still has the kKeepBody flag, which means its body is never removed.

This has no visible effect, but it consumes disk space. If there have been a lot of conflicts, and/or documents are large, it can be quite noticeable.

Activity

Show:

Jens Alfke February 25, 2020 at 11:23 PM

Fixed and out for review.

I'm also extending the "compact" subcommand of the cblite tool to optionally prune this stuff from existing databases.

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created February 22, 2020 at 2:15 AM
Updated September 10, 2020 at 7:46 PM
Resolved May 22, 2020 at 6:38 PM
Instabug