Philipp Leufke comments

Results 22 comments of


                                            Philipp Leufke

feat: a native SQLAlchemy dialect for Superset

Sounds interesting! Could you provide some possible Use Cases? Is this a step towards paving the path to a LookML-like modeling layer?

feat: a native SQLAlchemy dialect for Superset

Thanks for the explanation. I wonder, if all tables of a query built by explore are accessible by the same DB connection -- e.g. different DBs, but the same Snowflake...

feat(ingest): profiling - allow/deny SQL columns by type

Eagerly waiting for this PR :-)

[SQL Profiles] Feature request: deny certain data types

This PR will probably fix it: #4328

Feature/table iceberg

> a drop statement of iceberg table lead to deleting all the data in S3 What do you mean by "all data"? Does this imply any risk of losing data...

Feature/table iceberg

Thanks for clarifying 😊 I know what DROP means, but with your initial description I got confused

Feature/table iceberg

I see. Thanks again for explaining.

Support s3_data_dir and s3_data_naming

I'd also be interested in having this PR merged.

[CT-278] [Feature] Allow meta property to be accessible at compile time

I can only second this feature request. We are looking for a solution which would allow us to reuse as much as possible from existing marts' models for new marts...

Add Jinja templating to SQL runner

Don't close, please