PushdownDeclined
One node the compiler refused to push down to its source, and why.
Used as Input
0
functions accept this type
Used as Output
0
functions return this type(+2 nested)
Type Definition
83 nested items
struct— One node the compiler refused to push down to its source, and why.
node*:String— The node id, as the blueprint names it.
reason*:RejectReason— Why a mapping could not be compiled to a view. Every variant names something the emitter
variant 1:struct— A
Target::Event with no id expression: the extractor mints a fresh UUID per row, avariant 2:struct— A type name is read from the data and the catalog supplies no domain for the column it
variant 3:struct— A column domain has more distinct values than
MAX_TYPE_DOMAIN, so a per-type shapevariant 4:struct— A type name collides with one of the relations the emitter itself defines.
variant 5:struct— A mapping reads a node that is not declared.
variant 6:struct— A node's column shape could not be resolved, typically because of an unknown source table.
variant 7:struct— The node graph contains a cycle, so there is no order in which to emit it.
variant 8:struct— A node has no columns, and SQL has no zero-column
SELECT.variant 9:struct— A
Union node with no inputs.variant 10:struct— An expression reads a column the node does not have.
variant 11:struct— The catalog's
col_type for a column maps to novariant 12:struct— A
Float or Timestamp column, which has novariant 13:struct— A column whose
Value::display_string(super::value::Value::display_string) a SQL castvariant 14:struct— A timestamp is parsed by a
chrono cascade that is not translated to SQL.variant 15:struct— A join key column's declared kind is unknown, so whether the extractor's kind-tagged keys
variant 16:struct— A regular expression does not compile at all.
variant 17:struct— A
Template has an unterminated or empty placeholder, which makes it None for everyvariant 18:struct— An attribute's declared type is not the source column's kind, and the coercion
variant 19:struct— A mapping whose type name comes from the data declares an attribute that another mapping
variant 20:struct— A relation view's dependencies on other relation views form a cycle, so no order exists
variant 21:struct— The blueprint does not
validate(super::validate::validate) against the catalog, soExample JSON Value
json
{
"node": "example",
"reason": {
"SynthesizedId": {
"field": "example"
}
}
}