-
Notifications
You must be signed in to change notification settings - Fork 2.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
Consider removing parquetexporter #27284
Labels
Comments
This was referenced Oct 3, 2023
dmitryax
pushed a commit
that referenced
this issue
Oct 11, 2023
**Description:** Remove the parquet exporter **Link to tracking Issue:** Fixes #27284
JaredTan95
pushed a commit
to openinsight-proj/opentelemetry-collector-contrib
that referenced
this issue
Oct 18, 2023
**Description:** Remove the parquet exporter **Link to tracking Issue:** Fixes open-telemetry#27284
jmsnll
pushed a commit
to jmsnll/opentelemetry-collector-contrib
that referenced
this issue
Nov 12, 2023
**Description:** Remove the parquet exporter **Link to tracking Issue:** Fixes open-telemetry#27284
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Component(s)
exporter/parquet
Describe the issue you're reporting
I am the original author of the parquetexporter, and I think it needs to be removed.
Apache Parquet is a project defining a columnar data format that allows to work well with big data and S3-type storage.
This exporter was meant to be used to export data to Parquet files, but it's ambiguous how to write those files to S3. The awss3exporter would be a preferred approach to writing data. It is possible an encoder using Parquet will be applied moving forward, allowing easy marshaling and unmarshaling.
As is, the exporter is misleading ; it offers the hope for Parquet support but does little to get it done.
There was work from me on delivering a Parquet schema based off our protobuf schema, but it faltered. It appears the Otel Arrow approach is superior there and we should use this move forward.
In any case, I think it's time to remove this exporter altogether. No work has taken place on it in the last year.
The text was updated successfully, but these errors were encountered: