OptionalbudgetThe ID of the budget policy used to attribute the serverless compute cost of this materialization. If not specified, a default budget policy may be applied.
OptionalcronOptionaldestinationDestination for writing feature values to an offline Delta table.
Destination for writing feature values to an online Lakebase table.
OptionalfeatureThe full name of the feature in Unity Catalog.
OptionalisTrue if this is an online materialized feature. False if it is an offline materialized feature.
OptionallastThe timestamp when the pipeline last ran and updated the materialized feature values. If the pipeline has not run yet, this field will be null.
OptionallatestName of the latest backfill operation on this materialized feature. Format: operations/{operation_id}.
OptionalmaterializedServer-assigned unique identifier for the materialized feature.
OptionalpipelineThe schedule state of the materialization pipeline. Hidden from GraphQL: being deprecated, so not exposed to Catalog Explorer.
OptionaltableThe fully qualified Unity Catalog path to the table containing the materialized feature (Delta table or Lakebase table). Output only.
OptionaltagsCustom tags to associate with this materialization. They are applied to the materialization job (for batch features) or pipeline (for streaming features) and forwarded to the underlying compute as cluster tags, so materialization cost can be attributed in the billing system tables. These tags apply only to the materialization compute; they are not applied to the Unity Catalog Feature resource itself, whose tags are managed separately through the Unity Catalog tagging API. A maximum of 25 tags is supported; keys and values are subject to the same limitations as cluster tags.
OptionaltriggerThe trigger configuration for the materialization pipeline.
A cron-based schedule trigger for the materialization pipeline.
A trigger that fires when the upstream source table changes.
The Structured Streaming trigger mode used for materialization. Real-time mode (RTM) targets sub-second latency for operational workloads; micro-batch mode (MBM) favors cost efficiency for ETL and analytics workloads.
A materialized feature represents a feature that is continuously computed and stored.