diff options
| author | Jay Zhuang <zjay@fb.com> | 2021-02-18 09:36:23 -0800 |
|---|---|---|
| committer | Jay Zhuang <zjay@fb.com> | 2021-02-18 09:36:23 -0800 |
| commit | 09c7e96eac1ab983f97ce9e0406730b8014b3398 (patch) | |
| tree | def26bdd1d7ea31bbee85680c8cfae0f11ba576e | |
| parent | 9ef7f70c11e26ac82bc3716d47902ad3a773fa48 (diff) | |
Bump version and update HISTORY.md for 6.17.3v6.17.3
| -rw-r--r-- | HISTORY.md | 5 | ||||
| -rw-r--r-- | include/rocksdb/version.h | 2 |
2 files changed, 5 insertions, 2 deletions
diff --git a/HISTORY.md b/HISTORY.md index 384dacde3..a8d306776 100644 --- a/HISTORY.md +++ b/HISTORY.md @@ -1,9 +1,12 @@ # Rocksdb Change Log +## 6.17.3 (02/18/2021) +### Bug Fixes +* Fix `WRITE_PREPARED`, `WRITE_UNPREPARED` TransactionDB `MultiGet()` may return uncommitted data with snapshot. + ## 6.17.2 (02/05/2021) ### Bug Fixes * Since 6.15.0, `TransactionDB` returns error `Status`es from calls to `DeleteRange()` and calls to `Write()` where the `WriteBatch` contains a range deletion. Previously such operations may have succeeded while not providing the expected transactional guarantees. There are certain cases where range deletion can still be used on such DBs; see the API doc on `TransactionDB::DeleteRange()` for details. * `OptimisticTransactionDB` now returns error `Status`es from calls to `DeleteRange()` and calls to `Write()` where the `WriteBatch` contains a range deletion. Previously such operations may have succeeded while not providing the expected transactional guarantees. -* Fix `WRITE_PREPARED`, `WRITE_UNPREPARED` TransactionDB `MultiGet()` may return uncommitted data with snapshot. ## 6.17.1 (01/28/2021) ### Behavior Changes diff --git a/include/rocksdb/version.h b/include/rocksdb/version.h index eb62bb7a6..1bb502ecd 100644 --- a/include/rocksdb/version.h +++ b/include/rocksdb/version.h @@ -6,7 +6,7 @@ #define ROCKSDB_MAJOR 6 #define ROCKSDB_MINOR 17 -#define ROCKSDB_PATCH 2 +#define ROCKSDB_PATCH 3 // Do not use these. We made the mistake of declaring macros starting with // double underscore. Now we have to live with our choice. We'll deprecate these |