-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update the analytics CDK stack #481
Conversation
tags: [{ key: "version", value: config.dataVersion.toString() }], | ||
}) | ||
|
||
this.workGroupName = workGroup.name |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where are you using the workGroupName?
Is it at all necessary to tie the work group to the glue database? Or this is just on the Athena side?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are right it is not needed I can match the workGroup with the output bucket.
If we don't tie them here with a workgroup then we have to update the location in the console manually.
}, | ||
"amount": { | ||
"type": "string", | ||
"type": "number", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you keeping all decimals, rounding, or keeping the original big int?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently we are losing precision. I will store it as a string and let Athena handle casting CAST(amount AS DECIMAL(12, 4))
. That would keep it precise and flexible.
WorkGroup
to connect the S3 output bucket to the Glue database. We had the bucket before but it wasn't being used correctly.