The column name for partitions is different. Trino uses partitions and Spark uses partition_summaries.
$partitions table
spec_id, position_delete_record_count, position_delete_file_count, equality_delete_record_count, equality_delete_file_count, last_updated_at(μs), last_updated_snapshot_id columns are missing.
The column name for total size is different. Trino uses total_size and Spark uses total_data_file_size_in_bytes.
$files table
spec_id, partition, sort_order_id, readable_metrics columns are missing.
$properties
tableThis table is specific to Trino.
$history
tableTrino supports all columns in Spark.
$metadata_log_entries
tableTrino supports all columns in Spark.
$snapshots
tableTrino supports all columns in Spark.
$manifests
tableThe column name for partitions is different. Trino uses
partitions
and Spark usespartition_summaries
.$partitions
tablespec_id, position_delete_record_count, position_delete_file_count, equality_delete_record_count, equality_delete_file_count, last_updated_at(μs), last_updated_snapshot_id columns are missing. The column name for total size is different. Trino uses
total_size
and Spark usestotal_data_file_size_in_bytes
.$files
tablespec_id, partition, sort_order_id, readable_metrics columns are missing.
$refs
tableTrino supports all columns in Spark.
References: