-
Notifications
You must be signed in to change notification settings - Fork 3
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.
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
Allow controlling max manifests per content with env var #388
Conversation
Allow setting the max number of manifests per content piece during compaction using an env var.
|
||
mgr := newManagerForTesting(ctx, t, data, ManagerOptions{}) | ||
for _, test := range table { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
simplest to view with whitespace disabled
🤔 race detector tests failed in CI and locally when running the same command, but the reason they failed is |
Default to having the feature off if the env var isn't set or is set to a value that is <= 0. This makes things a bit safer since it requires explicit configuration to enable. Also be more careful about the types being used to contain values since we're parsing data from a string which may make different assumptions about integer widths. This also adds a layer of protection in some sense since values larger than maxInt64 will overflow to a negative value and result in the feature being disabled instead of writing out 1 manifest per content piece.
This should also fix race detector failures in CI since we no longer need to write out as many manifests.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🏁
Allow adjustments to the max number of manifests per content piece through the use of an environment variable