Bigint types in schema

[GuyEshdat]

Summary by CodeRabbit

• Bug Fixes

  • Updated alert freshness description text to display more explicit update cadence information.

• Improvements

  • Increased data capacity for tracking rows affected and failures to support larger datasets.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[github-actions]

👋 @GuyEshdat
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.

[coderabbitai]

Walkthrough

Two focused changes: updating a freshness description message phrasing in an anomaly detection macro and upgrading data type definitions from int to bigint for two columns in a dbt run results model.

Changes

Cohort / File(s)	Change Summary
Freshness Description Update macros/edr/alerts/anomaly_detection_description.sql	Modified freshness_description text phrasing from "X hours ago" format to "which is X hours without updates (only full buckets are considered)" for clearer update cadence communication
Data Type Upgrades models/run_results.yml	Updated rows_affected and failures column data types from int to bigint in the dbt_run_results model

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Straightforward text message updates and data type changes with no logic or control flow modifications
• Changes are isolated to configuration and messaging concerns

Possibly related PRs

• made the description of the anomaly test more accurate #883 — Modifies the same macro (macros/edr/alerts/anomaly_detection_description.sql) with identical freshness_description phrasing updates

Suggested reviewers

• ofek1weiss

Poem

🐰 Fresh updates and types refined,
From hours past to futures aligned,
Bigger buckets, clearer words we find,
The anomaly path now more designed! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Bigint types in schema' directly aligns with the primary changes in the pull request, which update data types from int to bigint for two columns in the run_results model.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch bigint-types-in-schema

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• 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 15c3290 and f1cb120.

📒 Files selected for processing (2)

• macros/edr/alerts/anomaly_detection_description.sql (1 hunks)
• models/run_results.yml (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (14)

• GitHub Check: test (latest_official, postgres) / test
• GitHub Check: test (fusion, redshift) / test
• GitHub Check: test (fusion, databricks_catalog) / test
• GitHub Check: test (latest_official, trino) / test
• GitHub Check: test (latest_official, snowflake) / test
• GitHub Check: test (latest_pre, postgres) / test
• GitHub Check: test (latest_official, bigquery) / test
• GitHub Check: test (latest_official, athena) / test
• GitHub Check: test (latest_official, redshift) / test
• GitHub Check: test (fusion, snowflake) / test
• GitHub Check: test (fusion, bigquery) / test
• GitHub Check: test (latest_official, databricks_catalog) / test
• GitHub Check: test (latest_official, clickhouse) / test
• GitHub Check: test (latest_official, dremio) / test

🔇 Additional comments (2)

macros/edr/alerts/anomaly_detection_description.sql (1)

12-14: Clearer freshness anomaly description message.

The rewording improves clarity by explicitly stating that only full buckets are considered in freshness calculations, helping end users better understand the metric.

models/run_results.yml (1)

199-201: Verify schema migration strategy for type changes.

Changing rows_affected and failures from int to bigint in an incremental dbt model requires careful consideration. In dbt, schema definition changes don't automatically migrate existing table columns—this typically requires either separate DDL execution or documented migration steps.

Confirm that:

• A migration strategy exists for existing deployments (ALTER TABLE or backfill approach)
• Downstream consumers and dependencies have been assessed
• The motivation is documented (overflow risk vs. precautionary change)

Also applies to: 211-213

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}