wbtiger
/
foundationdb
mirror of https://github.com/apple/foundationdb.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix trace event detail name collision in MutationTracking use cases.

This commit is contained in:
Steve Atherton 2021-08-24 08:04:19 -07:00
parent f000447414
commit d6bdde6fe8
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
fdbserver/RestoreApplier.actor.h
View File

@ -62,8 +62,8 @@ struct StagingKey {
void add(const MutationRef& m, LogMessageVersion newVersion) {
ASSERT(m.type != MutationRef::SetVersionstampedKey && m.type != MutationRef::SetVersionstampedValue);
DEBUG_MUTATION("StagingKeyAdd", newVersion.version, m)
.detail("Version", version.toString())
.detail("NewVersion", newVersion.toString());
.detail("SubVersion", version.toString())
.detail("NewSubVersion", newVersion.toString());
if (version == newVersion) {
// This could happen because the same mutation can be present in
// overlapping mutation logs, because new TLogs can copy mutations
@ -83,8 +83,8 @@ struct StagingKey {
}
if (version < newVersion) {
DEBUG_MUTATION("StagingKeyAdd", newVersion.version, m)
.detail("Version", version.toString())
.detail("NewVersion", newVersion.toString())
.detail("SubVersion", version.toString())
.detail("NewSubVersion", newVersion.toString())
.detail("MType", getTypeString(type))
.detail("Key", key)
.detail("Val", val)