Hacker News new | past | comments | ask | show | jobs | submit login

One example is that in Presto, joins assume that left (IIRC) table is the big one you stream, and the right one is the small one you hash. One of the newer features was that in some cases, the optimizer is able to ignore the SQL order and correctly pick which table to hash and which one to stream.



Isn't that just basic table/index statistics to know which table is the smallest?


Not if you're joining on a filtered table or a result of another join.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: