[jira] [Commented] (HIVE-538) make hive_jdbc.jar self-containing
[ https://issues.apache.org/jira/browse/HIVE-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058557#comment-14058557 ] Nick White commented on HIVE-538: - [~ekoifman] Are you adding the driver as a dependency to a Maven project? If so, you should probably add the non-standalone version so you have more control over transitive dependency versioning. I'd use the standalone jar as an end-user download, e.g. if you want to drop it into an existing app (e.g. http://squirrel-sql.sourceforge.net, Sqoop). Or is your question - "where is the standalone jar automatically published to?"? > make hive_jdbc.jar self-containing > -- > > Key: HIVE-538 > URL: https://issues.apache.org/jira/browse/HIVE-538 > Project: Hive > Issue Type: Improvement > Components: JDBC >Affects Versions: 0.3.0, 0.4.0, 0.6.0, 0.13.0 >Reporter: Raghotham Murthy >Assignee: Nick White > Fix For: 0.14.0 > > Attachments: ASF.LICENSE.NOT.GRANTED--HIVE-538.D2553.1.patch, > ASF.LICENSE.NOT.GRANTED--HIVE-538.D2553.2.patch, HIVE-538.patch > > > Currently, most jars in hive/build/dist/lib and the hadoop-*-core.jar are > required in the classpath to run jdbc applications on hive. We need to do > atleast the following to get rid of most unnecessary dependencies: > 1. get rid of dynamic serde and use a standard serialization format, maybe > tab separated, json or avro > 2. dont use hadoop configuration parameters > 3. repackage thrift and fb303 classes into hive_jdbc.jar -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HIVE-6923) Use slf4j For Logging Everywhere
[ https://issues.apache.org/jira/browse/HIVE-6923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13979462#comment-13979462 ] Nick White commented on HIVE-6923: -- [~vgumashta] see https://reviews.apache.org/r/20656/ - thanks! > Use slf4j For Logging Everywhere > > > Key: HIVE-6923 > URL: https://issues.apache.org/jira/browse/HIVE-6923 > Project: Hive > Issue Type: Improvement > Components: HiveServer2 >Reporter: Nick White >Assignee: Nick White > Fix For: 0.13.0 > > Attachments: HIVE-6923.patch > > > Hive uses a mixture of slf4j (backed by log4j) and commons-logging. I've > attached a patch to tidy this up, by just using slf4j for all loggers. This > means that applications using the JDBC driver can make Hive log through their > own slf4j implementation consistently. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6964) Upgrade to Thrift 0.9.1
[ https://issues.apache.org/jira/browse/HIVE-6964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick White updated HIVE-6964: - Status: Patch Available (was: Open) > Upgrade to Thrift 0.9.1 > --- > > Key: HIVE-6964 > URL: https://issues.apache.org/jira/browse/HIVE-6964 > Project: Hive > Issue Type: Bug > Components: Thrift API >Reporter: Nick White > Attachments: HIVE-6964.patch > > > Bump the version number & regenerate the src/gen/thrift/* files -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (HIVE-6964) Upgrade to Thrift 0.9.1
Nick White created HIVE-6964: Summary: Upgrade to Thrift 0.9.1 Key: HIVE-6964 URL: https://issues.apache.org/jira/browse/HIVE-6964 Project: Hive Issue Type: Bug Components: Thrift API Reporter: Nick White Attachments: HIVE-6964.patch Bump the version number & regenerate the src/gen/thrift/* files -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (HIVE-6964) Upgrade to Thrift 0.9.1
[ https://issues.apache.org/jira/browse/HIVE-6964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick White reassigned HIVE-6964: Assignee: Nick White > Upgrade to Thrift 0.9.1 > --- > > Key: HIVE-6964 > URL: https://issues.apache.org/jira/browse/HIVE-6964 > Project: Hive > Issue Type: Bug > Components: Thrift API >Reporter: Nick White >Assignee: Nick White > Attachments: HIVE-6964.patch > > > Bump the version number & regenerate the src/gen/thrift/* files -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6964) Upgrade to Thrift 0.9.1
[ https://issues.apache.org/jira/browse/HIVE-6964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick White updated HIVE-6964: - Attachment: HIVE-6964.patch > Upgrade to Thrift 0.9.1 > --- > > Key: HIVE-6964 > URL: https://issues.apache.org/jira/browse/HIVE-6964 > Project: Hive > Issue Type: Bug > Components: Thrift API >Reporter: Nick White > Attachments: HIVE-6964.patch > > > Bump the version number & regenerate the src/gen/thrift/* files -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HIVE-538) make hive_jdbc.jar self-containing
[ https://issues.apache.org/jira/browse/HIVE-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13975771#comment-13975771 ] Nick White commented on HIVE-538: - also, duplicating hive-jdbc's dependencies in an xml file in a different project will increase maintenance costs, as these two lists will have to be manually kept in sync. > make hive_jdbc.jar self-containing > -- > > Key: HIVE-538 > URL: https://issues.apache.org/jira/browse/HIVE-538 > Project: Hive > Issue Type: Improvement > Components: JDBC >Affects Versions: 0.3.0, 0.4.0, 0.6.0, 0.13.0 >Reporter: Raghotham Murthy >Assignee: Nick White > Attachments: ASF.LICENSE.NOT.GRANTED--HIVE-538.D2553.1.patch, > ASF.LICENSE.NOT.GRANTED--HIVE-538.D2553.2.patch, HIVE-538.patch > > > Currently, most jars in hive/build/dist/lib and the hadoop-*-core.jar are > required in the classpath to run jdbc applications on hive. We need to do > atleast the following to get rid of most unnecessary dependencies: > 1. get rid of dynamic serde and use a standard serialization format, maybe > tab separated, json or avro > 2. dont use hadoop configuration parameters > 3. repackage thrift and fb303 classes into hive_jdbc.jar -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HIVE-538) make hive_jdbc.jar self-containing
[ https://issues.apache.org/jira/browse/HIVE-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13975767#comment-13975767 ] Nick White commented on HIVE-538: - [~ashutoshc] not really, it manually lists some dependencies (not the transitive ones) instead of using maven to work them out, and creates a tar.gz of many jars, not a single jar with all the dependencies in. A tar.gz can't easily integrate with maven; it's easy to add this complete jar as a dependency to a third-party maven project as it's published with a distinct classifier. > make hive_jdbc.jar self-containing > -- > > Key: HIVE-538 > URL: https://issues.apache.org/jira/browse/HIVE-538 > Project: Hive > Issue Type: Improvement > Components: JDBC >Affects Versions: 0.3.0, 0.4.0, 0.6.0, 0.13.0 >Reporter: Raghotham Murthy >Assignee: Nick White > Attachments: ASF.LICENSE.NOT.GRANTED--HIVE-538.D2553.1.patch, > ASF.LICENSE.NOT.GRANTED--HIVE-538.D2553.2.patch, HIVE-538.patch > > > Currently, most jars in hive/build/dist/lib and the hadoop-*-core.jar are > required in the classpath to run jdbc applications on hive. We need to do > atleast the following to get rid of most unnecessary dependencies: > 1. get rid of dynamic serde and use a standard serialization format, maybe > tab separated, json or avro > 2. dont use hadoop configuration parameters > 3. repackage thrift and fb303 classes into hive_jdbc.jar -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-538) make hive_jdbc.jar self-containing
[ https://issues.apache.org/jira/browse/HIVE-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick White updated HIVE-538: Attachment: HIVE-538.patch > make hive_jdbc.jar self-containing > -- > > Key: HIVE-538 > URL: https://issues.apache.org/jira/browse/HIVE-538 > Project: Hive > Issue Type: Improvement > Components: JDBC >Affects Versions: 0.3.0, 0.4.0, 0.6.0, 0.13.0 >Reporter: Raghotham Murthy >Assignee: Nick White > Attachments: ASF.LICENSE.NOT.GRANTED--HIVE-538.D2553.1.patch, > ASF.LICENSE.NOT.GRANTED--HIVE-538.D2553.2.patch, HIVE-538.patch > > > Currently, most jars in hive/build/dist/lib and the hadoop-*-core.jar are > required in the classpath to run jdbc applications on hive. We need to do > atleast the following to get rid of most unnecessary dependencies: > 1. get rid of dynamic serde and use a standard serialization format, maybe > tab separated, json or avro > 2. dont use hadoop configuration parameters > 3. repackage thrift and fb303 classes into hive_jdbc.jar -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-538) make hive_jdbc.jar self-containing
[ https://issues.apache.org/jira/browse/HIVE-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick White updated HIVE-538: Attachment: (was: HIVE-538.patch) > make hive_jdbc.jar self-containing > -- > > Key: HIVE-538 > URL: https://issues.apache.org/jira/browse/HIVE-538 > Project: Hive > Issue Type: Improvement > Components: JDBC >Affects Versions: 0.3.0, 0.4.0, 0.6.0, 0.13.0 >Reporter: Raghotham Murthy >Assignee: Nick White > Attachments: ASF.LICENSE.NOT.GRANTED--HIVE-538.D2553.1.patch, > ASF.LICENSE.NOT.GRANTED--HIVE-538.D2553.2.patch, HIVE-538.patch > > > Currently, most jars in hive/build/dist/lib and the hadoop-*-core.jar are > required in the classpath to run jdbc applications on hive. We need to do > atleast the following to get rid of most unnecessary dependencies: > 1. get rid of dynamic serde and use a standard serialization format, maybe > tab separated, json or avro > 2. dont use hadoop configuration parameters > 3. repackage thrift and fb303 classes into hive_jdbc.jar -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6923) Use slf4j For Logging Everywhere
[ https://issues.apache.org/jira/browse/HIVE-6923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick White updated HIVE-6923: - Attachment: (was: HIVE-6923.patch) > Use slf4j For Logging Everywhere > > > Key: HIVE-6923 > URL: https://issues.apache.org/jira/browse/HIVE-6923 > Project: Hive > Issue Type: Improvement > Components: HiveServer2 >Reporter: Nick White >Assignee: Nick White > Fix For: 0.13.0 > > Attachments: HIVE-6923.patch > > > Hive uses a mixture of slf4j (backed by log4j) and commons-logging. I've > attached a patch to tidy this up, by just using slf4j for all loggers. This > means that applications using the JDBC driver can make Hive log through their > own slf4j implementation consistently. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6923) Use slf4j For Logging Everywhere
[ https://issues.apache.org/jira/browse/HIVE-6923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick White updated HIVE-6923: - Attachment: HIVE-6923.patch > Use slf4j For Logging Everywhere > > > Key: HIVE-6923 > URL: https://issues.apache.org/jira/browse/HIVE-6923 > Project: Hive > Issue Type: Improvement > Components: HiveServer2 >Reporter: Nick White >Assignee: Nick White > Fix For: 0.13.0 > > Attachments: HIVE-6923.patch > > > Hive uses a mixture of slf4j (backed by log4j) and commons-logging. I've > attached a patch to tidy this up, by just using slf4j for all loggers. This > means that applications using the JDBC driver can make Hive log through their > own slf4j implementation consistently. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (HIVE-6923) Use slf4j For Logging Everywhere
Nick White created HIVE-6923: Summary: Use slf4j For Logging Everywhere Key: HIVE-6923 URL: https://issues.apache.org/jira/browse/HIVE-6923 Project: Hive Issue Type: Improvement Components: HiveServer2 Reporter: Nick White Fix For: 0.13.0 Attachments: HIVE-6923.patch Hive uses a mixture of slf4j (backed by log4j) and commons-logging. I've attached a patch to tidy this up, by just using slf4j for all loggers. This means that applications using the JDBC driver can make Hive log through their own slf4j implementation consistently. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6923) Use slf4j For Logging Everywhere
[ https://issues.apache.org/jira/browse/HIVE-6923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick White updated HIVE-6923: - Assignee: Nick White Status: Patch Available (was: Open) > Use slf4j For Logging Everywhere > > > Key: HIVE-6923 > URL: https://issues.apache.org/jira/browse/HIVE-6923 > Project: Hive > Issue Type: Improvement > Components: HiveServer2 >Reporter: Nick White >Assignee: Nick White > Fix For: 0.13.0 > > Attachments: HIVE-6923.patch > > > Hive uses a mixture of slf4j (backed by log4j) and commons-logging. I've > attached a patch to tidy this up, by just using slf4j for all loggers. This > means that applications using the JDBC driver can make Hive log through their > own slf4j implementation consistently. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6923) Use slf4j For Logging Everywhere
[ https://issues.apache.org/jira/browse/HIVE-6923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick White updated HIVE-6923: - Attachment: HIVE-6923.patch > Use slf4j For Logging Everywhere > > > Key: HIVE-6923 > URL: https://issues.apache.org/jira/browse/HIVE-6923 > Project: Hive > Issue Type: Improvement > Components: HiveServer2 >Reporter: Nick White > Fix For: 0.13.0 > > Attachments: HIVE-6923.patch > > > Hive uses a mixture of slf4j (backed by log4j) and commons-logging. I've > attached a patch to tidy this up, by just using slf4j for all loggers. This > means that applications using the JDBC driver can make Hive log through their > own slf4j implementation consistently. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-538) make hive_jdbc.jar self-containing
[ https://issues.apache.org/jira/browse/HIVE-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick White updated HIVE-538: Attachment: HIVE-538.patch I've attached a patch that builds a self-containing jar - > make hive_jdbc.jar self-containing > -- > > Key: HIVE-538 > URL: https://issues.apache.org/jira/browse/HIVE-538 > Project: Hive > Issue Type: Improvement > Components: JDBC >Affects Versions: 0.3.0, 0.4.0, 0.6.0, 0.13.0 >Reporter: Raghotham Murthy >Assignee: Nick White > Attachments: ASF.LICENSE.NOT.GRANTED--HIVE-538.D2553.1.patch, > ASF.LICENSE.NOT.GRANTED--HIVE-538.D2553.2.patch, HIVE-538.patch > > > Currently, most jars in hive/build/dist/lib and the hadoop-*-core.jar are > required in the classpath to run jdbc applications on hive. We need to do > atleast the following to get rid of most unnecessary dependencies: > 1. get rid of dynamic serde and use a standard serialization format, maybe > tab separated, json or avro > 2. dont use hadoop configuration parameters > 3. repackage thrift and fb303 classes into hive_jdbc.jar -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HIVE-538) make hive_jdbc.jar self-containing
[ https://issues.apache.org/jira/browse/HIVE-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13971569#comment-13971569 ] Nick White commented on HIVE-538: - This should be easier to implement now Hive uses Maven as a build system - you could make the JDBC driver project use the shade plugin (https://maven.apache.org/plugins/maven-shade-plugin/shade-mojo.html). > make hive_jdbc.jar self-containing > -- > > Key: HIVE-538 > URL: https://issues.apache.org/jira/browse/HIVE-538 > Project: Hive > Issue Type: Improvement > Components: JDBC >Affects Versions: 0.3.0, 0.4.0, 0.6.0, 0.13.0 >Reporter: Raghotham Murthy >Assignee: Nick White > Attachments: ASF.LICENSE.NOT.GRANTED--HIVE-538.D2553.1.patch, > ASF.LICENSE.NOT.GRANTED--HIVE-538.D2553.2.patch > > > Currently, most jars in hive/build/dist/lib and the hadoop-*-core.jar are > required in the classpath to run jdbc applications on hive. We need to do > atleast the following to get rid of most unnecessary dependencies: > 1. get rid of dynamic serde and use a standard serialization format, maybe > tab separated, json or avro > 2. dont use hadoop configuration parameters > 3. repackage thrift and fb303 classes into hive_jdbc.jar -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-538) make hive_jdbc.jar self-containing
[ https://issues.apache.org/jira/browse/HIVE-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick White updated HIVE-538: Affects Version/s: 0.13.0 > make hive_jdbc.jar self-containing > -- > > Key: HIVE-538 > URL: https://issues.apache.org/jira/browse/HIVE-538 > Project: Hive > Issue Type: Improvement > Components: JDBC >Affects Versions: 0.3.0, 0.4.0, 0.6.0, 0.13.0 >Reporter: Raghotham Murthy >Assignee: Ashutosh Chauhan > Attachments: ASF.LICENSE.NOT.GRANTED--HIVE-538.D2553.1.patch, > ASF.LICENSE.NOT.GRANTED--HIVE-538.D2553.2.patch > > > Currently, most jars in hive/build/dist/lib and the hadoop-*-core.jar are > required in the classpath to run jdbc applications on hive. We need to do > atleast the following to get rid of most unnecessary dependencies: > 1. get rid of dynamic serde and use a standard serialization format, maybe > tab separated, json or avro > 2. dont use hadoop configuration parameters > 3. repackage thrift and fb303 classes into hive_jdbc.jar -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (HIVE-538) make hive_jdbc.jar self-containing
[ https://issues.apache.org/jira/browse/HIVE-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick White reassigned HIVE-538: --- Assignee: Nick White (was: Ashutosh Chauhan) > make hive_jdbc.jar self-containing > -- > > Key: HIVE-538 > URL: https://issues.apache.org/jira/browse/HIVE-538 > Project: Hive > Issue Type: Improvement > Components: JDBC >Affects Versions: 0.3.0, 0.4.0, 0.6.0, 0.13.0 >Reporter: Raghotham Murthy >Assignee: Nick White > Attachments: ASF.LICENSE.NOT.GRANTED--HIVE-538.D2553.1.patch, > ASF.LICENSE.NOT.GRANTED--HIVE-538.D2553.2.patch > > > Currently, most jars in hive/build/dist/lib and the hadoop-*-core.jar are > required in the classpath to run jdbc applications on hive. We need to do > atleast the following to get rid of most unnecessary dependencies: > 1. get rid of dynamic serde and use a standard serialization format, maybe > tab separated, json or avro > 2. dont use hadoop configuration parameters > 3. repackage thrift and fb303 classes into hive_jdbc.jar -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HIVE-2564) Set dbname at JDBC URL or properties
[ https://issues.apache.org/jira/browse/HIVE-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13913616#comment-13913616 ] Nick White commented on HIVE-2564: -- Actually, it seems it might have been fixed in HIVE-4256, maybe this should be resolved as a duplicate? > Set dbname at JDBC URL or properties > > > Key: HIVE-2564 > URL: https://issues.apache.org/jira/browse/HIVE-2564 > Project: Hive > Issue Type: Improvement > Components: JDBC >Affects Versions: 0.7.1, 0.12.0 >Reporter: Shinsuke Sugaya >Priority: Critical > Labels: patch > Attachments: HIVE-2564.1.patch, HIVE-2564.2.patch, HIVE-2564.3.patch, > hive-2564.patch > > > The current Hive implementation ignores a database name at JDBC URL, > though we can set it by executing "use " statement. > I think it is better to also specify a database name at JDBC URL or database > properties. > Therefore, I'll attach the patch. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (HIVE-2564) Set dbname at JDBC URL or properties
[ https://issues.apache.org/jira/browse/HIVE-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick White updated HIVE-2564: - Priority: Critical (was: Major) Affects Version/s: 0.12.0 > Set dbname at JDBC URL or properties > > > Key: HIVE-2564 > URL: https://issues.apache.org/jira/browse/HIVE-2564 > Project: Hive > Issue Type: Improvement > Components: JDBC >Affects Versions: 0.7.1, 0.12.0 >Reporter: Shinsuke Sugaya >Priority: Critical > Labels: patch > Attachments: HIVE-2564.1.patch, HIVE-2564.2.patch, HIVE-2564.3.patch, > hive-2564.patch > > > The current Hive implementation ignores a database name at JDBC URL, > though we can set it by executing "use " statement. > I think it is better to also specify a database name at JDBC URL or database > properties. > Therefore, I'll attach the patch. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (HIVE-2564) Set dbname at JDBC URL or properties
[ https://issues.apache.org/jira/browse/HIVE-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick White updated HIVE-2564: - Attachment: HIVE-2564.3.patch I've attached a rebased patch > Set dbname at JDBC URL or properties > > > Key: HIVE-2564 > URL: https://issues.apache.org/jira/browse/HIVE-2564 > Project: Hive > Issue Type: Improvement > Components: JDBC >Affects Versions: 0.7.1, 0.12.0 >Reporter: Shinsuke Sugaya > Labels: patch > Attachments: HIVE-2564.1.patch, HIVE-2564.2.patch, HIVE-2564.3.patch, > hive-2564.patch > > > The current Hive implementation ignores a database name at JDBC URL, > though we can set it by executing "use " statement. > I think it is better to also specify a database name at JDBC URL or database > properties. > Therefore, I'll attach the patch. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (HIVE-6426) Metastore Doesn't Log Reason for Datastore Failure when Retrying
[ https://issues.apache.org/jira/browse/HIVE-6426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick White updated HIVE-6426: - Attachment: HIVE-6426.patch > Metastore Doesn't Log Reason for Datastore Failure when Retrying > > > Key: HIVE-6426 > URL: https://issues.apache.org/jira/browse/HIVE-6426 > Project: Hive > Issue Type: Bug > Components: Metastore >Affects Versions: 0.12.0 >Reporter: Nick White > Attachments: HIVE-6426.patch > > > The metastore only logs a messages like "JDO datastore error. Retrying > metastore command after %d ms (attempt %d of %d)", but doesn't include the > reason why the command failed. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (HIVE-6426) Metastore Doesn't Log Reason for Datastore Failure when Retrying
[ https://issues.apache.org/jira/browse/HIVE-6426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick White updated HIVE-6426: - Status: Patch Available (was: Open) > Metastore Doesn't Log Reason for Datastore Failure when Retrying > > > Key: HIVE-6426 > URL: https://issues.apache.org/jira/browse/HIVE-6426 > Project: Hive > Issue Type: Bug > Components: Metastore >Affects Versions: 0.12.0 >Reporter: Nick White > Attachments: HIVE-6426.patch > > > The metastore only logs a messages like "JDO datastore error. Retrying > metastore command after %d ms (attempt %d of %d)", but doesn't include the > reason why the command failed. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (HIVE-6426) Metastore Doesn't Log Reason for Datastore Failure when Retrying
Nick White created HIVE-6426: Summary: Metastore Doesn't Log Reason for Datastore Failure when Retrying Key: HIVE-6426 URL: https://issues.apache.org/jira/browse/HIVE-6426 Project: Hive Issue Type: Bug Components: Metastore Affects Versions: 0.12.0 Reporter: Nick White The metastore only logs a messages like "JDO datastore error. Retrying metastore command after %d ms (attempt %d of %d)", but doesn't include the reason why the command failed. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (HIVE-6423) Read Timestamps and Dates from Avro files (stored as Strings in ISO format)
[ https://issues.apache.org/jira/browse/HIVE-6423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick White updated HIVE-6423: - Attachment: HIVE-6423.patch > Read Timestamps and Dates from Avro files (stored as Strings in ISO format) > --- > > Key: HIVE-6423 > URL: https://issues.apache.org/jira/browse/HIVE-6423 > Project: Hive > Issue Type: New Feature > Components: HiveServer2 >Affects Versions: 0.12.0 >Reporter: Nick White > Attachments: HIVE-6423.patch > > > Avro doesn't have native timestamp or date data types. Some tools (e.g. > apache Sqoop) work around this by adding the java.sql.Types type number as an > "sqlType" attribute to the Avro schema JSON field element. The attached patch > makes the Avro SerDe look for an sqlType attribute, and if it is a Hive > primitive type that's not an Avro primitive type (i.e. timestamp and date) it > returns the appropriate Hive type (the one corresponding to the SQL type). -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (HIVE-6423) Read Timestamps and Dates from Avro files (stored as Strings in ISO format)
[ https://issues.apache.org/jira/browse/HIVE-6423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick White updated HIVE-6423: - Status: Patch Available (was: Open) > Read Timestamps and Dates from Avro files (stored as Strings in ISO format) > --- > > Key: HIVE-6423 > URL: https://issues.apache.org/jira/browse/HIVE-6423 > Project: Hive > Issue Type: New Feature > Components: HiveServer2 >Affects Versions: 0.12.0 >Reporter: Nick White > Attachments: HIVE-6423.patch > > > Avro doesn't have native timestamp or date data types. Some tools (e.g. > apache Sqoop) work around this by adding the java.sql.Types type number as an > "sqlType" attribute to the Avro schema JSON field element. The attached patch > makes the Avro SerDe look for an sqlType attribute, and if it is a Hive > primitive type that's not an Avro primitive type (i.e. timestamp and date) it > returns the appropriate Hive type (the one corresponding to the SQL type). -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (HIVE-6423) Read Timestamps and Dates from Avro files (stored as Strings in ISO format)
Nick White created HIVE-6423: Summary: Read Timestamps and Dates from Avro files (stored as Strings in ISO format) Key: HIVE-6423 URL: https://issues.apache.org/jira/browse/HIVE-6423 Project: Hive Issue Type: New Feature Components: HiveServer2 Affects Versions: 0.12.0 Reporter: Nick White Avro doesn't have native timestamp or date data types. Some tools (e.g. apache Sqoop) work around this by adding the java.sql.Types type number as an "sqlType" attribute to the Avro schema JSON field element. The attached patch makes the Avro SerDe look for an sqlType attribute, and if it is a Hive primitive type that's not an Avro primitive type (i.e. timestamp and date) it returns the appropriate Hive type (the one corresponding to the SQL type). -- This message was sent by Atlassian JIRA (v6.1.5#6160)
