[jira] [Commented] (HIVE-2957) Hive JDBC doesn't support TIMESTAMP column
[ https://issues.apache.org/jira/browse/HIVE-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259049#comment-13259049 ] Bharath Ganesh commented on HIVE-2957: -- Looks fine to me. Thanks. Hive JDBC doesn't support TIMESTAMP column -- Key: HIVE-2957 URL: https://issues.apache.org/jira/browse/HIVE-2957 Project: Hive Issue Type: Bug Components: JDBC Affects Versions: 0.8.1, 0.9.0 Reporter: Bharath Ganesh Assignee: Bharath Ganesh Priority: Minor Attachments: HIVE-2957.2.patch.txt, HIVE-2957.patch Steps to replicate: 1. Create a table with at least one column of type TIMESTAMP 2. Do a DatabaseMetaData.getColumns () such that this TIMESTAMP column is part of the resultset. 3. When you iterate over the TIMESTAMP column it would fail, throwing the below exception: Exception in thread main java.sql.SQLException: Unrecognized column type: timestamp at org.apache.hadoop.hive.jdbc.Utils.hiveTypeToSqlType(Utils.java:56) at org.apache.hadoop.hive.jdbc.JdbcColumn.getSqlType(JdbcColumn.java:62) at org.apache.hadoop.hive.jdbc.HiveDatabaseMetaData$2.next(HiveDatabaseMetaData.java:244) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2957) Hive JDBC doesn't support TIMESTAMP column
[ https://issues.apache.org/jira/browse/HIVE-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharath Ganesh updated HIVE-2957: - Summary: Hive JDBC doesn't support TIMESTAMP column (was: JDBC getColumns() fails on a TIMESTAMP column) Hive JDBC doesn't support TIMESTAMP column -- Key: HIVE-2957 URL: https://issues.apache.org/jira/browse/HIVE-2957 Project: Hive Issue Type: Bug Components: JDBC Affects Versions: 0.8.1, 0.9.0 Reporter: Bharath Ganesh Assignee: Bharath Ganesh Priority: Minor Steps to replicate: 1. Create a table with at least one column of type TIMESTAMP 2. Do a DatabaseMetaData.getColumns () such that this TIMESTAMP column is part of the resultset. 3. When you iterate over the TIMESTAMP column it would fail, throwing the below exception: Exception in thread main java.sql.SQLException: Unrecognized column type: timestamp at org.apache.hadoop.hive.jdbc.Utils.hiveTypeToSqlType(Utils.java:56) at org.apache.hadoop.hive.jdbc.JdbcColumn.getSqlType(JdbcColumn.java:62) at org.apache.hadoop.hive.jdbc.HiveDatabaseMetaData$2.next(HiveDatabaseMetaData.java:244) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2957) Hive JDBC doesn't support TIMESTAMP column
[ https://issues.apache.org/jira/browse/HIVE-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharath Ganesh updated HIVE-2957: - Fix Version/s: 0.8.0 0.10 0.9.0 Status: Patch Available (was: In Progress) Hive JDBC doesn't support TIMESTAMP column -- Key: HIVE-2957 URL: https://issues.apache.org/jira/browse/HIVE-2957 Project: Hive Issue Type: Bug Components: JDBC Affects Versions: 0.8.1, 0.9.0 Reporter: Bharath Ganesh Assignee: Bharath Ganesh Priority: Minor Fix For: 0.9.0, 0.10, 0.8.0 Steps to replicate: 1. Create a table with at least one column of type TIMESTAMP 2. Do a DatabaseMetaData.getColumns () such that this TIMESTAMP column is part of the resultset. 3. When you iterate over the TIMESTAMP column it would fail, throwing the below exception: Exception in thread main java.sql.SQLException: Unrecognized column type: timestamp at org.apache.hadoop.hive.jdbc.Utils.hiveTypeToSqlType(Utils.java:56) at org.apache.hadoop.hive.jdbc.JdbcColumn.getSqlType(JdbcColumn.java:62) at org.apache.hadoop.hive.jdbc.HiveDatabaseMetaData$2.next(HiveDatabaseMetaData.java:244) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2957) Hive JDBC doesn't support TIMESTAMP column
[ https://issues.apache.org/jira/browse/HIVE-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharath Ganesh updated HIVE-2957: - Attachment: HIVE-2957.patch Added support for TIMESTAMP column on the JDBC driver. I am not 100% sure of the precision and scale. Please do verify. I tested the sanity and I am able to retrieve a column upto nano-second precision. Hive JDBC doesn't support TIMESTAMP column -- Key: HIVE-2957 URL: https://issues.apache.org/jira/browse/HIVE-2957 Project: Hive Issue Type: Bug Components: JDBC Affects Versions: 0.8.1, 0.9.0 Reporter: Bharath Ganesh Assignee: Bharath Ganesh Priority: Minor Fix For: 0.9.0 Attachments: HIVE-2957.patch Steps to replicate: 1. Create a table with at least one column of type TIMESTAMP 2. Do a DatabaseMetaData.getColumns () such that this TIMESTAMP column is part of the resultset. 3. When you iterate over the TIMESTAMP column it would fail, throwing the below exception: Exception in thread main java.sql.SQLException: Unrecognized column type: timestamp at org.apache.hadoop.hive.jdbc.Utils.hiveTypeToSqlType(Utils.java:56) at org.apache.hadoop.hive.jdbc.JdbcColumn.getSqlType(JdbcColumn.java:62) at org.apache.hadoop.hive.jdbc.HiveDatabaseMetaData$2.next(HiveDatabaseMetaData.java:244) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2957) Hive JDBC doesn't support TIMESTAMP column
[ https://issues.apache.org/jira/browse/HIVE-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharath Ganesh updated HIVE-2957: - Fix Version/s: (was: 0.10) (was: 0.8.0) Hive JDBC doesn't support TIMESTAMP column -- Key: HIVE-2957 URL: https://issues.apache.org/jira/browse/HIVE-2957 Project: Hive Issue Type: Bug Components: JDBC Affects Versions: 0.8.1, 0.9.0 Reporter: Bharath Ganesh Assignee: Bharath Ganesh Priority: Minor Fix For: 0.9.0 Attachments: HIVE-2957.patch Steps to replicate: 1. Create a table with at least one column of type TIMESTAMP 2. Do a DatabaseMetaData.getColumns () such that this TIMESTAMP column is part of the resultset. 3. When you iterate over the TIMESTAMP column it would fail, throwing the below exception: Exception in thread main java.sql.SQLException: Unrecognized column type: timestamp at org.apache.hadoop.hive.jdbc.Utils.hiveTypeToSqlType(Utils.java:56) at org.apache.hadoop.hive.jdbc.JdbcColumn.getSqlType(JdbcColumn.java:62) at org.apache.hadoop.hive.jdbc.HiveDatabaseMetaData$2.next(HiveDatabaseMetaData.java:244) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (HIVE-2957) JDBC getColumns() fails on a TIMESTAMP column
[ https://issues.apache.org/jira/browse/HIVE-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HIVE-2957 started by Bharath Ganesh. JDBC getColumns() fails on a TIMESTAMP column - Key: HIVE-2957 URL: https://issues.apache.org/jira/browse/HIVE-2957 Project: Hive Issue Type: Bug Components: JDBC Affects Versions: 0.8.1, 0.9.0 Reporter: Bharath Ganesh Assignee: Bharath Ganesh Priority: Minor Steps to replicate: 1. Create a table with at least one column of type TIMESTAMP 2. Do a DatabaseMetaData.getColumns () such that this TIMESTAMP column is part of the resultset. 3. When you iterate over the TIMESTAMP column it would fail, throwing the below exception: Exception in thread main java.sql.SQLException: Unrecognized column type: timestamp at org.apache.hadoop.hive.jdbc.Utils.hiveTypeToSqlType(Utils.java:56) at org.apache.hadoop.hive.jdbc.JdbcColumn.getSqlType(JdbcColumn.java:62) at org.apache.hadoop.hive.jdbc.HiveDatabaseMetaData$2.next(HiveDatabaseMetaData.java:244) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2890) Example UDAFs do not run
[ https://issues.apache.org/jira/browse/HIVE-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13240365#comment-13240365 ] Bharath Ganesh commented on HIVE-2890: -- I dont think this issue exists on the trunk. I verified the UDAF constructors are public and I was able to execute them. Can you confirm? Example UDAFs do not run Key: HIVE-2890 URL: https://issues.apache.org/jira/browse/HIVE-2890 Project: Hive Issue Type: Bug Components: Contrib, Documentation Affects Versions: 0.8.1 Reporter: robin morris Priority: Minor Original Estimate: 1h Remaining Estimate: 1h The example UDAFs in src/contrib/src/java/org/apache/hadoop/hive/contrib/udaf/example have their constructors declared as private. This causes the udaf to fail at run-time. Removing the declaration of the constructor fixes the problem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
JDBC Driver support for multiple database/schema
Hello, While using the JDBC driver on 0.7.1, there seems to be an issue around support for multiple databases. According to Hive JDBC documentation at https://cwiki.apache.org/Hive/hiveclient.html : * * *For standalone server, uri is jdbc:hive://host:port/dbname where host and port are determined by where the hive server is run. For example, jdbc:hive://localhost:1/default. Currently, the only dbname supported is default. * Was there any specific reason to not support non-default databases? The obvious way for me to get it working is to patch the connection object, parse the connection string, pick the database name and issue a USE db-name query as part of initializing the connection. Do you think this is a reasonable way to do this? Would be happy to have your suggestions! Thanks, Bharath
