You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ignore async_io ReadOption if FileSystem doesn't support it (facebook#11296)
Summary:
In PosixFileSystem, IO uring support is opt-in. If the support is not enabled by the user, then ignore the async_io ReadOption in MultiGet and iteration at the top, rather than follow the async_io codepath and transparently switch to sync IO at the FileSystem layer.
Pull Request resolved: facebook#11296
Test Plan: Add new unit tests
Reviewed By: akankshamahajan15
Differential Revision: D44045776
Pulled By: anand1976
fbshipit-source-id: a0881bf763ca2fde50b84063d0068bb521edd8b9
Copy file name to clipboardexpand all lines: HISTORY.md
+1
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,7 @@
2
2
## Unreleased
3
3
### Behavior changes
4
4
* Compaction output file cutting logic now considers range tombstone start keys. For example, SST partitioner now may receive ParitionRequest for range tombstone start keys.
5
+
* If the async_io ReadOption is specified for MultiGet or NewIterator on a platform that doesn't support IO uring, the option is ignored and synchronous IO is used.
5
6
6
7
### Bug Fixes
7
8
* Fixed an issue for backward iteration when user defined timestamp is enabled in combination with BlobDB.
0 commit comments