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
{{ message }}
This repository has been archived by the owner on Sep 23, 2024. It is now read-only.
Describe the bug
I created a file format called PROD_RAW.PUBLIC.MELTANO_TARGET_SNOWFLAKE. However, I'm trying to load data into a development database called DEV_STERLINGP_RAW. I'm getting a "file format not found" error when I try to execute a pipeline, despite my user having USAGE permissions on this target.
To Reproduce
Steps to reproduce the behavior:
Create file format in a database that is different from the target database
Run the target
See error target_snowflake.exceptions.FileFormatNotFoundException: Named file format not found: PROD_RAW.PUBLIC.MELTANO_TARGET_SNOWFLAKE
Expected behavior
Target should be able to find file formats in different databases.
Your environment
Version of target: v2.2.0
Version of python 3.8
Additional context Looks like the target is stripping the database and schema name when it's looking for the file format. Presumably the connection is using the target database as default. Fixing this should be as simple as getting the db.schema and using SHOW FILE FORMATS LIKE '{file_format_name}' in schema {file_format_db_schema}
The text was updated successfully, but these errors were encountered:
Describe the bug
I created a file format called
PROD_RAW.PUBLIC.MELTANO_TARGET_SNOWFLAKE
. However, I'm trying to load data into a development database calledDEV_STERLINGP_RAW
. I'm getting a "file format not found" error when I try to execute a pipeline, despite my user having USAGE permissions on this target.To Reproduce
Steps to reproduce the behavior:
target_snowflake.exceptions.FileFormatNotFoundException: Named file format not found: PROD_RAW.PUBLIC.MELTANO_TARGET_SNOWFLAKE
Expected behavior
Target should be able to find file formats in different databases.
Your environment
Additional context
Looks like the target is stripping the database and schema name when it's looking for the file format. Presumably the connection is using the target database as default. Fixing this should be as simple as getting the db.schema and using
SHOW FILE FORMATS LIKE '{file_format_name}' in schema {file_format_db_schema}
The text was updated successfully, but these errors were encountered: