-
Notifications
You must be signed in to change notification settings - Fork 18
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
implement timeout in all backends #47
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tyrasd
force-pushed
the
scanquery-timeout
branch
2 times, most recently
from
January 11, 2019 13:34
eb0b388
to
d6bfb16
Compare
tyrasd
force-pushed
the
scanquery-timeout
branch
3 times, most recently
from
January 29, 2019 10:30
9715b2e
to
321ca30
Compare
tyrasd
changed the title
[WIP] implement timeout in ignite scanquery backend
[WIP] implement timeout in ignite-scanquery backend
Feb 5, 2019
tyrasd
force-pushed
the
scanquery-timeout
branch
from
February 8, 2019 14:04
321ca30
to
f998e6b
Compare
tyrasd
changed the title
[WIP] implement timeout in ignite-scanquery backend
implement timeout in ignite-scanquery backend
Feb 8, 2019
tyrasd
force-pushed
the
scanquery-timeout
branch
from
February 8, 2019 15:44
b8bb89d
to
cdbd029
Compare
tyrasd
changed the title
implement timeout in ignite-scanquery backend
[wip] implement timeout in ignite-scanquery and rest of remaining backends
Feb 15, 2019
tyrasd
changed the title
[wip] implement timeout in ignite-scanquery and rest of remaining backends
implement timeout in ignite-scanquery and rest of remaining backends
Feb 18, 2019
tyrasd
changed the title
implement timeout in ignite-scanquery and rest of remaining backends
implement timeout in all backends
Feb 18, 2019
tyrasd
force-pushed
the
scanquery-timeout
branch
from
February 18, 2019 15:43
c094e2f
to
a914c0b
Compare
so it can't be altered during a query by changing it in a different thread (concurrently running queries) also add a method to clear a previously existing timeout value
tyrasd
force-pushed
the
scanquery-timeout
branch
from
February 18, 2019 15:49
a914c0b
to
866f5c0
Compare
rtroilo
approved these changes
Feb 19, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This implements timeouts for the remaining backends
also add supports for the data streaming functionality