This message was deleted.
# generals
Slackbot
07/10/2023, 3:42 PMThis message was deleted.
➕ 2
b
Ben Krug
07/10/2023, 6:53 PMIt seems to be fairly new, and I don't see documentation. That said, I believe some people are using it in production. You might want to test it out, and monitor things if you decide to use it. (If you need to do concurrent batch ingestions, eg.)
g
Gian Merlino
07/10/2023, 10:34 PMas with anything undocumented it's "use at your own risk"
Gian Merlino
07/10/2023, 10:34 PMI am not sure if there are currently plans to make this the default behavior— perhaps @Eric Tschetter knows?
e
Eric Tschetter
07/10/2023, 10:38 PMIt generally works. We are working on doing more fundamental changes to allow for both "append" and "replace" at the same time, which will end up using a different type of lock that we are in the process of introducing.
What's the problem you are running into that you want to solve?
h
Hellmar Becker
07/11/2023, 9:24 AM@Eric Tschetter Does this work in MSQ too?
t
Tomasz Melcer
07/11/2023, 11:42 AMthank you,
as with anything undocumented it's "use at your own risk"that's our attitude as well… we've noticed that we were missing data that we tried batch loading concurrently, and observed the lock to be a problem.
2 Views