fork of https://github.com/oxigraph/rocksdb and https://github.com/facebook/rocksdb for nextgraph and oxigraph

You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

mrambacher e628f59e87 Create a CustomEnv class; Add WinFileSystem; Make LegacyFileSystemWrapper private (#7703) ... Summary: This PR does the following: -> Creates a WinFileSystem class. This class is the Windows equivalent of the PosixFileSystem and will be used on Windows systems. -> Introduces a CustomEnv class. A CustomEnv is an Env that takes a FileSystem as constructor argument. I believe there will only ever be two implementations of this class (PosixEnv and WinEnv). There is still a CustomEnvWrapper class that takes an Env and a FileSystem and wraps the Env calls with the input Env but uses the FileSystem for the FileSystem calls -> Eliminates the public uses of the LegacyFileSystemWrapper. With this change in place, there are effectively the following patterns of Env: - "Base Env classes" (PosixEnv, WinEnv). These classes implement the core Env functions (e.g. Threads) and have a hard-coded input FileSystem. These classes inherit from CompositeEnv, implement the core Env functions (threads) and delegate the FileSystem-like calls to the input file system. - Wrapped Composite Env classes (MemEnv). These classes take in an Env and a FileSystem. The core env functions are re-directed to the wrapped env. The file system calls are redirected to the input file system - Legacy Wrapped Env classes. These classes take in an Env input (but no FileSystem). The core env functions are re-directed to the wrapped env. A "Legacy File System" is created using this env and the file system calls directed to the env itself. With these changes in place, the PosixEnv becomes a singleton -- there is only ever one created. Any other use of the PosixEnv is via another wrapped env. This cleans up some of the issues with the env construction and destruction. Additionally, there were places in the code that required had an Env when they required a FileSystem. Many of these places would wrap the Env with a LegacyFileSystemWrapper instead of using the env->GetFileSystem(). These places were changed, thereby removing layers of additional redirection (LegacyFileSystem --> Env --> Env::FileSystem). Pull Request resolved: https://github.com/facebook/rocksdb/pull/7703 Reviewed By: zhichao-cao Differential Revision: D25762190 Pulled By: anand1976 fbshipit-source-id: 1a088e97fc916f28ac69c149cd1dcad0ab31704b		4 years ago
..
env_default.cc	Create a CustomEnv class; Add WinFileSystem; Make LegacyFileSystemWrapper private (#7703)	4 years ago
env_win.cc	Create a CustomEnv class; Add WinFileSystem; Make LegacyFileSystemWrapper private (#7703)	4 years ago
env_win.h	Create a CustomEnv class; Add WinFileSystem; Make LegacyFileSystemWrapper private (#7703)	4 years ago
io_win.cc	Create a CustomEnv class; Add WinFileSystem; Make LegacyFileSystemWrapper private (#7703)	4 years ago
io_win.h	Create a CustomEnv class; Add WinFileSystem; Make LegacyFileSystemWrapper private (#7703)	4 years ago
port_win.cc	Fix MSVC-related build issues (#7439)	4 years ago
port_win.h	Fix MSVC-related build issues (#7439)	4 years ago
win_jemalloc.cc	build: make it compile with @mode/win (#7406)	4 years ago
win_logger.cc	Create a CustomEnv class; Add WinFileSystem; Make LegacyFileSystemWrapper private (#7703)	4 years ago
win_logger.h	Create a CustomEnv class; Add WinFileSystem; Make LegacyFileSystemWrapper private (#7703)	4 years ago
win_thread.cc	build: make it compile with @mode/win (#7406)	4 years ago
win_thread.h	Replace namespace name "rocksdb" with ROCKSDB_NAMESPACE (#6433)	5 years ago
xpress_win.cc	Introduce a helper method UncompressData (#7434)	4 years ago
xpress_win.h	Introduce a helper method UncompressData (#7434)	4 years ago