1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
Hello,
When you enable partition projection on a table, Athena ignores any partition metadata in the AWS Glue Data Catalog or external Hive metastore for that table. But, with DESCRIBE TABLE query, you can get the list of columns, including partition columns, for the named column. This allows you to examine the attributes of a complex column. You can also list table properties using SHOW TBLPROPERTIES query.
REFERENCES:
https://docs.aws.amazon.com/athena/latest/ug/describe-table.html https://docs.aws.amazon.com/athena/latest/ug/show-tblproperties.html
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 9 Monaten- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
Not quite the question I'm asking. Table and partition stats as returned by:
https://docs.aws.amazon.com/glue/latest/webapi/API_GetColumnStatisticsForPartition.html https://docs.aws.amazon.com/glue/latest/webapi/API_GetColumnStatisticsForTable.html
That data is used for cost based optimization within Athena I'm assuming. If partition projection skips the call to Glue Catalog and hence does not collect column stats....how does this impact Athena cost based optimization for query planning? Would query planning then lack this information and hence more inefficient join queries would be produced? Without that information the optimizer would not be able to do such a good job of automatic join reordering, this would have an impact on performance.
So, does partition projection prevent Athena from accessing column stats and therefore have a negative impact of cost based optimization and join performance?