Dgraph is moving away from RocksDB to their own Badger solution so this section may not be accurate for much longer - https://open.dgraph.io/post/badger/#conclu
| This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||
| ||||||||||||||
Dgraph is moving away from RocksDB to their own Badger solution so this section may not be accurate for much longer - https://open.dgraph.io/post/badger/#conclusion Antnee (talk) 14:55, 30 May 2017 (UTC)
The geospatial support was removed in v6.0.0 (source: https://github.com/facebook/rocksdb/blob/main/HISTORY.md#600-2019-02-19)
From HISTORY.md: "Remove geodb, spatial_db, document_db, json_document, date_tiered_db, and redis_lists."
Dveeden (talk) 13:31, 1 November 2022 (UTC)
The bindings for the Python lanague cited in https://github.com/stephan-hof/pyrocksdb are outdated by eight years. https://github.com/faust-streaming/python-rocksdb and https://github.com/Congyuwang/RocksDict are more actively maintained. Wbarnha (talk) 00:56, 9 June 2023 (UTC)
When I googled this, I got a synopsis based on the Wikipedia page, from the definition paragraph. That paragraph mentions the role of the predecessor of LevelDB and Google as the author of LevelDB, but it doesn't mention Facebook's role as the current maintainer of the RocksDB project itself. Thus, it gives the false knowing from a quick (inattention) review from the synopsis, that the main role in maintaining and development of rocksdb is belongs to Google. BlzzUa (talk) 08:57, 22 August 2026 (UTC)
Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.