NO-SNOW: Deprecate BUFFER_FLUSH_INTERVAL_IN_MILLIS parameter #659
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.
MAX_CLIENT_LAG
was introduced, it's not backward compatible with the current logic sinceMAX_CLIENT_LAG_ENABLED
is true by default and we won't even check forBUFFER_FLUSH_INTERVAL_IN_MILLIS
. Instead of supporting backward compatible, I decide to removeBUFFER_FLUSH_INTERVAL_IN_MILLIS
completely since that is an undocumented parameter. We only supportMAX_CLIENT_LAG
going forward and usingBUFFER_FLUSH_INTERVAL_IN_MILLIS
will result in an exception.BUFFER_FLUSH_INTERVAL_IN_MILLIS
so the transition is smooth,MAX_CLIENT_LAG
now also supports LONG input and input without a time unit (default will be milliseconds)