feat(influxdb): add connect/read timeouts#30
Merged
Conversation
- Add optional connectTimeout and readTimeout properties on InfluxDBConnection (Duration / ISO-8601, e.g. PT10S) - Keep existing behaviour unchanged when timeouts are not set - Add FluxReadTimeoutTest that simulates delayed first response bytes and verifies readTimeout failure/success
Contributor
src/main/java/io/kestra/plugin/influxdb/InfluxDBConnection.java
Outdated
Show resolved
Hide resolved
src/main/java/io/kestra/plugin/influxdb/InfluxDBConnection.java
Outdated
Show resolved
Hide resolved
Malaydewangan09
approved these changes
Jan 6, 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.
What changes are being made and why?
connectTimeoutandreadTimeoutproperties on InfluxDBConnection (Duration / ISO-8601, e.g. PT10S)resolves: #29
Setup Instructions
Contributor Checklist ✅
closes #ISSUE_IDorfixes #ISSUE_IDin the description if the PR relates to an opened issue.@Schemafor properties and outputs,@Pluginwith examples,README.mdfile with basic knowledge and specifics).rnotrendered(eg:rHost).runContext.logger()to log enough important infos where it's needed and with the best level (DEBUG, INFO, WARN or ERROR).⚙️ Properties
Property<T>carrier type, do not use@PluginProperty.@NotNulland checked during the rendering.Property<Map<String, Object>>.🧪 Tests
RunContextto actually run tasks).src/test/resources/flows..github/setup-unit.sh(to be set executable withchmod +x setup-unit.sh) (which can be executed locally and in the CI) all along with a newdocker-compose-ci.ymlfile (do not edit the existingdocker-compose.yml). If needed, create an executable (chmod +x cleanup-unit.sh)cleanup-unit.shto remove the potential costly resources (tables, datasets, etc).