Remove leading period from info logging about dbt-spark HOT 3 CLOSED

I believe the culprit is get_node_representation.

Spark's profile.yml config requires the user to specify schema. A user can optionally also specify database, which is meaningless, because schema == database in Spark. I confirmed that I see this issue when I specify only schema in my profile, and the leading period disappears when I also specify database with the same value as schema. This is a bit surprising, since we set database = schema as a _post_init on the credentials object.

I'm not sure if there's a way to override get_node_representation for Spark, since it's a class method on ModelRunner, not BaseAdapter.

This leads me to think there could be more serious functional issues related to the database model configs that I haven't had a chance to test yet.

from dbt-spark.

After more testing, I confirmed this is not an issue with the profile configs, but with relations themselves. Given a profile that sets schema: my_schema_name, this error disappears if I set the following in dbt_project.yml:

models:
  my_project:
    database: my_schema_name

At the same time, if I set it to be something else entirely:

models:
  my_project:
    database: not_the_same

dbt will print out

1 of 15 START table model not_the_same.my_schema_name.table_model..... [RUN]

But it will actually just attempt to create a table located at the namespace my_schema_name.table_model.

I'm going to open a separate issue laying out how I think we should reconcile custom schemas and databases, likely for 0.17.0.

from dbt-spark.

Fixed by dbt#2450. We should enjoy nicer-looking output in 0.17.0

from dbt-spark.