You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AWS and Azure export to parquet differently for cost columns which means conversion is required.
Which area does this issue relate to?
A: Missing FinOps feature, use case, or scenario
Detailed Description
When exporting AWS FOCUS and Azure Focus, Azure exports to Parquet in DECIMAL (38) and AWS in DOUBLE. The headache here is finding a common ground in a warehouse that doesn't support double. Float doesn't work, so I had to change the receiving column to varchar and then convert to decimal.
What use cases, FinOps or others, can't be performed with the existing specification unless this issue is addressed?
There is a work around, but it would be good if alignment could be achieved between parquet exports.
Which FinOps personas does this issue relate to?
Technical
Which provider groups or specific providers does this issue relate to?
AWS, Azure.
On a scale of 1 - 4, how critical is this for your organization?
3: Important for adoption in the next 6-12 months
Objective
Establish a common parquet format.
Data Examples
No response
Issues, PRs, or Other References
No response
The text was updated successfully, but these errors were encountered:
Summary
AWS and Azure export to parquet differently for cost columns which means conversion is required.
Which area does this issue relate to?
A: Missing FinOps feature, use case, or scenario
Detailed Description
When exporting AWS FOCUS and Azure Focus, Azure exports to Parquet in DECIMAL (38) and AWS in DOUBLE. The headache here is finding a common ground in a warehouse that doesn't support double. Float doesn't work, so I had to change the receiving column to varchar and then convert to decimal.
What use cases, FinOps or others, can't be performed with the existing specification unless this issue is addressed?
There is a work around, but it would be good if alignment could be achieved between parquet exports.
Which FinOps personas does this issue relate to?
Technical
Which provider groups or specific providers does this issue relate to?
AWS, Azure.
On a scale of 1 - 4, how critical is this for your organization?
3: Important for adoption in the next 6-12 months
Objective
Establish a common parquet format.
Data Examples
No response
Issues, PRs, or Other References
No response
The text was updated successfully, but these errors were encountered: