You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m trying to understand how well AWS Redshift Spectrum supports data skipping when working with Hudi datasets.
From the Athena documentation, it’s clear that Athena supports file listing from Hudi’s meta table but doesn’t utilize features like column statistics or bloom filters for data skipping. However, the official docs do not mention this for Redshift Spectrum.
Does anyone know if Redshift Spectrum, Supports column statistics and bloom filters from Hudi’s meta table for query optimization?
or it Works the same as Athena by only supporting file listing?
Any clarification or references would be really helpful. Thanks!
The text was updated successfully, but these errors were encountered:
The following documentation for Redshift Spectrum has been located. However, it does not provide information regarding the feature's support status. We will therefore need to contact the AWS product team for further clarification.
"Hudi supports snapshot isolation, which means you can query data without picking up any in-progress or not-yet-committed changes. This means you can write changes to the dataset in EMR at the same time users are querying it with Athena and Amazon Redshift Spectrum."
I’m trying to understand how well AWS Redshift Spectrum supports data skipping when working with Hudi datasets.
From the Athena documentation, it’s clear that Athena supports file listing from Hudi’s meta table but doesn’t utilize features like column statistics or bloom filters for data skipping. However, the official docs do not mention this for Redshift Spectrum.
Does anyone know if Redshift Spectrum, Supports column statistics and bloom filters from Hudi’s meta table for query optimization?
or it Works the same as Athena by only supporting file listing?
Any clarification or references would be really helpful. Thanks!
The text was updated successfully, but these errors were encountered: