-
Notifications
You must be signed in to change notification settings - Fork 478
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
The streaming query API has no possibility to cancel query and to be notified about finished stream #516
Conversation
Codecov Report
@@ Coverage Diff @@
## master #516 +/- ##
============================================
+ Coverage 87.91% 87.97% +0.06%
- Complexity 378 380 +2
============================================
Files 25 25
Lines 1531 1547 +16
Branches 169 172 +3
============================================
+ Hits 1346 1361 +15
Misses 120 120
- Partials 65 66 +1
Continue to review full report at Codecov.
|
LGTM |
FAQ.md
Outdated
@@ -102,3 +103,37 @@ SSLv3/TLSv1/TLSv1.1/TLSv1.2 | |||
|
|||
So if the server supports TLS1.2, the communication should be encrypted by TLS 1.2 (during the handshake the client will provide the list of accepted security protocols and the server will pick one, so this case the server would pick TLS 1.2) | |||
|
|||
## How to use SSL client certificate authentication |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @rhajek,
as the FAQ additions are unrelated to the streaming PR could you please move them to a seperate PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bednar you have to resolv the merge conflicts in this branch, after that i will merge. |
Hi @majst01, conflicts are resolved. |
fix issue #515