DM-55338: Update cloud functions for staging of update records#14
Merged
Conversation
andy-slac
approved these changes
Jul 21, 2026
The updates parquet file can now be processed similarly to the regular table data, instead.
JeremyMcCormick
force-pushed
the
tickets/DM-55338
branch
from
July 21, 2026 22:28
9c35524 to
d643daf
Compare
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
2 participants
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.
This changes the staging of update records so they are handled like the procedure for regular table data: ee29c77
There are also some minor updates to the logging, as well as an update to how the updatable fields are handled using an enum.