]> git-server-git.apps.pok.os.sepia.ceph.com Git - rocksdb.git/commit
Merge operator failed subcode (#11231)
authorAndrew Kryczka <andrewkr@fb.com>
Fri, 17 Feb 2023 18:58:46 +0000 (10:58 -0800)
committerFacebook GitHub Bot <facebook-github-bot@users.noreply.github.com>
Fri, 17 Feb 2023 18:58:46 +0000 (10:58 -0800)
commit25e1365227bdb544276d50df5b0fd2843640b22d
treef73dc4173919b3159994afe15ecf818a71082214
parent6aef1a05d65d10731fada543ecab838c51d01156
Merge operator failed subcode (#11231)

Summary:
From HISTORY.md: Added a subcode of `Status::Corruption`, `Status::SubCode::kMergeOperatorFailed`, for users to identify corruption failures originating in the merge operator, as opposed to RocksDB's internally identified data corruptions.

This is a followup to https://github.com/facebook/rocksdb/issues/11092, where we gave users the ability to keep running a DB despite merge operator failing. Now that the DB keeps running despite such failures, they want to be able to distinguish such failures from real corruptions.

Pull Request resolved: https://github.com/facebook/rocksdb/pull/11231

Test Plan: updated unit test

Reviewed By: akankshamahajan15

Differential Revision: D43396607

Pulled By: ajkr

fbshipit-source-id: 17fbcc779ad724dafada8abd73efd38e1c5208b9
HISTORY.md
db/db_merge_operator_test.cc
db/merge_helper.cc
db/version_set.cc
db/version_set_sync_and_async.h
include/rocksdb/status.h
table/get_context.cc
table/get_context.h
util/status.cc