You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Andrey Gura (JIRA)" <ji...@apache.org> on 2019/07/03 17:13:00 UTC

[jira] [Commented] (IGNITE-11958) JDBC connection validation should use it's own task instead of cache validation task

    [ https://issues.apache.org/jira/browse/IGNITE-11958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16878003#comment-16878003 ] 

Andrey Gura commented on IGNITE-11958:
--------------------------------------

[~Denis Chudov] What is motivation for this change? Is there any issues related with it?

> JDBC connection validation should use it's own task instead of cache validation task
> ------------------------------------------------------------------------------------
>
>                 Key: IGNITE-11958
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11958
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Denis Chudov
>            Assignee: Denis Chudov
>            Priority: Major
>             Fix For: 2.8
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> JDBC connection is validated using GridCacheQueryJdbcValidationTask. We should create own validation task for this activity.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)