Skip to content
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

Isolation level #392

Open
ruria opened this issue Jul 11, 2024 · 0 comments
Open

Isolation level #392

ruria opened this issue Jul 11, 2024 · 0 comments
Labels

Comments

@ruria
Copy link

ruria commented Jul 11, 2024

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?

@ruria ruria added the bug label Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant