-
Notifications
You must be signed in to change notification settings - Fork 93
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
Question about your architecture #17
Comments
Hi @cesaraugusto98, Yes, both bronze and silver schemas are managed by Spark (one logical db). The gold schema is managed by Postgres. You need to run CTAS queries that read data from Iceberg and store data in Postgres when moving data from silver to gold. Trino is much better for such federated queries. |
Hi @zsvoboda. How about using only Trino and a data lake framework (Delta, Iceberg) for everything (bronze, silver, gold). Or am I missing something that only Spark would be capable of? |
This is certainly an option. However, Spark is more resilient for larger datasets (10s of billions of rows). I was running into memory issues with Trino myself. |
This has been my issue as well. For trino/presto - it was a memory hog
compared to spark. Also, remember that spark is based on
mappers/reducers - larger data sets are basically the reason for it's
existence.
Kind regards,
James Clayton
…On 2/20/2023 3:40 AM, Zdenek Svoboda wrote:
This is certainly an option. However, Spark is more resilient for larger
datasets (10s of billions of rows). I was running into memory issues
with Trino myself.
—
Reply to this email directly, view it on GitHub
<#17 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABEEW5OY63W33FJI4QNICKDWYMUWVANCNFSM6AAAAAAU77FVXY>.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Hi @zsvoboda Why do you use DBT + Spark between bronze layer to silver layer; and only uses dbt+trino moving from Silver to Gold? Is there any specific reason?
The text was updated successfully, but these errors were encountered: