small fix: meta under config in dbt_run_results

[haritamar]

Summary by CodeRabbit

• New Features
  • No user-facing changes.
• Refactor
  • Relocated deprecated column metadata into the model’s configuration for consistency with current conventions. Behavior and outputs remain unchanged.
• Chores
  • Aligned metadata structure to improve maintainability and clarity. Existing column definitions remain the same.

[linear]

ELE-4962 dbt-fusion compilation error fix

[coderabbitai]

Walkthrough

Relocated the deprecated_columns metadata for the dbt_run_results model from a top-level meta block to config.meta within models/run_results.yml. The compiled_sql field definition remains unchanged. No functional logic or additional fields were modified.

Changes

Cohort / File(s)	Summary
Model metadata relocation models/run_results.yml	Moved meta.deprecated_columns to config.meta.deprecated_columns for the dbt_run_results model; compiled_sql entry unchanged (name, data_type, description).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I nudged a note from shelf to drawer,
A tiny tweak—no less, no more.
Compiled script still shines the same,
Just labeled under config’s name.
Thump-thump! my paws approve the sort—
Metadata hops to its new port. 🐇✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 2579747 and 561b61f.

📒 Files selected for processing (1)

• models/run_results.yml (1 hunks)

🧰 Additional context used

🧠 Learnings (4)

📓 Common learnings

Learnt from: haritamar
PR: elementary-data/dbt-data-reliability#825
File: models/run_results.yml:139-145
Timestamp: 2025-07-15T19:31:54.689Z
Learning: In dbt-fusion (dbt 2.0+), the `meta` configuration for models should be nested under the `config` block (i.e., `config: meta:`), not as a top-level `meta` key. This is different from traditional dbt where `meta` was a sibling of `config`.

Learnt from: haritamar
PR: elementary-data/dbt-data-reliability#825
File: integration_tests/dbt_project/models/exposures.yml:18-24
Timestamp: 2025-07-15T19:31:02.744Z
Learning: For dbt exposures, the `meta` configuration can be nested under the `config` block (i.e., `config: meta:`). This is a valid and supported pattern in modern dbt versions, contrary to some older documentation that suggested only top-level `meta` blocks were supported.

Learnt from: haritamar
PR: elementary-data/dbt-data-reliability#825
File: integration_tests/dbt_project/models/exposures.yml:18-24
Timestamp: 2025-07-15T19:31:02.744Z
Learning: For dbt exposures in v1.10+, the `meta` configuration should be nested under the `config` block (i.e., `config: meta:`), not as a top-level `meta` key. This is the officially documented and supported format for exposures.

Learnt from: haritamar
PR: elementary-data/dbt-data-reliability#825
File: integration_tests/dbt_project/models/exposures.yml:39-44
Timestamp: 2025-07-15T19:30:40.238Z
Learning: In dbt exposures, metadata should be defined under `config.meta` not directly under `meta`. The correct schema for exposures is to nest the meta field under config according to official dbt documentation.

📚 Learning: 2025-07-15T19:31:54.689Z

Learnt from: haritamar
PR: elementary-data/dbt-data-reliability#825
File: models/run_results.yml:139-145
Timestamp: 2025-07-15T19:31:54.689Z
Learning: In dbt-fusion (dbt 2.0+), the `meta` configuration for models should be nested under the `config` block (i.e., `config: meta:`), not as a top-level `meta` key. This is different from traditional dbt where `meta` was a sibling of `config`.

Applied to files:

• models/run_results.yml

📚 Learning: 2025-07-15T19:31:02.744Z

Learnt from: haritamar
PR: elementary-data/dbt-data-reliability#825
File: integration_tests/dbt_project/models/exposures.yml:18-24
Timestamp: 2025-07-15T19:31:02.744Z
Learning: For dbt exposures in v1.10+, the `meta` configuration should be nested under the `config` block (i.e., `config: meta:`), not as a top-level `meta` key. This is the officially documented and supported format for exposures.

Applied to files:

• models/run_results.yml

📚 Learning: 2025-07-15T19:31:02.744Z

Learnt from: haritamar
PR: elementary-data/dbt-data-reliability#825
File: integration_tests/dbt_project/models/exposures.yml:18-24
Timestamp: 2025-07-15T19:31:02.744Z
Learning: For dbt exposures, the `meta` configuration can be nested under the `config` block (i.e., `config: meta:`). This is a valid and supported pattern in modern dbt versions, contrary to some older documentation that suggested only top-level `meta` blocks were supported.

Applied to files:

• models/run_results.yml

🔇 Additional comments (1)

models/run_results.yml (1)

139-144: Correctly moved deprecated_columns under config.meta (dbt-fusion compliant).

This aligns with the dbt-fusion requirement to nest meta under config. Indentation and structure look valid, and the deprecated column details were preserved.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch ele-4962-dbt-fusion-compilation-error-fix

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

👋 @haritamar
Thank you for raising your pull request.
Please make sure to add tests and document all user-facing changes.
You can do this by editing the docs files in the elementary repository.