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

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

                Author: ASF GitHub Bot
            Created on: 03/Jul/19 20:15
            Start Date: 03/Jul/19 20:15
    Worklog Time Spent: 10m 
      Work Description: bharatviswa504 commented on issue #1044: HDDS-1731. 
Implement File CreateFile Request to use Cache and DoubleBuffer.
URL: https://github.com/apache/hadoop/pull/1044#issuecomment-508239467
 
 
   Test failures are not related to this patch.
   I will commit this to the trunk.
   Thank You @arp7 for the review.
 
----------------------------------------------------------------
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: 271865)
    Time Spent: 5h 40m  (was: 5.5h)

> Implement File CreateFile Request to use Cache and DoubleBuffer
> ---------------------------------------------------------------
>
>                 Key: HDDS-1731
>                 URL: https://issues.apache.org/jira/browse/HDDS-1731
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>            Reporter: Bharat Viswanadham
>            Assignee: Bharat Viswanadham
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.5.0
>
>          Time Spent: 5h 40m
>  Remaining Estimate: 0h
>
> In this Jira, we shall implement createFile request according to the HA 
> model, and use cache and double buffer.



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