Skip to content

update(S3 Tables): Support for Parquet file format #3071

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

Open
wants to merge 3 commits into
base: release-6.0
Choose a base branch
from

Conversation

Meggielqk
Copy link
Collaborator

@Meggielqk Meggielqk added this to the 6.0.0 milestone Jul 14, 2025
@Meggielqk Meggielqk marked this pull request as ready for review July 15, 2025 09:14
@Meggielqk Meggielqk requested review from thalesmg and id July 15, 2025 09:14
thalesmg
thalesmg previously approved these changes Jul 15, 2025

- **Data File Format**: Defines the format of the data file used to store batched MQTT messages in S3. Supported values:
- `avro`: (Default) Stores records in Avro format.
- `parquet`: Stores records in Apache Parquet format. Ideal for use with data warehouses and analytics tools such as AWS Athena.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: the comment suggests that avro might not work in AWS Athena, which is not true. It works with avro data files.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about the descriptions like the following (with extra info for users to make a suitable decision):

  • avro: (Default) Stores records in Avro format, which is row-based and ideal for streaming data and evolving schemas.

  • parquet: Stores records in Apache Parquet format, which is column-based and optimized for analytical queries over large datasets.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants