Multiple copy numbers #221

Merged
fyrchik merged 1 commit from feat/multiple-copies-number into master 2023-05-05 16:07:14 +00:00
Member

Blocked by TrueCloudLab/frostfs-sdk-go#46.

Implementation might have to be changed according to TrueCloudLab/frostfs-sdk-go#45 discussion.

Blocked by https://git.frostfs.info/TrueCloudLab/frostfs-sdk-go/pulls/46. Implementation might have to be changed according to https://git.frostfs.info/TrueCloudLab/frostfs-sdk-go/issues/45 discussion.
carpawell force-pushed feat/multiple-copies-number from 3648ff99b4 to 85430af1ac 2023-04-11 18:01:12 +00:00 Compare
carpawell changed title from WIP: Multiple copy numbers to Multiple copy numbers 2023-04-11 18:22:51 +00:00
carpawell force-pushed feat/multiple-copies-number from 85430af1ac to 0720550a74 2023-04-11 18:25:11 +00:00 Compare
carpawell requested review from storage-core-committers 2023-04-11 18:26:56 +00:00
carpawell requested review from storage-core-developers 2023-04-11 18:26:56 +00:00
carpawell requested review from fyrchik 2023-04-11 18:27:00 +00:00
dstepanov-yadro requested changes 2023-04-12 06:58:16 +00:00
@ -144,3 +144,3 @@
var stream *rpc.PutRequestWriter
err = c.RawForAddress(addr, func(cli *rawclient.Client) error {
err = c.RawForAddress(context.Background(), addr, func(cli *rawclient.Client) error {

I think context.TODO() is better. context.Background() means that we don't need parent context. But for this case, in the bright future, we will use the parent context.

I think `context.TODO()` is better. `context.Background()` means that we don't need parent context. But for this case, in the bright future, we will use the parent context.
Author
Member

agree, fixed

agree, fixed
dstepanov-yadro marked this conversation as resolved
carpawell force-pushed feat/multiple-copies-number from 0720550a74 to 90ac80e433 2023-04-12 07:38:09 +00:00 Compare
carpawell requested review from dstepanov-yadro 2023-04-12 07:38:19 +00:00
carpawell requested review from storage-core-developers 2023-04-12 07:38:26 +00:00
dstepanov-yadro approved these changes 2023-04-12 09:36:32 +00:00
acid-ant approved these changes 2023-04-12 10:06:15 +00:00
carpawell added the due date 2023-04-21 2023-04-17 14:12:24 +00:00
fyrchik approved these changes 2023-04-21 09:47:05 +00:00
@ -144,3 +144,3 @@
var stream *rpc.PutRequestWriter
err = c.RawForAddress(addr, func(cli *rawclient.Client) error {
err = c.RawForAddress(context.TODO(), addr, func(cli *rawclient.Client) error {
Owner

Do we have an issue?

Do we have an issue?
Author
Member

that line problem somehow disappeared (well, hehe, thanks to @dstepanov-yadro)

_that line_ problem somehow disappeared (well, hehe, thanks to @dstepanov-yadro)
@ -87,0 +88,4 @@
// backward compatibility for scalar `copies_number`
if len(cfg.copyNumbers) == 1 {
cn := cfg.copyNumbers[0]
cfg.flatSuccess = &cn
Owner

Can't we just take address of the first element directly?

Can't we just take address of the first element directly?
Author
Member

usually try not to do that but it looks safe here, fixed

usually try not to do that but it looks safe here, fixed
@ -94,6 +101,11 @@ func NewTraverser(opts ...Option) (*Traverser, error) {
for i := 0; i < replNum; i++ {
if cfg.trackCopies {
if len(cfg.copyNumbers) > i {
Owner

What about creating default vector with ReplicaNumberByIndex elements and removing special case here?

What about creating default vector with `ReplicaNumberByIndex` elements and removing special case here?
Author
Member

hope i got you right and fixed but double check that, please

hope i got you right and fixed but double check that, please
Owner

@carpawell rebase, please

@carpawell rebase, please
carpawell force-pushed feat/multiple-copies-number from 90ac80e433 to 604ca51264 2023-05-04 15:00:02 +00:00 Compare
carpawell requested review from fyrchik 2023-05-04 15:00:47 +00:00
fyrchik approved these changes 2023-05-05 16:07:08 +00:00
fyrchik merged commit ee58b390bb into master 2023-05-05 16:07:14 +00:00
fyrchik deleted branch feat/multiple-copies-number 2023-05-05 16:07:14 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

2023-04-21

Dependencies

No dependencies set.

Reference: TrueCloudLab/frostfs-node#221
No description provided.