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
Hi, I´m trying to execute my queries against sql server using "read uncommitted" or "snapshot" isolation level cause I don´t want to lock others while long queries.
I think there is no other way to do that but insert it in sql statemet (example: "set transaction isolation level read uncommitted; select * from ...") but does not work, locks are adquire in the server for this query.
Is there something in logstash / jdbc / sequel that avoid to use this workarround?
The text was updated successfully, but these errors were encountered:
Note: I try to confirm this bug first ( https://discuss.elastic.co/t/isolation-level/362818 ) but no sure if it is or is not at the moment.
Hi, I´m trying to execute my queries against sql server using "read uncommitted" or "snapshot" isolation level cause I don´t want to lock others while long queries.
I think there is no other way to do that but insert it in sql statemet (example: "set transaction isolation level read uncommitted; select * from ...") but does not work, locks are adquire in the server for this query.
Is there something in logstash / jdbc / sequel that avoid to use this workarround?
The text was updated successfully, but these errors were encountered: