[HDDS-795] RocksDb specific classes leak from DBStore/Table interfaces

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Target Version/s: 0.4.0
• Assignee: Marton Elek
• Reporter: Marton Elek
• Created: 02/Nov/18 12:48
• Updated: 21/Nov/18 20:47
• Resolved: 21/Nov/18 20:28

Description

org.apache.hadoop.utils.db.RocksDB and Table interfaces provide a vendor-independent way to access any key value store.

The default implementation uses RocksDb but other implementation also could be used (for example an InMemory implementation for testing only).

The current Table interface contains methods which depend on RocksDB specific classes. For example:

public interface DBStore extends AutoCloseable {
//...
/**
   * Return the Column Family handle. TODO: This leaks an RockDB abstraction
   * into Ozone code, cleanup later.
   *
   * @return ColumnFamilyHandle
   */
  ColumnFamilyHandle getHandle();
//...

We need to remove the RocksDB specific classes from the generic interfaces.

Issue Links

• blocks: HDDS-748 Use strongly typed metadata Table implementation