-
Notifications
You must be signed in to change notification settings - Fork 530
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
Difficulty reading parquet files externally #2226
Comments
We have seen similar issues where various Parquet tooling doesn't support the same features that parquet-go does. We are working on a I believe the error pictured is being addressed, but I will let the engineer (@stoewer) who is working on it comment. |
Tempo In the meantime you could try stoewer/parquet-cli to gain insights about Tempo blocks (but keep in mind that this is an experimental tool and not meant to be used in production). |
Thank you for pointing me to the parquet-cli project, I cannot build it so I created an issue on that repo. But now I've found a way to log traceIDs, there's less of a need for me to inspect the data itself. I'll close this issue. |
Describe the bug
After Tempo compacts some data into a
data.parquet
file, I'd like to view this data with an external tool, but I have not been able to do so. I've tried parquet-tools, bdt, pandas (with both parquet engines), pyarrow (10.0.1 and a pretty recent build), and even parquet-mr. Could you recommend me a tool to use for inspecting these file contents?For example, this is the output from parquet-mr:
The text was updated successfully, but these errors were encountered: