[ 
https://issues.apache.org/jira/browse/HDDS-795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16693637#comment-16693637
 ] 

Elek, Marton commented on HDDS-795:
-----------------------------------

Ups. Thanks. My comment was changed back during my fight with git rebase. 

Now I fixed it together with the one remaining checkstyle issue.

{code}
   * Initialize an atomic batch operation which can hold multiple PUT/DELETE
   * operations and committed later in one step.
   *
   * @return BatchOperation holder which can be used to add or commit batch
   * operations.
   */
  BatchOperation initBatchOperation();
{code}

> RocksDb specific classes leak from DBStore/Table interfaces
> -----------------------------------------------------------
>
>                 Key: HDDS-795
>                 URL: https://issues.apache.org/jira/browse/HDDS-795
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
>            Priority: Major
>         Attachments: HDDS-795.001.patch, HDDS-795.002.patch, 
> HDDS-795.003.patch, HDDS-795.004.patch, HDDS-795.005.patch, HDDS-795.006.patch
>
>
> 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:
> {code}
> 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();
> //...
> {code}
> We need to remove the RocksDB specific classes from the generic interfaces.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to