-
Notifications
You must be signed in to change notification settings - Fork 89
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
Query endpoint for SnowparkTableDataset
#721
Comments
This seems very specific to the |
After the discussion with the team, we've decided to look through similar datasets to check if it makes sense to extend their configuration with a query endpoint. As a potential solution to this issue, we can consider adding |
@ElenaKhaustova @merelcht I'm going to move this into a new issue for tracking purposes (just found it while searching the issue tracker for Ibis). |
Description
SnowparkTableDataset
dataset configuration does not have a query endpoint, so running database-level SQL queries is not possible at the catalog level. Thus users have to make it at the level of the database - at first, execute query to filter data and only after run a Kedro pipeline. Users expect it to work similar toSQLQueryDataset
andGBQQueryDataset
where they have a query endpoint.https://docs.kedro.org/projects/kedro-datasets/en/kedro-datasets-3.0.1/api/kedro_datasets.snowflake.SnowparkTableDataset.html
We propose to:
SQL
queries withIbis
in such cases instead: https://kedro.org/blog/sql-data-processing-in-kedro-ml-pipelines.Context
https://docs.kedro.org/projects/kedro-datasets/en/kedro-datasets-3.0.1/api/kedro_datasets.pandas.SQLQueryDataset.html
https://docs.kedro.org/projects/kedro-datasets/en/kedro-datasets-3.0.1/api/kedro_datasets.pandas.GBQQueryDataset.html
The text was updated successfully, but these errors were encountered: