feat/Influx sink - support multiple retention policies#70
Merged
Conversation
added 4 commits
May 7, 2026 02:15
Context: Some of the measurements/series you're interested in live data, old data is not so useful/interesting OR Say you've high frequency influx points and you've summarry/aggregated points. You would like to keep summary points for over weeks/months whereas granular/high frequency data can't be kept for that duration For the above mentioned cases - one can utilize the retention policies where; same db, same measurement, but different retention policy. Details: Add a new configuration SINK_INFLUX_RETENTION_POLICY_LIST_KEY which is similar to SINK_INFLUX_MEASUREMENTS_LIST_KEY and the usage similar how we used multiple measurements. In custom jobs we would like to configure the sink like ``` measurements = String.split(configuration.getString(SINK_INFLUX_MEASUREMENTS_LIST_KEY), ',') measurementName = measurements[0] retention_policies = String.split(configuration.getString(SINK_INFLUX_RETENTION_POLICY_LIST_KEY), ',') retentionPolicy = retention_policies[1] getSink(measurement_name, retentionPolicy, .....and other args) ```
…parameters of the methods
deepanshgoyal33
approved these changes
May 8, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Context:
Some of the measurements/series you're interested in live data, old
data is not so useful/interesting
OR
Say you've high frequency influx points and you've summarry/aggregated
points. You would like to keep summary points for over weeks/months
whereas granular/high frequency data can't be kept for that duration
For the above mentioned cases - one can utilize the retention policies
where; same db, same measurement, but different retention policy.
Details:
Add a new configuration SINK_INFLUX_RETENTION_POLICY_LIST_KEY which is similar to SINK_INFLUX_MEASUREMENTS_LIST_KEY and the usage similar how we used multiple measurements.
In custom jobs we would like to configure the sink like
and refactor - overrides are packaged in an object instead of increasing parameters of the methods