Add InfluxDB Connector #24220
Open
Add InfluxDB Connector #24220
+4,736
−0
Conversation
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
k3rnL
force-pushed
the
k3rnl/influxdb-connector
branch
9 times, most recently
from
c26a3f8
to
caed040
Compare
|
I'm not sure if the CI fails because of the PR's code or if the tests are flaky ? |
|
|
k3rnL
force-pushed
the
k3rnl/influxdb-connector
branch
from
caed040
to
480d66d
Compare
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.
Description
This PR introduces a new connector for InfluxDB, enabling Trino to query time-series data stored in InfluxDB. InfluxDB is a widely used time-series database but diverges from many traditional database standards, requiring a tailored approach to integration.
Additional context and related issues
I must note that most of the work was made in the past, but the PR was never finalized #15549
I have mostly only rebased the code, fixed tests and adapt the code to the new requirements.
My addition is the support for schema creation and schema/table destruction.
Release notes
( ) Release notes are required, with the following suggested text: