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 공식업데이트됨 일 년 전