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

Yuanbo Liu commented on HDFS-12195:
-----------------------------------

[~anu]/[~vagarychen]/[~nandakumar131]/[~cheersyang]
Thanks for your review.
{quote}
please rename FAILED_KEY_NOT_FOUND ==> KEY_NOT_FOUND
{quote}
It's renamed in 
{{KeySpaceManagerProtocolServerSideTranslatorPB#exceptionToResponseStatus}}, so 
I didn't change it in the latest patch.

I've exposed metadata store in metadata manager instead of creating 
listKeys(keyPrefix, maxKeys).
Other comments are addressed, upload v3 patch.

> Ozone: DeleteKey-1: KSM replies delete key request asynchronously
> -----------------------------------------------------------------
>
>                 Key: HDFS-12195
>                 URL: https://issues.apache.org/jira/browse/HDFS-12195
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ozone
>    Affects Versions: HDFS-7240
>            Reporter: Weiwei Yang
>            Assignee: Yuanbo Liu
>         Attachments: client-ksm.png, HDFS-12195-HDFS-7240.001.patch, 
> HDFS-12195-HDFS-7240.002.patch
>
>
> We will implement delete key in ozone in multiple child tasks, this is 1 of 
> the child task to implement client to scm communication. We need to do it in 
> async manner, once key state is changed in ksm metadata, ksm is ready to 
> reply client with a successful message. Actual deletes on other layers will 
> happen some time later.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to