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
I am using rocksdb v7.5. The db open fails on Win if we use diacritic characters in the folder name.
./ldb --db=C:/Desktop/Sévigné --create_if_missing put a1 b1
Failed: IO error: No such file or directory: Failed to create a directory: C:/Desktop/SΘvignΘ: The system cannot find the path specified.
The same operation works fine on Mac.
Expected behavior
db should open without any issues even if the folder name contains diacritic characters
Actual behavior
db open failed
Steps to reproduce the behavior
./ldb --db=C:/Desktop/Sévigné --create_if_missing put a1 b1
Failed: IO error: No such file or directory: Failed to create a directory: C:/Desktop/SΘvignΘ: The system cannot find the path specified.
The text was updated successfully, but these errors were encountered:
Duplicate issue. Enabling WITH_WINDOWS_UTF8_FILENAMES in the CMakeLists.txt and rebuilding rocksdb library fixed the issue.
Before:
option(WITH_WINDOWS_UTF8_FILENAMES "use UTF8 as characterset for opening files, regardles of the system code page" OFF)
if (WITH_WINDOWS_UTF8_FILENAMES)
add_definitions(-DROCKSDB_WINDOWS_UTF8_FILENAMES)
endif()
After:
option(WITH_WINDOWS_UTF8_FILENAMES "use UTF8 as characterset for opening files, regardles of the system code page" ON)
if (WITH_WINDOWS_UTF8_FILENAMES)
add_definitions(-DROCKSDB_WINDOWS_UTF8_FILENAMES)
endif()
I am using
rocksdb v7.5
. The db open fails on Win if we use diacritic characters in the folder name.The same operation works fine on Mac.
Expected behavior
db should open without any issues even if the folder name contains diacritic characters
Actual behavior
db open failed
Steps to reproduce the behavior
./ldb --db=C:/Desktop/Sévigné --create_if_missing put a1 b1
Failed: IO error: No such file or directory: Failed to create a directory: C:/Desktop/SΘvignΘ: The system cannot find the path specified.
The text was updated successfully, but these errors were encountered: