feature request: Import API: add `overwrite` to `collision_strategy`
See original GitHub issueIn cartoframes development, we rely on the Import API for updating a table in a user’s account.
Having a collision_strategy=overwrite
option would make our development cleaner and allow us to offload the complexity of data/map management to CARTO’s APIs instead of having to rely on the unintended consequences of dropping a table that a visualization is attached to.
- Strategy
- If the schema does not exactly match, raise an error.
- Documentation
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:14 (13 by maintainers)
Top Results From Across the Web
Overwriting feature layers | ArcGIS API for Python
Let us overwrite the feature layer using the new csv file we just created. To overwrite, we will use the overwrite() method. from...
Read more >Overwrite feature layer Python API - Esri Community
Hi, I'm trying to use the overwrite feature within the Python API to add/update a feature layer. The script is supposed to update...
Read more >[0.9.1] data with same timestamp and tags gets overwritten
I'm currently adding an uuid tag to prevent points overwriting each other, is this a good practice?
Read more >Path Operation Advanced Configuration - FastAPI
If you want to use your APIs' function names as operationId s, you can iterate over all of them and override each path...
Read more >SharePoint Online Import Migration API - Microsoft Learn
SharePoint Import Migration API (CreationMigrationJob) ... or the migration job will be unable to add events to the queue. ... This is an...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
If we want to implement this we should close the scope a lot, specifically about table schema. If the schema does not exactly match I’d raise an error.
To give some perspective. We had (during years) a feature called import append flag. Actually we had that feature in the first version of the editor, it was always disabled and we finally removed it because we didn’t implement it. I also heard a lot of times the “replace table” thing
@andy-esch give this a try at your CartoFrames workflow. If you find bugs or rough edges open a new issue and we’ll discuss it.