[X] I have searched the existing issues, and I could not find an existing issue for this bug
Current Behavior
base_location_subpath should be an optional parameter that the user provides as an additional scoping mechanism. Instead, it is currently responsible for base generation creation.
Expected Behavior
Dynamic iceberg tables should render ddl using the _dbt/schema/relation name base location when no base_location_subpath is provided.
Steps To Reproduce
in an iceberg-enabled snowflake, write a dynamic iceberg table code artifact with no base_location_subpath param
Is this a new bug in dbt-snowflake?
Current Behavior
base_location_subpath
should be an optional parameter that the user provides as an additional scoping mechanism. Instead, it is currently responsible for base generation creation.Expected Behavior
Dynamic iceberg tables should render ddl using the
_dbt/schema/relation name
base location when nobase_location_subpath
is provided.Steps To Reproduce
base_location_subpath
paramdbt run
Relevant log output
No response
Environment
Additional Context
No response