-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failure to delete ingress data rows #612
Comments
Do you see anything in the log when running with |
Also, can you try submitting the same command with |
The log from receiving the request to timeout:
|
|
I was only able to reproduce this when the pipeline is in the |
Yes, I actually tested this in PAUSED state. Not sure about semantics of this state. Can the delete request get queued while the pipeline is paused (and reflect the change in data browser), and applied to the output views once pipeline is resumed? |
This isn't really specific to deletes. Insertions are handled in the same way. Buffering inputs indefinitely is probably not a good idea. Sure, people are not going to submit millions of updates via the UI, but the same API is used for regular http input streaming. Ideally we would just process the updates by unpausing just one input connector. It's totally doable but needs some extra machinery. For now maybe we can just refuse to process deletes in paused state. Let me look into it a bit more and come up with a suggestion. |
Great! In the meantime I'll disable deletion in non-RUNNING states |
I guess you mean in PAUSED state. We should do the same with insertions. |
So here are the options:
3 seems like the best option to me. What do you guys think? @gz , @Karakatiza666 |
3 sounds like a workaround; If effort to implement it on the backend is more than 33% of option 4 - I'd say option 1 right now, and do option 4 when possible. If less - option 3 for now |
Yes, it's easy to implement. In fact, I now realize that option 4 won't even work, since HTTP connectors are created implicitly and are not even exposed through the API. So option 3 it is. |
Solved in #630. |
When running delete query error 500 is returned. Example query:
Error forwarding HTTP request to pipeline '018a0825-c038-71f2-9747-17f154da8c5c': 'Timeout while waiting for response'
Can be tested with "delete" button present when selecting rows in Data Browser in
feat-ui
branchExample query:
body:
The text was updated successfully, but these errors were encountered: