You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Tim Armstrong (Jira)" <ji...@apache.org> on 2020/07/31 15:34:00 UTC
[jira] [Resolved] (IMPALA-10031) Unable to close the connection
when fetching data from two databases
[ https://issues.apache.org/jira/browse/IMPALA-10031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong resolved IMPALA-10031.
------------------------------------
Resolution: Duplicate
> Unable to close the connection when fetching data from two databases
> ---------------------------------------------------------------------
>
> Key: IMPALA-10031
> URL: https://issues.apache.org/jira/browse/IMPALA-10031
> Project: IMPALA
> Issue Type: Bug
> Components: Clients
> Reporter: jayashree
> Priority: Critical
>
> Hi Team,
> I am connecting two databases using cloudera.impala.jdbc41.Driver.
> I have two classes with two different connections, each having different SQLs to perform in respective database.
> When I am executing these two classes together, I am getting below error though I am closing first connection and then connecting to other Database.
> Error:
> j*ava.sql.SQLException: [Simba][ImpalaJDBCDriver](500051) ERROR processing query/statement. Error Code: 0, SQL state: TStatus(statusCode:ERROR_STATUS, sqlState:HY000, errorMessage:AnalysisException: Could not resolve table reference:*
> *Caused by: java.sql.SQLException:*
> *[Simba][ImpalaJDBCDriver](500051) ERROR processing query/statement. Error Code: 0, SQL state: TStatus(statusCode:ERROR_STATUS, sqlState:HY000, errorMessage:AnalysisException: Could not resolve table reference:*
> *Caused by: com.cloudera.support.exceptions.GeneralException:*
> *[Simba][ImpalaJDBCDriver](500051) ERROR processing query/statement. Error Code: 0, SQL state: TStatus(statusCode:ERROR_STATUS, sqlState:HY000, errorMessage:AnalysisException: Could not resolve table reference:*
>
> *Seems its not able to close first connection.*
> *Can you please check it*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)