You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Tim Armstrong (JIRA)" <ji...@apache.org> on 2018/06/11 19:22:00 UTC

[jira] [Resolved] (IMPALA-1904) Issue with Impala JDBC using Spring JDBC Template with pooled datasource

     [ https://issues.apache.org/jira/browse/IMPALA-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Armstrong resolved IMPALA-1904.
-----------------------------------
    Resolution: Invalid

We don't track bugs for this client here, it's not part of Apache IMpala.

> Issue with Impala JDBC using Spring JDBC Template with pooled datasource
> ------------------------------------------------------------------------
>
>                 Key: IMPALA-1904
>                 URL: https://issues.apache.org/jira/browse/IMPALA-1904
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Clients
>    Affects Versions: Impala 2.1.1
>         Environment: Wiindows 7 64bit, java 6 & 7
>            Reporter: Sandeep
>            Assignee: Syed A. Hashmi
>            Priority: Minor
>              Labels: impala
>         Attachments: TestWeb1.zip
>
>
> Hi,
> I am facing a strange issue while using imapala jdbc drivers to connect with hadoop.
> The scenario is when UI is hitting two of my REST services which internally trying to fetch data from 3 tables, one of the API throws exception saying SQL DataIntegrityViolation. This is a random behaviour from both the API's. Both the API works fine if we call them one by one. This is like UI is making async calls at the same time.
> I am using Spring framework and using JDBCTemplate to run sql statements. We have a Single instance of DataSource throughout the application.  No matter whether I use Imapala's DataSource which supports pooling or Spring DriverManagerDataSource result is same. On the other side it works fine if i use Core JDBC syntax like closing statement and connection object after each call. In Spring closing of statement and connection object is being handled by Spring JDBCTemplate itself.
> Please let me know if its a known issue and we have an alternate for that.
> Thanks
> Sandeep Verma



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org