Skip to content

RocksJava API TODO

Jörg Maier edited this page Feb 1, 2015 · 27 revisions

This page sets out the known TODO items for the RocksJava API, it also shows who is thinking/working on a particular topic; Through this mechanism hopefully we can avoid duplicating effort.

TODO

  1. Fix locking issues with Slice/DirectSlice from Comparator. Move to thread-local storage of cached slice objects rather than single Slice locking with mutex. @adamretter

  2. Perhaps decide weather to use only Slice or DirectSlice to simplify overall API implementation, probably DirectSlice is more memory efficient.

  3. Use the Slice class in other Java classes where byte[] was previously used, so that we better align with C++ API, e.g. RocksIterator.

  4. Rework WBWIIterator to use both Slice and DirectSlice (see above).

  5. Implement ARM (Automatic Resource Management) e.g. try-with-resources Java 7 use via Closeable/AutoCloseable for iterators, db, write batches etc.

  6. Introduce final on variables/members everywhere they are immutable. @adamretter

  7. Implement ldb for Java. For example, the ability to specify the Comparator which implemented in Java. @adamretter

  8. Custom merge operator for Java. At the moment it is only possible to use merge operators which are available in C++ but not implementing custom functionality solely in Java. @fyrz

  9. Expose an AbstractLogger. RocksDB C++ api allows to provide a custom Logger. This shall also be possible from Java side and allows to attach RocksDB logging to application logging facilities. @fyrz

  10. Port remaining functionality in db.h to RocksJava. @fyrz

  11. Update Statistics/HistogramData to 3.10 @fyrz

Contents

Clone this wiki locally