ExtractionError
Why
recorded in
Serializable but not deserializable: some variants carry
deserializer can manufacture), so this only ever crosses a bindings boundary outbound.
extract(super::extract::extract) could not run at all, or a non-fatal problemrecorded in
ExtractionReport::errors while it did.Serializable but not deserializable: some variants carry
&'static str fields (a borrow nodeserializer can manufacture), so this only ever crosses a bindings boundary outbound.
Used as Input
0
functions accept this type
Used as Output
0
functions return this type(+2 nested)
Type Definition
159 nested items
enum(11 variants)— Why
extract(super::extract::extract) could not run at all, or a non-fatal problemvariant 1:struct— The blueprint failed
validate(super::validate::validate), so extract refuses to runvariant 2:struct— A
Source node names a source_id with no entry in the providers map extract wasvariant 3:struct— A predicate's or split's regular expression failed to compile. Fatal.
validate checksvariant 4:struct— A
Join's on clause named a key column that its input's rows do not carry. Fatal:variant 5:struct— A
RowProvider(super::provider::RowProvider) call failed. Fatal: the rows a mappingvariant 6:struct— An
ExtractionSink(super::sink::ExtractionSink) call failed for a reason other than avariant 7:struct— Two mappings, or two rows, produced the same rendered id under two different types.
variant 8:struct— Two mappings declared the same attribute of the same entity type under different value
variant 9:struct—
on_duplicate_object: Error fired: id had already been added by mapping. Non-fatal.variant 10:struct—
on_missing_endpoint: Error fired: endpoint named id, which could not be resolved.variant 11:struct—
on_missing_endpoint: Error fired for a sink that answeredExample JSON Value
json
{
"Invalid": [
{
"found": 1,
"supported": 1,
"type": "unsupported-version"
}
]
}