Fix: allow operational metadata to be disabled on MV's and update docs#21
Open
Fix: allow operational metadata to be disabled on MV's and update docs#21
Conversation
1 task
haillew
reviewed
Feb 24, 2026
|
|
||
| Disabling Operational Metadata in a Dataflow Spec | ||
| ------------------------------------------------- | ||
| You can disable operational metadata for a dataflow spec or for a target table. |
Collaborator
There was a problem hiding this comment.
just to make it super clear would it be better to update this to "You can disable operational metadata at a dataflow spec level or for specific target tables" or something like that to make it clear it's two different scopes not two separate items
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated docs for operational metadata and added fix to properly handling the disabling of operational metadata for MV's by either of the following methods:
Disabling the feature at Spec Level:
{
"dataFlowId": "feature_materialized_views",
"dataFlowGroup": "feature_samples",
"dataFlowType": "materialized_view",
"features": {
"operationalMetadataEnabled": false
}
}
Disable at MV level using the configFlags setting:
"targetDetails": {
"table": "customer_address",
"tableProperties": {
"delta.autoOptimize.optimizeWrite": "true",
"delta.autoOptimize.autoCompact": "true"
},
"partitionColumns": ["country_code"],
"schemaPath": "schemas/customer_address.json",
"configFlags": ["disableOperationalMetadata"]
},