[COST-4936] Add memory and operating system columns to aws trino table #5071
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.
Jira Ticket
COST-4936
Description
This change will:
product_operatingsystem
column to theaws_line_items
table in trinoproduct_memory
andproduct_operatingsystem
columns toaws_line_items_daily
table in trinoTesting
Checkout main branch
Restart Koku and test aws source
In the trino shell:
i. see that you have
aws_line_items
andaws_line_items_daily
tablesii. see that the new columns are missing in the respective tables
Checkout this branch
Run
python scripts/cji_scripts/migrate_trino.py
to drop the aws line tables. Verify by repeating step3.i
to see that those tables are removed.Generate a new report for your aws source and trigger download
i. In your koku environment, generate a fresh report via nise (assuming your source is local)
ii. Trigger download for the new report, which will trigger recreating the aws line item tables
http://127.0.0.1:5042/api/cost-management/v1/download/?provider_uuid=<your_provider_uuid>
Repeat
step 3
and see thatproduct_memory
andproduct_operatingsystem
columns are present in the respective tables.Release Notes