Skip to content

Deprecation warning for query_tags and view_update_via_alter in dbt-core #1540

Description

@kimkoningscz

Describe the bug

I get the following warnings since upgrading my dbt-core and dbt-databricks:

13:04:35  [WARNING][CustomKeyInConfigDeprecation]: Deprecated functionality
Custom key `+query_tags` found in `config` at path
`ssda_declareren_dbt.+query_tags` in file `C:\Users\629231\Git
projects\ssda-declareren\projects\dbt\src\dbt_project.yml`. Custom config keys
should move into the `config.meta`.

This seems in line with #1302

Steps To Reproduce

When running a model I get the warning of deprecated functionality. See screenshot below. I didn't have the warnings a few days ago when I was still running on dbt-core 1.11.2 with registered adapter: databricks=1.11.4.

When running with dbt-core 1.11.8 and dbt-databricks 1.11.8 I do get the warnings and I see in the release notes of dbt-core that they added warnings but it seems like the dbt-databricks configs are note added.

Release note:
https://github.com/dbt-labs/dbt-core/releases?page=2
Image

Warnings I get:
Image

With the following config:

Image

Expected behavior

No warnings. In line with #1302 it seems dbt-databricks specific configs are not recognized and therefore warnings are given.

Screenshots and log output

Image

System information

The output of dbt --version:

$ dbt --version
WARNING:thrift.transport.sslcompat:using legacy validation callback
Core:
  - installed: 1.11.8 
  - latest:    1.11.11 - Update available!

  Your version of dbt-core is out of date!
  You can find instructions for upgrading here:
  https://docs.getdbt.com/docs/installation

Plugins:
  - databricks: 1.11.8 - Update available!
  - spark:      1.10.1 - Update available!

  At least one plugin is out of date with dbt-core.
  You can find instructions for upgrading here:
  https://docs.getdbt.com/docs/installation

Additional context

Add any other context about the problem here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingexternal issueAn issue that is better addressed by a different project

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions