-
Notifications
You must be signed in to change notification settings - Fork 90
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
IGNITE-21815 Client handler: use QueryProcessor instead of IgniteSql #3459
Conversation
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.
LGTM!
@@ -41,6 +41,7 @@ | |||
* Asynchronous result set implementation. | |||
*/ | |||
public class AsyncResultSetImpl<T> implements AsyncResultSet<T> { | |||
@Nullable |
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.
according to our guidelines, type-use annotations appear immediately before the annotated type
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.
Fixed.
Use internal
QueryProcessor
API in client handler instead of publicIgniteSql
:HybridTimestamp
propagationhttps://issues.apache.org/jira/browse/IGNITE-21815