Thanks for sharing the additional tests @dbxenthusiast. These results narrow the problem down quite a bitSince:Storage Credential validation succeeds,the External Location works from classic compute,the S3 bucket policy has no restrictive VPC/IP cond...
Thanks @Louis_Frolio , this really helps connect the different pieces of the discussion.I especially like the idea of treating a full refresh as a planned operational event rather than redesigning the whole ingestion architecture, especially since th...
Great explanation! I'd add one important consideration from a cross-cloud architecture and data governance perspective.Before implementing OpenSharing with AWS Glue, I would clarify exactly what the source team means by "no replication or ingestion i...
Thanks for clarifying! It sounds like you've already made a good architectural decision by separating workloads based on their refresh requirements.Since continuous ingestion was too expensive, I wouldn't recommend switching approaches without first ...
Great discussion. I think there is another architectural consideration worth exploring before changing the gateway configuration.Does the 15-minute freshness requirement apply to all 80 tables, or only to a subset of business-critical tables?If only ...
