dbt-labs/dbt-core · error
type should be accessible
Error message
type should be accessible
What it means
Test-only assertion in test_constraints_to_jinja_exposes_object_attributes: the first constraint yielded by iterating unset_constraints must expose a `type` attribute readable from Jinja. Fires only if individual constraint objects stop exposing their type.
Solutions
- Ensure each constraint in the Jinja wrapper exposes a `type` attribute
- Check the per-constraint object implementation used by to_jinja
- Treat failure as a regression in Jinja attribute exposure
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at crates/dbt-adapter/src/relation/databricks/config/components/constraints.rs:958 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of dbt-labs/dbt-core@0267ce9170 (2026-09-07).
Data as JSON: /api/errors/b9f0b030e2c2d064.
Report an issue: GitHub.
Appendix: source
Thrown at crates/dbt-adapter/src/relation/databricks/config/components/constraints.rs:958
let constraints = Constraints::new(
IndexSet::new(),
IndexSet::new(),
IndexSet::new(),
IndexSet::from([pk]),
);
let jinja_val = constraints.to_jinja();
let unset = jinja_val
.get_attr("unset_constraints")
.expect("unset_constraints should be accessible");
let mut iter = unset
.try_iter()
.expect("unset_constraints should be iterable");
let constraint_val = iter.next().expect("should have one constraint");
let type_val = constraint_val
.get_attr("type")
.expect("type should be accessible");
assert_eq!(type_val.as_str(), Some("primary_key"));
let name_val = constraint_val
.get_attr("name")
.expect("name should be accessible");
assert_eq!(name_val.as_str(), Some("pk_id"));
let render_val = constraint_val
.get_attr("render")
.expect("render should be accessible");
assert!(
!render_val.is_undefined(),
"render should be a callable function"
);
}
#[test]
fn test_constraint_normalization_and_diff() {View on GitHub (pinned to 0267ce9170)