Update cloud instance type history ingestion process. #2160
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 PR does two things.
A couple of notes.
instance_type_change_flag.json- usesLAGto set a 1 or 0 to denote if that row is where a change in configuation occurredinstance_type_config_group.json- uses theis_changecolumn frommodw_cloud.instance_type_change_flagand a window function to set a mark each different configuration for an instance typeinstance_type_grouped.json- Groups all instance types using the config group to get a MIN start time for each configuration. Uses MAX on display and description columns to make it compliant with the ONLY_FULL_GROUP_BY mode. Since these column should have the same value within each group it should always have the correct value.instance_type_staging.json- Sets the end time for each instance type configuration using LEAD.CloudInstanceTypeStateIngestoringestor and it's associated test were deleted because they are no longer needed.Tests performed
Tested in docker
Checklist: