[ 
https://issues.apache.org/jira/browse/HDDS-1691?focusedWorklogId=267110&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-267110
 ]

ASF GitHub Bot logged work on HDDS-1691:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 25/Jun/19 23:14
            Start Date: 25/Jun/19 23:14
    Worklog Time Spent: 10m 
      Work Description: avijayanhwx commented on issue #1013: HDDS-1691 : 
RDBTable#isExist should use Rocksdb#keyMayExist
URL: https://github.com/apache/hadoop/pull/1013#issuecomment-505656426
 
 
   cc @bharatviswa504 , @mukul1987, @nandakumar131 
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 267110)
    Time Spent: 1h 50m  (was: 1h 40m)

> RDBTable#isExist should use Rocksdb#keyMayExist
> -----------------------------------------------
>
>                 Key: HDDS-1691
>                 URL: https://issues.apache.org/jira/browse/HDDS-1691
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>            Reporter: Mukul Kumar Singh
>            Assignee: Aravindan Vijayan
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> RDBTable#isExist can use Rocksdb#keyMayExist, this avoids the cost of reading 
> the value for the key.
> Please refer, 
> https://github.com/facebook/rocksdb/blob/7a8d7358bb40b13a06c2c6adc62e80295d89ed05/java/src/main/java/org/rocksdb/RocksDB.java#L2184



--
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