Skip to content
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

Support joins with query pushdown in the SQL API #8483

Open
igorlukanin opened this issue Jul 17, 2024 · 2 comments
Open

Support joins with query pushdown in the SQL API #8483

igorlukanin opened this issue Jul 17, 2024 · 2 comments
Assignees
Labels
api:sql Issues related to SQL API enhancement New feature proposal Roadmap: Q1 FY'26 (Feb-Apr 2025)

Comments

@igorlukanin
Copy link
Member

igorlukanin commented Jul 17, 2024

Currently, joins between cubes are not supported in queries to the SQL API if query pushdown is enabled. We would like to support joins and lift that limitations.

It's currently planned for February 2025.

@igorlukanin igorlukanin added enhancement New feature proposal api:sql Issues related to SQL API labels Jul 17, 2024
@igorlukanin igorlukanin changed the title Supports joins with query pushdown in the SQL API Support joins with query pushdown in the SQL API Jul 17, 2024
@pauldheinrichs
Copy link

pauldheinrichs commented Sep 19, 2024

Hello!

@igorlukanin Just a thought I had this AM, with the recent release of v36 rollup_joins are unblocked by joining different datasources with different driver Factory syntax. 💚 (thank you all for that)


A feature that i have absolutely no idea the feasibility would be genuinely amazing on the roadmap of this current epic. If cube was capable of auto joining different datasources (providing a rollup existed) IE: removing the need for the rollup_join pre-definitions of which rollups should be referenced when joining.

IE the following query

select user_id from mysql.users
LEFT JOIN user_id from redshift.users

and the understanding that redshift.users has a pre-build pre-aggregation with a dimension on user_id

cube is capable of planning that sql to some capacity? 🤷

Anywho - just a thought.

@igorlukanin
Copy link
Member Author

select user_id from mysql.users LEFT JOIN user_id from redshift.users

@pauldheinrichs I think this is outside of the current scope of what we feel Cube should be capable of. This is the territory of query engines and I feel like Athena/Trino/Presto/DuckDB would do a much better job joining data across different data sources than Cube, given how much effort they have invested into this feature. And since Cube supports all of them, then it looks like reimplementing this in Cube might be redundant.

So, I guess, it's fair to not expect anything like cross-data source joins (without pre-aggregations) to appear in Cube.

(Just to clarify, the feature described in this ticket relates to joins in SQL API queries—that can be resolved against a single data source.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api:sql Issues related to SQL API enhancement New feature proposal Roadmap: Q1 FY'26 (Feb-Apr 2025)
Projects
None yet
Development

No branches or pull requests

3 participants