You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am frustrated by the fact that there isn't a way to upsert data to bigquery using ibis.
What is the motivation behind your request?
I am trying to make an endpoint that I can send table data to. This endpoint determines if it needs to create the table or insert data into an existing table. However, the problem is that the records I send through occasionally gets updated. And, given the current functionality, I can only upload this as a new record. This inevitably leads to duplications and complications for downstream clients as I have to try to teach them "Oh yea, you can't rely on the data here because these transactions are going to be duplicated, no you didn't get 50 000 transactions in march, you got 3 highly edited ones"
Describe the solution you'd like
I'd like if there was a dedicated upsert function that I could say "Hey dude, here's the data, match using THIS column, please figure out the rest". As of right now I could only implement table specific solutions, which would defeat the point of trying to make the API endpoint generic.
What version of ibis are you running?
3.3
What backend(s) are you using, if any?
BigQuery
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
I am frustrated by the fact that there isn't a way to upsert data to bigquery using ibis.
What is the motivation behind your request?
I am trying to make an endpoint that I can send table data to. This endpoint determines if it needs to create the table or insert data into an existing table. However, the problem is that the records I send through occasionally gets updated. And, given the current functionality, I can only upload this as a new record. This inevitably leads to duplications and complications for downstream clients as I have to try to teach them "Oh yea, you can't rely on the data here because these transactions are going to be duplicated, no you didn't get 50 000 transactions in march, you got 3 highly edited ones"
Describe the solution you'd like
I'd like if there was a dedicated upsert function that I could say "Hey dude, here's the data, match using THIS column, please figure out the rest". As of right now I could only implement table specific solutions, which would defeat the point of trying to make the API endpoint generic.
What version of ibis are you running?
3.3
What backend(s) are you using, if any?
BigQuery
Code of Conduct
The text was updated successfully, but these errors were encountered: