gardenia opened a new pull request, #9363:
URL: https://github.com/apache/ozone/pull/9363

   Please describe your PR in detail:
   
   In OzoneManagerStateMachine when certain write requests complete 
successfully a summary of that request will be written to a new rocksdb 
"ledger" table named CompletedRequestInfo
   
   The current CompletedRequestInfo schema is minimal:
   
   ```
   /**
    * CompletedRequestInfo table entry
    */
   message CompletedRequestInfo {
   
     optional int64 trxLogIndex = 1;
     required Type cmdType = 2; // Type of the command
     optional string volumeName = 3;
     optional string bucketName = 4;
     optional string keyName = 5;
     optional uint64 creationTime = 6;
   
     optional CreateKeyOperationArgs       createKeyArgs = 7;
     optional RenameKeyOperationArgs       renameKeyArgs = 8;
     optional DeleteKeyOperationArgs       deleteKeyArgs = 9;
     optional CommitKeyOperationArgs       commitKeyArgs = 10;
     optional CreateDirectoryOperationArgs createDirectoryArgs = 11;
     optional CreateFileOperationArgs      createFileArgs = 12;
   }
   ```
   
   The use of "optional" for the arguments was based on feedback from the 
community call where @errose28 made the point that the previous sketch of a 
schema (using a freeform Map<String, String>) did not jibe well with schema 
management and this optional pattern had been used in other places to get 
around that.
   
   This change adds the protobufs and entity class to store the completed event 
info (with the intent that a consumer can  use that data to generate event 
notifications about changes on the filesystem)
   
   ## What is the link to the Apache JIRA
   
   https://issues.apache.org/jira/browse/HDDS-14003
   
   ## How was this patch tested?
   
   unit tests
   


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

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

Reply via email to