Skip to content

HDDS-4735. Fix typo in hdds.proto #1837

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
cku328 merged 4 commits into from
Jan 26, 2021
Merged

HDDS-4735. Fix typo in hdds.proto #1837

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
45cbc90
HDDS-4735. Fix typo in hdds.proto
symious Jan 24, 2021
b520bb4
trigger new CI check
symious Jan 24, 2021
9f344a9
HDDS-4735. Fix some other typos
symious Jan 25, 2021
9df91ce
HDDS-4735. Fix some other typos
symious Jan 25, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions hadoop-hdds/interface-client/src/main/proto/hdds.proto
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@
/**
* These .proto interfaces are private and unstable.
* Please see http://wiki.apache.org/hadoop/Compatibility
* for what changes are allowed for a *unstable* .proto interface.
* for what changes are allowed for an *unstable* .proto interface.
*/

option java_package = "org.apache.hadoop.hdds.protocol.proto";
Expand Down Expand Up @@ -51,7 +51,7 @@ message DatanodeDetailsProto {

/**
The DatanodeDetailsProto is a basic type that will be shared by many Proto,
to reduce the number of fields transfered by ProtoBuf, only need to extend
to reduce the number of fields transferred by ProtoBuf, only need to extend
DatanodeDetailsProto for registering DataNode with SCM and Recon.
*/
message ExtendedDatanodeDetailsProto {
Expand Down Expand Up @@ -158,12 +158,12 @@ message NodePool {

/**
* LifeCycleState for SCM object creation state machine:
* ->Allocated: allocated on SCM but clean has not started creating it yet.
* ->Allocated: allocated on SCM but client has not started creating it yet.
* ->Creating: allocated and assigned to client to create but not ack-ed yet.
* ->Open: allocated on SCM and created on datanodes and ack-ed by a client.
* ->Close: container closed due to space all used or error?
* ->Close: container closed due to space all used or error.
* ->Timeout -> container failed to create on datanodes or ack-ed by client.
* ->Deleting(TBD) -> container will be deleted after timeout
* ->Deleting(TBD) -> container will be deleted after timeout.
* 1. ALLOCATE-ed containers on SCM can't serve key/block related operation
* until ACK-ed explicitly which changes the state to OPEN.
* 2. Only OPEN/CLOSED containers can serve key/block related operation.
Expand Down