Add new ArchiveSize and FileSize fields #158
Merged
Conversation
This file contains 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
cristinaleonr
approved these changes
Jun 6, 2023
complete! 1 of 1 approvals obtained
|
Thank you! |
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.
This change adds the
ArchiveSizeandFileSizefields to the synthetic, standard-column definition of the static web100 transformation.The standard column version of the web100 schema is not actively managed by the current etl parser schema. So, these fields cannot be added automatically, as they are for all other datatypes.
Unfortunately, the unified views use
UNION ALLacross the the ndt7, ndt5, and legacy web100 tables. When the web100 schema is different, it causes theUNION ALLto fail.This change corrects the schema for web100, but it must be applied manually.
This change is