You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ratis.apache.org by "runzhiwang (Jira)" <ji...@apache.org> on 2020/11/13 07:29:00 UTC

[jira] [Comment Edited] (RATIS-1154) Add a flush() API in streaming

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

runzhiwang edited comment on RATIS-1154 at 11/13/20, 7:28 AM:
--------------------------------------------------------------

[~szetszwo]  I think we need this api,  especially if ozone want to support hflush,  what do you think ?  But we can do it after error hanlding.


was (Author: yjxxtd):
[~szetszwo]  I think we need this api,  especially if ozone want to support hflush,  what do you think ?

> Add a flush() API in streaming
> ------------------------------
>
>                 Key: RATIS-1154
>                 URL: https://issues.apache.org/jira/browse/RATIS-1154
>             Project: Ratis
>          Issue Type: Sub-task
>          Components: Streaming
>            Reporter: Shashikant Banerjee
>            Assignee: runzhiwang
>            Priority: Major
>
> In Ozone, for a single block there will be multiple putBlock opertions.  In case of using streaming for block write , ratis log transaction should be created for all these operations() (as happens with stream.close()). In such cases, it would be useful to add a flush() semantic in streaming which ensures one block can be wriiten over a single streaming channel with multiple commits happening in between.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)