container: Add ListStream method #70
No reviewers
Labels
No labels
P0
P1
P2
P3
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
5 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-api#70
Loading…
Reference in a new issue
No description provided.
Delete branch "elebedeva/frostfs-api:feat/stream-for-list"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
TrueCloudLab/frostfs-node#1452
Signed-off-by: Ekaterina Lebedeva ekaterina.lebedeva@yadro.com
WIP: [#XX] container: Add ListStream methodto WIP: container: Add ListStream methoda14a8281bf
tob1c4f02946
WIP: container: Add ListStream methodto container: Add ListStream method@ -62,2 +62,4 @@
// container list access denied.
rpc List(ListRequest) returns (ListResponse);
// Returns all owner's containers from 'Container` smart contract' storage
Fixed
b1c4f02946
toeba1a55f88
eba1a55f88
tod3d8412323
d3d8412323
toefe46b28bc
@ -248,0 +261,4 @@
message ListStreamRequest {
// List containers stream request body.
message Body {
// Identifier of the container owner
There is no dot at the end, and I am now wondering why we do not check this.
efe46b28bc
to8540f0d18d
New commits pushed, approval review dismissed automatically according to repository settings
New commits pushed, approval review dismissed automatically according to repository settings
@ -248,0 +295,4 @@
// Carries response verification information. This header is used to
// authenticate the nodes of the message route and check the correctness of
// transmission.
neo.fs.v2.session.ResponseVerificationHeader verify_header = 3;
#69 had been merged last week. Since, we don't use
neo.fs.v2
namespace - it does no longer exist. You'll probably encounter difficulties trying regenerate protobufs withinfrostfs-sdk-go/api
.I'd like to know the steps for an implementation of this method in
frostfs-node
. Should it be held for a while until all nodes bumpfrostfs-sdk-go
version (in other words, all services will run handlers in the new namespace)?Sorry, this comment is irrelevant as those PR was merged into non-master branch