Touch publications are kind of a perfect fit for expanded specs in user-initiated publications. Expanded specs are never modified by the publication, and it's annoying to add publication specs for things that users haven't intended to publish. Using is_touch: true on expanded specs prevents the creation of unnecessary publication specs. It also avoids unnecessary modification of last_pub_id, so there will be less chance of ExpectPubIdMismatch errors. The touched specs are still validated, which serves the original purpose of spec expansion.
Resolves #1643
Workflow steps:
Create a capture into one or more collections, and a materialization.
Publish a change to only the collection using flowctl
Observe that the last_pub_id of the capture and materialization have not changed, but the last_build_id has
No publication_specs are added for the capture and materialization, only the collection
Notes for reviewers:
This is a follow up change from #1629 , which added the "touch" capability. I wanted to break this out as a separate PR just to limit the scope of changes in any one deployment.
Description:
Touch publications are kind of a perfect fit for expanded specs in user-initiated publications. Expanded specs are never modified by the publication, and it's annoying to add publication specs for things that users haven't intended to publish. Using
is_touch: true
on expanded specs prevents the creation of unnecessary publication specs. It also avoids unnecessary modification oflast_pub_id
, so there will be less chance ofExpectPubIdMismatch
errors. The touched specs are still validated, which serves the original purpose of spec expansion.Resolves #1643
Workflow steps:
last_pub_id
of the capture and materialization have not changed, but thelast_build_id
haspublication_specs
are added for the capture and materialization, only the collectionNotes for reviewers:
This is a follow up change from #1629 , which added the "touch" capability. I wanted to break this out as a separate PR just to limit the scope of changes in any one deployment.
This change is