2 回答
- 最新
- 投票最多
- 评论最多
0
Your current architecture sounds standard (and good!).
Part of the reason that CSV import is so fast is that it's only handling a limited set of functions. I'm pretty sure there's no ability to handle the on conflict
idea there.
已回答 2 年前
0
Thanks for the feedback.
What would be a nice simplification of the solution would be if there was a way of parsing the JSON structure in the S3 bucket directly as part of the import, as I currently have to split the JSON into individual files for each 'table' for the import process, then write a custom stored procedure to do the merge from each bucket.
First world problems...
已回答 2 年前
相关内容
- AWS 官方已更新 1 年前