You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, database and schema need to be specified in all SQL files used by aql.render(); otherwise, Astro (0.5.1) raises the following exception:
File "/usr/local/lib/python3.9/site-packages/astro/utils/snowflake_transform.py", line 30, in _handle_table
return t.database + "." + t.schema + "." + t.table_name
TypeError: unsupported operand type(s) for +: 'NoneType' and 'str'
This means that the user has to specify the database and schema in all upstream and downstream tasks.
Acceptance criteria
Evaluate the possible ways of solving this problem, and chose an approach. Some possible solutions could involve using a configuration file, an environment variable, or inheriting from the upstream task.
Astro users are able to use aql.render without specifying database and schema headers in all SQL files.
* Fix inheritance from partially defined output tables #124
This fixes an issue where the sql decorator doesn't pass on credentials
for partially defined or undefined output tables.
* also ensures that partial tables are handled for dataframe functions
* cleanup
* cleanup
* Fix inheritance from partially defined output tables #124
This fixes an issue where the sql decorator doesn't pass on credentials
for partially defined or undefined output tables.
* also ensures that partial tables are handled for dataframe functions
* cleanup
* cleanup
Context
At the moment,
database
andschema
need to be specified in all SQL files used by aql.render(); otherwise, Astro (0.5.1) raises the following exception:This means that the user has to specify the database and schema in all upstream and downstream tasks.
Acceptance criteria
aql.render
without specifyingdatabase
andschema
headers in all SQL files.The text was updated successfully, but these errors were encountered: