-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: influx inspect export parquet #25047
Open
alespour
wants to merge
16
commits into
master-1.x
Choose a base branch
from
feat/influx-inspect-export-parquet
base: master-1.x
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 1 commit
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
0c65d78
feat(client): add initial support for exporting to Parquet
alespour 733e1bb
style: import order
alespour 3b5896c
fix: unused input parameter
alespour 92f08e2
test: add influx_inspect test
alespour 2544c28
style: go fmt
alespour f04fc04
fix: extend Parquet options values checks
alespour 031aae7
chore: update arrow to v16
alespour 50f4511
docs: update with new influx_inspect options and sample command
alespour db4bb2a
refactor: use constants instead of literal values
alespour 05c1e50
fix: use errors.Capture to handle errors in defer calls
alespour 6482911
fix: use errors.Capture to handle errors in defer calls
alespour c1e50bb
fix: wrap original error
alespour b48a1ca
fix: print buffer inside error message
alespour 54906a5
fix: print buffer inside error message
alespour 5b5d6ee
fix: check for empty input
alespour b09c14e
test: assert and cleanaup properly
alespour File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The tag set schema can change within a single TSM file from one series key to the next.
If a user writes the following point:
The schema is for the previous line is:
If the next write is:
The schema for that line is:
Therefore, the schema must be the union of all series keys, resulting in a table schema of:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume then the export have to iterate over twice TSM files. In the first iteration, complete tables schema would be gathered, and in the seconds iteration the actual data exported, correct?