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年前
関連するコンテンツ
- 質問済み 6年前