[
https://issues.apache.org/jira/browse/HIVE-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13827170#comment-13827170
]
Jeff Beard commented on HIVE-4256:
----------------------------------
We've seen the behavior where the database specified in the JDBC URL is
*sometimes* ignored.
We worked around it by executing a "use database" query before any others.
However, It also appears that there is some lingering state because the next
program that runs against Hive will use the database specified in the last "use
database" statement and not the one specified in the JDBC URL. So all our Hive
JDBC programs execute a "use database" query before running any others.
This is with the Cloudera variant of 0.10.0.
> JDBC2 HiveConnection does not use the specified database
> --------------------------------------------------------
>
> Key: HIVE-4256
> URL: https://issues.apache.org/jira/browse/HIVE-4256
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2, JDBC
> Affects Versions: 0.11.0
> Reporter: Chris Drome
> Assignee: Chris Drome
>
> HiveConnection ignores the database specified in the connection string when
> configuring the connection.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
