This website uses cookies to ensure you get the best experience.
Learn more.
A large fact table joins a genuinely small dimension that fits safely in executor memory. Which optimization may avoid a costly large shuffle?
Published
- Force a Cartesian product
- Collect both tables to the driver
- A broadcast join for the small side
- Broadcast the entire large fact table blindly
Comments — 0
Sign in to comment