Timeline for Allow users upload CSV files, and embed the data for a simple API
Current License: CC BY-SA 4.0
5 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jan 28, 2020 at 15:03 | history | bounty ended | CommunityBot | ||
Jan 22, 2020 at 15:31 | comment | added | JimmyJames | @yonatanmn Ah, that changes things a good bit. I will need to revise my answer. You should probably clarify this distinction in your question. Another think that's important is the size of the rows. I major component of Dynamo pricing is done it terms of 'reads' and if I understand the pricing correctly, one read of 1K of data costs the same as a read of 4K of data. This leads me to the conclusion that lots of tiny records are not cost effective in Dynamo. | |
Jan 22, 2020 at 15:24 | history | edited | JimmyJames | CC BY-SA 4.0 |
typo
|
Jan 21, 2020 at 11:35 | comment | added | yonatanmn |
Thx for the reply @JimmyJames. The ID that the api is referring to is the row-id , in my example - id345 (not user id, nor csv id). the user uploads a large db (as CSV) , and he wants a public api to get data about one specific row. How would you structure that?
|
|
Jan 20, 2020 at 16:09 | history | answered | JimmyJames | CC BY-SA 4.0 |