-
Notifications
You must be signed in to change notification settings - Fork 217
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
Add aggregate_threshold with maximum_size to s3 sink #4385
Merged
graytaylor0
merged 3 commits into
opensearch-project:main
from
graytaylor0:FinalAggregateThreshold
Apr 4, 2024
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
42 changes: 42 additions & 0 deletions
42
...a/org/opensearch/dataprepper/plugins/sink/s3/configuration/AggregateThresholdOptions.java
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,42 @@ | ||
/* | ||
* Copyright OpenSearch Contributors | ||
* SPDX-License-Identifier: Apache-2.0 | ||
*/ | ||
|
||
package org.opensearch.dataprepper.plugins.sink.s3.configuration; | ||
|
||
import com.fasterxml.jackson.annotation.JsonProperty; | ||
import jakarta.validation.constraints.Max; | ||
import jakarta.validation.constraints.Min; | ||
import jakarta.validation.constraints.NotNull; | ||
import org.opensearch.dataprepper.model.types.ByteCount; | ||
|
||
|
||
/** | ||
* An implementation class of s3 index configuration Options | ||
*/ | ||
public class AggregateThresholdOptions { | ||
|
||
@JsonProperty("maximum_size") | ||
@NotNull | ||
private ByteCount maximumSize; | ||
|
||
/** | ||
* Controls how aggressive the force flush is when the maximum_size is reached. | ||
* Groups will be flushed until the total size is less than maximum_size * flush_capacity_ratio | ||
*/ | ||
@JsonProperty("flush_capacity_ratio") | ||
@Min(value = 0, message = "flush_capacity_ratio must be between 0.0 and 1.0") | ||
@Max(value = 1, message = "flush_capacity_ratio must be between 0.0 and 1.0") | ||
private double flushCapacityRatio = 0.5; | ||
|
||
/** | ||
* Read byte capacity configuration. | ||
* @return maximum byte count. | ||
*/ | ||
public ByteCount getMaximumSize() { | ||
return maximumSize; | ||
} | ||
|
||
public double getFlushCapacityRatio() { return flushCapacityRatio; } | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Should this be made to
private AggregateThresholdOptions aggregateThresholdOptions = new AggregateThresholdOptions();
, or should this remain null by default?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.
I like the idea of having a default. But, I think it would have to by dynamic. That is, we'd probably need to assign it like this:
As it is now, we may have a bug if you set this:
You would have an aggregate threshold of 50mb, but you are trying to get a 100mb threshold on each group.
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.
This makes sense. It is a little strange to add defaults based on other config parameters though, as they aren't really connected in the code. Also, it may be better to not require the code that checks for aggregate thresholds to run every time by default, since in many cases (all existing cases) users only have a single group, making the aggregate threshold obsolete. For these reasons, I will just leave it with no default
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.
Yea, let's not have any default - even the maximum_size. I think if the user is going to specify the
aggregate_threshold
at all, then he must also specify themaximum_size
. This will require the user to think about it more and hopefully get it correct in relation to the other thresholds.We could always change this later. But, if you remove the default 50mb for now, we won't have this possible confusion.