21–30 of 70 posts
Earlier quoted context omitted.
Check out this PR. I believe we may have tackled this one but you'd need to try it out on Trino: https://github.com/trinodb/trino/pull/1415
Hooray! Yet another data point for Trino > Presto as far as I'm concerned ;^)
Full disclosure I work at Starburst.
Big shout out to Brian Olsen from the Trino community (and Starburst) for helping the Trino community be successful - https://github.com/bitsondatadev - https://www.linkedin.com/in/bitsondatadev/ I recommend the Trino Slack for people not already in it: https://trino.io/slack.html
If you want to get started with Trino, here's a repo I created to do so: https://github.com/bitsondatadev/trino-getting-started
I do the support for my department's trino cluster. We move ~1tb (and growing) in ETL jobs and support interactive queries for the data scientists/analysts. It would be super good if you guys added big query write support. Its really annoying to have to run a hive cluster in google to act as a proxy for this.
But, yes, we do plan to add that eventually after ironing out all the kinks. See https://github.com/trinodb/trino/pull/13094
Can Trino be used as a Snowflake replacement? How is the query speed compared to Snowflake?
https://trino.io/blog/2022/06/30/trino-summit-call-for-speak...
Earlier quoted context omitted.
Hooray! Yet another data point for Trino > Presto as far as I'm concerned ;^)
If you want to try an SaaS Athena alternative that's backed by Trino you can check out Starburst Galaxy: https://www.starburst.io/platform/starburst-galaxy/ Full disclosure I work at Starburst.
Guy who goes by the name of "Randgalt" online builds some great Java libraries and works there too I believe.
BTW, purely curiosity, I compared Trino with Presto from OSS point of view (https://ossinsight.io/analyze/prestodb/presto?vs=trinodb%2Ft...), both communities are still popular but Trino seems more active than Presto now. I also wonder if two communities may reunion someday again to really boost its impact (comparing to Spark community).
I recently had to write SQL query generation for AWS Athena, which is based off Presto 0.217 It turns out that the dialect doesn't support LATERAL joins with a LIMIT in them. The below query only works if you remove the LIMIT clause. https://i.stack.imgur.com/rdB1s.png This makes saying things like "Fetch all artists where ..., for each artist fetch their first 3 albums where ..., and for each album fetch the top 10…
AWS Athena: selling a buggy, old, stale copy of someone else's work (Presto / Trino) for high prices and getting away with it because you control the platform. If that's not peak Amazon, I don't know what is.
Trino vs ClickHouse, can anyone tell from experience how those two compare?
Realtime is generally more expensive to run as you process every individual row as it comes, batch is when you can deal with minute latency and want to handle a lot of data in chunks.
Trino is also a query engine rather than a database and it connects to many different systems: https://trino.io/docs/current/connector.html
It also happens to connect to Clickhouse and it's very common that people will use Trino to query clickhouse realtime data and join it with data in big query, an object store data lake, or Snowflake: https://trino.io/docs/current/connector/clickhouse.html