feat: add influxdb3_client
#24662
Closed
feat: add influxdb3_client
#24662
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
A new crate, influxdb3_client, was added, which provides the Client struct. This gives programmatic access to the infludxb3 HTTP API. This commit implements a partial version of the api_v3_write_lp method along with a test for ensuring the happy path. The underlying API is not yet complete, so the response handling is still a TODO.
hiltontj
force-pushed
the
hiltontj/24661-influxdb3-client
branch
from
5ede4d5
to
e8e1f23
Compare
Prior to this change we've had CI fail nightly because we can't push the image to CI due to permissions issues. The problem is that influxdata/influxdb_iox is the one that actually has access to push that data to quay. This commit removes the nightly build and references to it as this image is built nightly by the IOx team. If things break we have access to fix it, but I don't think it'll be an issue.
This commit adds the ability to choose the output format of a query via the v3 api so that a user can choose, whether by Accept headers or the format url param, how the data will be returned to them. Prior to this commit the default was a pretty printed text format, but that instead has been changed to json as the default. There are multiple formats one can choose: 1. json 2. csv 3. pretty printed text 4. parquet I've tested each of these out and it works well. In particular the parquet output is exciting as users will be able to perform a query and receive back parquet data that they can then load into say a Python script or something else to work on and operate it. As we extend what data can be queried, as well as persisting it, what people will be able to do with Edge will be really cool and I'm interested to see how users will end up using this functionality in the future.
* refactor: move write buffer into its own dir * feat: implement write buffer segment with wal flushing This creates the WriteBufferFlusher and OpenBufferSegment. If a wal is passed into the buffer, data written into it will be persisted to the wal for the initialized segment id. * refactor: use crossbeam in flusher and pr cleanup
|
Closing after making a mess of the git commit history, see #24665 |
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.
A new crate,
influxdb3_client, was added, which provides theClientstruct to give programmatic access to theinfluxdb3HTTP API.Closes #24661
Description
WIP