[COST-4745] OCPGCP Network data processing SQL #5058
Draft
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-4745
Network unattributed
project in [COST-4744] Azure network data processing SQL #5056Description
This change will add ocp on gcp network processing, I need to separate out the migrations and get nise updated, this PR is not ready for review. The migration here will be needed for all 3 cloud providers and will be joined into a single migration when its ready.
NOTE: when GCP renamed Ingress to
Data Transfer in
, Egress was renamed toData Transfer
that sometimes has a conditional of out but sometimes does not. Based on my understanding of this GCP article, Ingress was simply renamed toData Transfer In
and any other data transfer is Egress/OutboundTesting
docker exec -it trino trino --server localhost:8080 --catalog hive --schema org1234567 --user admin --debug
72000 = 50 (usage) * 2 (rate) * 24 hours * 30 days
✅216000 = 30 (usage) * 10 (rate) * 24 hours * 30 days
✅Release Notes