netmap: Clarify MaxObjectSize parameter implication on object size #63

Merged
fyrchik merged 1 commit from a-savchuk/frostfs-api:doc-max-object-size into master 2024-10-26 11:30:28 +00:00
Member

Close #50

Signed-off-by: Aleksey Savchuk a.savchuk@yadro.com

Close #50 Signed-off-by: Aleksey Savchuk <a.savchuk@yadro.com>
a-savchuk added 3 commits 2024-09-05 11:26:54 +00:00
Signed-off-by: Aleksey Savchuk <a.savchuk@yadro.com>
Signed-off-by: Aleksey Savchuk <a.savchuk@yadro.com>
[#50] *: Regenerate docs
All checks were successful
DCO action / DCO (pull_request) Successful in 23s
Formatters / Run fmt (pull_request) Successful in 41s
Pre-commit hooks / Pre-commit (pull_request) Successful in 41s
810575e144
Signed-off-by: Aleksey Savchuk <a.savchuk@yadro.com>
a-savchuk added 1 commit 2024-09-05 11:31:20 +00:00
test
Some checks failed
Formatters / Run fmt (pull_request) Successful in 20s
DCO action / DCO (pull_request) Failing after 34s
Pre-commit hooks / Pre-commit (pull_request) Successful in 46s
8780d30a3f
a-savchuk force-pushed doc-max-object-size from 8780d30a3f to b0415c455d 2024-09-05 11:32:49 +00:00 Compare
a-savchuk force-pushed doc-max-object-size from b0415c455d to 83bb8cc4ba 2024-09-05 11:40:17 +00:00 Compare
a-savchuk force-pushed doc-max-object-size from 83bb8cc4ba to 30f2eb344d 2024-09-05 11:45:24 +00:00 Compare
a-savchuk force-pushed doc-max-object-size from 30f2eb344d to 56bdadd74d 2024-09-05 11:53:10 +00:00 Compare
a-savchuk force-pushed doc-max-object-size from 56bdadd74d to c1eba27379 2024-09-05 11:54:57 +00:00 Compare
realloc reviewed 2024-09-05 12:52:31 +00:00
@ -291,1 +291,4 @@
// Value: little-endian integer. Default: 0.
//
// This value refers to the maximum size of a **physically** stored object
// in NeoFS. However, from a user's perspective, the **logical** size of a
Owner

FrostFS

FrostFS
Author
Member

But NeoFS is used throughout the documentation. Should I change all occurrences to keep it consistent?

But NeoFS is used throughout the documentation. Should I change all occurrences to keep it consistent?
Owner

Yes, but in a separate commit, please

Yes, but in a separate commit, please
Author
Member

Done

Done
fyrchik reviewed 2024-09-05 12:55:00 +00:00
@ -203,3 +203,2 @@
// * Continent \
// Node's continent name according to the [Seven-Continent model]
// (https://en.wikipedia.org/wiki/Continent#Number). Calculated
// Node's continent name according to the [Seven-Continent
Owner

How could it be misformatted if we have just merged PR where actions were green?

How could it be misformatted if we have just merged PR where actions were green?
Author
Member

It's just an incorrectly formatted link e.g. [frostfs] (git.frostfs.info), where an extra space in the middle will cause it to render as-is, rather than as the intended frostfs. It's not the responsibility of current actions to check for such issues

It's just an incorrectly formatted link e.g. `[frostfs] (git.frostfs.info)`, where an extra space in the middle will cause it to render as-is, rather than as the intended [frostfs](git.frostfs.info). It's not the responsibility of current actions to check for such issues
fyrchik marked this conversation as resolved
a-savchuk changed title from WIP: netmap: Clarify MaxObjectSize parameter implication on object size to netmap: Clarify MaxObjectSize parameter implication on object size 2024-09-05 13:02:35 +00:00
a-savchuk force-pushed doc-max-object-size from c1eba27379 to 2a46a9ea0a 2024-09-05 13:28:16 +00:00 Compare
aarifullin approved these changes 2024-09-06 07:24:44 +00:00
a-savchuk requested review from storage-core-developers 2024-09-06 07:34:01 +00:00
a-savchuk requested review from storage-core-committers 2024-09-06 07:34:02 +00:00
achuprov approved these changes 2024-09-06 07:48:10 +00:00
dstepanov-yadro approved these changes 2024-09-06 10:47:26 +00:00
fyrchik approved these changes 2024-09-06 13:35:48 +00:00
fyrchik merged commit 2a46a9ea0a into master 2024-09-06 13:35:57 +00:00
a-savchuk deleted branch doc-max-object-size 2024-11-02 13:45:27 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
6 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: TrueCloudLab/frostfs-api#63
No description provided.