[jira] [Created] (HIVE-8664) Use curator in JDBC Driver and HiveServer2 for better reliability
Vaibhav Gumashta created HIVE-8664: -- Summary: Use curator in JDBC Driver and HiveServer2 for better reliability Key: HIVE-8664 URL: https://issues.apache.org/jira/browse/HIVE-8664 Project: Hive Issue Type: Bug Components: HiveServer2, JDBC Affects Versions: 0.14.0 Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Curator provides well defined reliability on top of ZooKeeper. Should be using that instead of plain ZooKeeper clients. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-8664) Use Apache Curator in JDBC Driver and HiveServer2 for better reliability
[ https://issues.apache.org/jira/browse/HIVE-8664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-8664: --- Summary: Use Apache Curator in JDBC Driver and HiveServer2 for better reliability (was: Use curator in JDBC Driver and HiveServer2 for better reliability) Use Apache Curator in JDBC Driver and HiveServer2 for better reliability Key: HIVE-8664 URL: https://issues.apache.org/jira/browse/HIVE-8664 Project: Hive Issue Type: Bug Components: HiveServer2, JDBC Affects Versions: 0.14.0 Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Curator provides well defined reliability on top of ZooKeeper. Should be using that instead of plain ZooKeeper clients. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Review Request 27362: Use Apache Curator in JDBC Driver and HiveServer2 for better reliability
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27362/ --- Review request for hive and Thejas Nair. Bugs: HIVE-8664 https://issues.apache.org/jira/browse/HIVE-8664 Repository: hive-git Description --- https://issues.apache.org/jira/browse/HIVE-8664 Diffs - jdbc/pom.xml 9a569d1 jdbc/src/java/org/apache/hive/jdbc/Utils.java d53cde7 jdbc/src/java/org/apache/hive/jdbc/ZooKeeperHiveClientHelper.java 3e4f4e5 pom.xml 69f4413 service/pom.xml 9d47a69 service/src/java/org/apache/hive/service/server/HiveServer2.java 0aab3f9 Diff: https://reviews.apache.org/r/27362/diff/ Testing --- Manual testing with ZK. Thanks, Vaibhav Gumashta
[jira] [Updated] (HIVE-8664) Use Apache Curator in JDBC Driver and HiveServer2 for better reliability
[ https://issues.apache.org/jira/browse/HIVE-8664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-8664: --- Status: Patch Available (was: Open) Use Apache Curator in JDBC Driver and HiveServer2 for better reliability Key: HIVE-8664 URL: https://issues.apache.org/jira/browse/HIVE-8664 Project: Hive Issue Type: Bug Components: HiveServer2, JDBC Affects Versions: 0.14.0 Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Attachments: HIVE-8664.1.patch Curator provides well defined reliability on top of ZooKeeper. Should be using that instead of plain ZooKeeper clients. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-8664) Use Apache Curator in JDBC Driver and HiveServer2 for better reliability
[ https://issues.apache.org/jira/browse/HIVE-8664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-8664: --- Attachment: HIVE-8664.1.patch Use Apache Curator in JDBC Driver and HiveServer2 for better reliability Key: HIVE-8664 URL: https://issues.apache.org/jira/browse/HIVE-8664 Project: Hive Issue Type: Bug Components: HiveServer2, JDBC Affects Versions: 0.14.0 Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Attachments: HIVE-8664.1.patch Curator provides well defined reliability on top of ZooKeeper. Should be using that instead of plain ZooKeeper clients. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HIVE-8664) Use Apache Curator in JDBC Driver and HiveServer2 for better reliability
[ https://issues.apache.org/jira/browse/HIVE-8664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14189521#comment-14189521 ] Vaibhav Gumashta commented on HIVE-8664: [~hagleitn] Possible to add this to 14? W/o this there might be some issues with dynamic service discovery in HS2. Use Apache Curator in JDBC Driver and HiveServer2 for better reliability Key: HIVE-8664 URL: https://issues.apache.org/jira/browse/HIVE-8664 Project: Hive Issue Type: Bug Components: HiveServer2, JDBC Affects Versions: 0.14.0 Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Attachments: HIVE-8664.1.patch Curator provides well defined reliability on top of ZooKeeper. Should be using that instead of plain ZooKeeper clients. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 27263: HIVE-8615 : beeline csv, tsv outputformat needs backward compatibility mode
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27263/#review58777 --- Ship it! Ship It! - Vaibhav Gumashta On Oct. 28, 2014, 3:12 a.m., Thejas Nair wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27263/ --- (Updated Oct. 28, 2014, 3:12 a.m.) Review request for hive and Vaibhav Gumashta. Bugs: HIVE-8615 https://issues.apache.org/jira/browse/HIVE-8615 Repository: hive-git Description --- https://issues.apache.org/jira/browse/HIVE-8615 Diffs - beeline/src/java/org/apache/hive/beeline/BeeLine.java e3c2449 beeline/src/java/org/apache/hive/beeline/BeeLineOpts.java 2a0e9b5 beeline/src/java/org/apache/hive/beeline/DeprecatedSeparatedValuesOutputFormat.java PRE-CREATION beeline/src/java/org/apache/hive/beeline/SeparatedValuesOutputFormat.java 6bbb046 beeline/src/main/resources/BeeLine.properties d40c0dc itests/hive-unit/src/test/java/org/apache/hive/beeline/TestBeeLineWithArgs.java 0947b8d Diff: https://reviews.apache.org/r/27263/diff/ Testing --- tests added Thanks, Thejas Nair
[jira] [Commented] (HIVE-8615) beeline csv,tsv outputformat needs backward compatibility mode
[ https://issues.apache.org/jira/browse/HIVE-8615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14186485#comment-14186485 ] Vaibhav Gumashta commented on HIVE-8615: +1. Thanks for adding MiniHS2 to the test! beeline csv,tsv outputformat needs backward compatibility mode -- Key: HIVE-8615 URL: https://issues.apache.org/jira/browse/HIVE-8615 Project: Hive Issue Type: Bug Components: Beeline Affects Versions: 0.14.0 Reporter: Thejas M Nair Assignee: Thejas M Nair Priority: Critical Fix For: 0.14.0 Attachments: HIVE-8615.1.patch, HIVE-8615.2.patch Changes in HIVE-7390 break backward compatibility for beeline csv and tsv formats. This can cause problems for users upgrading to hive 0.14, if they have code for parsing the old output format. Instead of removing the old format in this release, we should consider it deprecated and support it in a few releases before removing it completely. Incompatible Changes in the tsv and csv formats- - Old format quoted every field. New format quotes only fields that contain a delimiter or the quoteing char. - Old format quoted using single quotes, new format quotes using double quotes - Old format didn't escape quotes in a field (a bug). New format does escape the quotes -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HIVE-8579) Guaranteed NPE in DDLSemanticAnalyzer
[
https://issues.apache.org/jira/browse/HIVE-8579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14186490#comment-14186490
]
Vaibhav Gumashta commented on HIVE-8579:
+1
Guaranteed NPE in DDLSemanticAnalyzer
-
Key: HIVE-8579
URL: https://issues.apache.org/jira/browse/HIVE-8579
Project: Hive
Issue Type: Bug
Reporter: Lars Francke
Assignee: Jason Dere
Attachments: HIVE-8579.1.patch, HIVE-8579.1.patch
This was added by [~jdere] in HIVE-8411. I don't fully understand the code
(i.e. what it means when desc is null) but I'm sure, Jason, you can fix it
without much trouble?
{code}
if (desc == null ||
!AlterTableDesc.doesAlterTableTypeSupportPartialPartitionSpec(desc.getOp())) {
throw new SemanticException(
ErrorMsg.ALTER_TABLE_TYPE_PARTIAL_PARTITION_SPEC_NO_SUPPORTED,
desc.getOp().name());
} else if (!conf.getBoolVar(HiveConf.ConfVars.DYNAMICPARTITIONING)) {
throw new SemanticException(ErrorMsg.DYNAMIC_PARTITION_DISABLED);
}
{code}
You check for whether {{desc}} is null but then use it to do {{desc.getOp()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HIVE-8544) Beeline SeparatedValuesOutputFormat (csv/tsv/dsv) wraps the results with extra double quotes
[
https://issues.apache.org/jira/browse/HIVE-8544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vaibhav Gumashta updated HIVE-8544:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Beeline SeparatedValuesOutputFormat (csv/tsv/dsv) wraps the results with
extra double quotes
--
Key: HIVE-8544
URL: https://issues.apache.org/jira/browse/HIVE-8544
Project: Hive
Issue Type: Bug
Components: CLI, JDBC
Affects Versions: 0.14.0
Reporter: Vaibhav Gumashta
Assignee: Vaibhav Gumashta
Attachments: HIVE-8544.1.patch
Noticed additional double quotes in select * complex datatypes output
while running it through HiveServer2/Beeline
Actual
{noformat}
[18,19] {col1:alice brown,col2:18}{alice
brown:18}
[18,19] {col1:alice garcia,col2:18} {alice
garcia:18}
[18,19] {col1:alice garcia,col2:18} {alice
garcia:18}
[18,19] {col1:alice thompson,col2:18} {alice
thompson:18}
[18,19] {col1:alice xylophone,col2:18}{alice
xylophone:18}
[18,19] {col1:bob hernandez,col2:18} {bob
hernandez:18}
[18,19] {col1:bob ichabod,col2:18}{bob
ichabod:18}
{noformat}
Expected
{noformat}
[18,19] {col1:alice brown,col2:18}{alice brown:18}
[18,19] {col1:alice garcia,col2:18} {alice garcia:18}
[18,19] {col1:alice garcia,col2:18} {alice garcia:18}
[18,19] {col1:alice thompson,col2:18} {alice thompson:18}
[18,19] {col1:alice xylophone,col2:18}{alice xylophone:18}
[18,19] {col1:bob hernandez,col2:18} {bob hernandez:18}
[18,19] {col1:bob ichabod,col2:18}{bob ichabod:18}
{noformat}
Run these queries through HiveServer2 to reproduce the issue:
{noformat}
create table insert_9 (a arrayint, b structcol1:string,col2:int, c
mapstring, int);
insert overwrite table insert_9 select array(age, age+1), struct(name, age),
map(name, age) from studenttab10k;
select * from insert_9;
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HIVE-8544) Beeline SeparatedValuesOutputFormat (csv/tsv/dsv) wraps the results with extra double quotes
[
https://issues.apache.org/jira/browse/HIVE-8544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14186495#comment-14186495
]
Vaibhav Gumashta commented on HIVE-8544:
Resolving this as HIVE-8615 supersedes this.
Beeline SeparatedValuesOutputFormat (csv/tsv/dsv) wraps the results with
extra double quotes
--
Key: HIVE-8544
URL: https://issues.apache.org/jira/browse/HIVE-8544
Project: Hive
Issue Type: Bug
Components: CLI, JDBC
Affects Versions: 0.14.0
Reporter: Vaibhav Gumashta
Assignee: Vaibhav Gumashta
Attachments: HIVE-8544.1.patch
Noticed additional double quotes in select * complex datatypes output
while running it through HiveServer2/Beeline
Actual
{noformat}
[18,19] {col1:alice brown,col2:18}{alice
brown:18}
[18,19] {col1:alice garcia,col2:18} {alice
garcia:18}
[18,19] {col1:alice garcia,col2:18} {alice
garcia:18}
[18,19] {col1:alice thompson,col2:18} {alice
thompson:18}
[18,19] {col1:alice xylophone,col2:18}{alice
xylophone:18}
[18,19] {col1:bob hernandez,col2:18} {bob
hernandez:18}
[18,19] {col1:bob ichabod,col2:18}{bob
ichabod:18}
{noformat}
Expected
{noformat}
[18,19] {col1:alice brown,col2:18}{alice brown:18}
[18,19] {col1:alice garcia,col2:18} {alice garcia:18}
[18,19] {col1:alice garcia,col2:18} {alice garcia:18}
[18,19] {col1:alice thompson,col2:18} {alice thompson:18}
[18,19] {col1:alice xylophone,col2:18}{alice xylophone:18}
[18,19] {col1:bob hernandez,col2:18} {bob hernandez:18}
[18,19] {col1:bob ichabod,col2:18}{bob ichabod:18}
{noformat}
Run these queries through HiveServer2 to reproduce the issue:
{noformat}
create table insert_9 (a arrayint, b structcol1:string,col2:int, c
mapstring, int);
insert overwrite table insert_9 select array(age, age+1), struct(name, age),
map(name, age) from studenttab10k;
select * from insert_9;
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HIVE-8392) HiveServer2 Operation.close fails on windows
[
https://issues.apache.org/jira/browse/HIVE-8392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14186654#comment-14186654
]
Vaibhav Gumashta commented on HIVE-8392:
[~hagleitn] I'll upload one in next couple of days.
HiveServer2 Operation.close fails on windows
Key: HIVE-8392
URL: https://issues.apache.org/jira/browse/HIVE-8392
Project: Hive
Issue Type: Bug
Components: HiveServer2
Affects Versions: 0.14.0
Reporter: Vaibhav Gumashta
Assignee: Vaibhav Gumashta
Priority: Critical
Fix For: 0.14.0
{code}
java.io.IOException: Unable to delete file:
C:\Users\HADOOP~1.ONP\AppData\Local\Temp\hadoop\operation_logs\ac7d4f51-d9b9-4189-b248-6e8d5e3102af\4b1f1153-5c0c-4741-8f53-1f1b6ed9b190
at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:2279)
at
org.apache.hive.service.cli.operation.OperationLog$LogFile.remove(OperationLog.java:131)
at
org.apache.hive.service.cli.operation.OperationLog.close(OperationLog.java:95)
at
org.apache.hive.service.cli.operation.Operation.cleanupOperationLog(Operation.java:268)
at
org.apache.hive.service.cli.operation.SQLOperation.close(SQLOperation.java:307)
at
org.apache.hive.service.cli.operation.OperationManager.closeOperation(OperationManager.java:215)
at
org.apache.hive.service.cli.session.HiveSessionImpl.closeOperation(HiveSessionImpl.java:640)
at
org.apache.hive.service.cli.CLIService.closeOperation(CLIService.java:392)
at
org.apache.hive.service.cli.thrift.ThriftCLIService.CloseOperation(ThriftCLIService.java:573)
at
org.apache.hive.service.cli.thrift.TCLIService$Processor$CloseOperation.getResult(TCLIService.java:1513)
at
org.apache.hive.service.cli.thrift.TCLIService$Processor$CloseOperation.getResult(TCLIService.java:1498)
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
at
org.apache.hive.service.auth.TSetIpAddressProcessor.process(TSetIpAddressProcessor.java:56)
at
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:206)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{code}
On windows, close needs to be called before delete.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Review Request 27216: HIVE-8557 : automatically setup ZooKeeperTokenStore to use kerberos authentication when kerberos is enabled
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27216/#review58841 --- common/src/java/org/apache/hadoop/hive/conf/HiveConf.java https://reviews.apache.org/r/27216/#comment9 Should we mention our preference for using hive.zookeeper.quorum? common/src/java/org/apache/hadoop/hive/conf/HiveConf.java https://reviews.apache.org/r/27216/#comment5 Was the original config a comma separated list of ACLs or a list of servers? This description (original version) looks confusing... service/src/java/org/apache/hive/service/server/HiveServer2.java https://reviews.apache.org/r/27216/#comment100054 Minor nit: I just noticed that setZookeeperClientJaasConfig is setting the JAAS config specific to Kerberos authentication. Currently ZK SASL implementation seems to support only Kerberos login module, but it seems likely that this will get expanded to support other SASL auth modules. In that case if we decide to use it to set up ACLs, we might want to indicate that this method specifically sets up Kerberos JAAS Config. shims/common-secure/src/main/java/org/apache/hadoop/hive/shims/HadoopShimsSecure.java https://reviews.apache.org/r/27216/#comment12 Unintentional change? shims/common-secure/src/main/java/org/apache/hadoop/hive/thrift/ZooKeeperTokenStore.java https://reviews.apache.org/r/27216/#comment100070 I'm just wondering if after opening the client connection (which will do the authentication), we should restore the original JAAS config in the runtime. Just wondering if we can get into an inconsistent state with multiple JAAS logins happening. shims/common-secure/src/main/java/org/apache/hadoop/hive/thrift/ZooKeeperTokenStore.java https://reviews.apache.org/r/27216/#comment100010 The doc needs to use TokenStoreException. shims/common-secure/src/main/java/org/apache/hadoop/hive/thrift/ZooKeeperTokenStore.java https://reviews.apache.org/r/27216/#comment100016 Nit: it will be good to have a self documenting variable name instead of csv. - Vaibhav Gumashta On Oct. 28, 2014, 6:35 a.m., Thejas Nair wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27216/ --- (Updated Oct. 28, 2014, 6:35 a.m.) Review request for hive, Eugene Koifman and Vaibhav Gumashta. Bugs: HIVE-8557 https://issues.apache.org/jira/browse/HIVE-8557 Repository: hive-git Description --- https://issues.apache.org/jira/browse/HIVE-8557 Diffs - common/src/java/org/apache/hadoop/hive/conf/HiveConf.java 7d8e5bc hcatalog/webhcat/svr/pom.xml 6065748 itests/hive-unit-hadoop2/src/test/java/org/apache/hadoop/hive/thrift/TestHadoop20SAuthBridge.java b81942a itests/hive-unit/src/test/java/org/apache/hadoop/hive/thrift/TestDBTokenStore.java 8860d30 itests/hive-unit/src/test/java/org/apache/hadoop/hive/thrift/TestZooKeeperTokenStore.java 83a80b4 metastore/src/java/org/apache/hadoop/hive/metastore/HiveMetaStore.java 3cf43a9 pom.xml c694980 ql/src/java/org/apache/hadoop/hive/ql/util/ZooKeeperHiveHelper.java 11dd962 service/src/java/org/apache/hive/service/auth/HiveAuthFactory.java ab34d2d service/src/java/org/apache/hive/service/server/HiveServer2.java 0aab3f9 shims/0.20/src/main/java/org/apache/hadoop/hive/shims/Hadoop20Shims.java d18ae44 shims/common-secure/pom.xml 98b5ca1 shims/common-secure/src/main/java/org/apache/hadoop/hive/shims/HadoopShimsSecure.java 606f973 shims/common-secure/src/main/java/org/apache/hadoop/hive/thrift/DBTokenStore.java 0bb2763 shims/common-secure/src/main/java/org/apache/hadoop/hive/thrift/DelegationTokenStore.java f3c2e48 shims/common-secure/src/main/java/org/apache/hadoop/hive/thrift/HadoopThriftAuthBridge20S.java 56735d8 shims/common-secure/src/main/java/org/apache/hadoop/hive/thrift/MemoryTokenStore.java 9908aa4 shims/common-secure/src/main/java/org/apache/hadoop/hive/thrift/TokenStoreDelegationTokenSecretManager.java 4ccf895 shims/common-secure/src/main/java/org/apache/hadoop/hive/thrift/ZooKeeperTokenStore.java 8683496 shims/common/src/main/java/org/apache/hadoop/hive/shims/HadoopShims.java 9850405 shims/common/src/main/java/org/apache/hadoop/hive/thrift/HadoopThriftAuthBridge.java d0d6c7b Diff: https://reviews.apache.org/r/27216/diff/ Testing --- Existing tests excercised, manually tested in a cluster. Thanks, Thejas Nair
[jira] [Commented] (HIVE-8557) automatically setup ZooKeeperTokenStore to use kerberos authentication when kerberos is enabled
[ https://issues.apache.org/jira/browse/HIVE-8557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14187627#comment-14187627 ] Vaibhav Gumashta commented on HIVE-8557: [~thejas] Some minor comments on review board. Otherwise looks good. Thanks! automatically setup ZooKeeperTokenStore to use kerberos authentication when kerberos is enabled --- Key: HIVE-8557 URL: https://issues.apache.org/jira/browse/HIVE-8557 Project: Hive Issue Type: Bug Reporter: Thejas M Nair Assignee: Thejas M Nair Fix For: 0.14.0 Attachments: HIVE-8557.1.patch, HIVE-8557.2.patch ZooKeeperTokenStore does not automatically setup the zookeeper client to use kerberos authentication to talk to zookeeper, it requires additional configuration. If kerberos is enabled in the configuration, it makes sense to do this configuration for zookeeper client automatically. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 27216: HIVE-8557 : automatically setup ZooKeeperTokenStore to use kerberos authentication when kerberos is enabled
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27216/#review58961 --- Ship it! Ship It! - Vaibhav Gumashta On Oct. 29, 2014, 12:29 a.m., Thejas Nair wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27216/ --- (Updated Oct. 29, 2014, 12:29 a.m.) Review request for hive, Eugene Koifman and Vaibhav Gumashta. Bugs: HIVE-8557 https://issues.apache.org/jira/browse/HIVE-8557 Repository: hive-git Description --- https://issues.apache.org/jira/browse/HIVE-8557 Diffs - common/src/java/org/apache/hadoop/hive/conf/HiveConf.java 7d8e5bc hcatalog/webhcat/svr/pom.xml 6065748 itests/hive-unit-hadoop2/src/test/java/org/apache/hadoop/hive/thrift/TestHadoop20SAuthBridge.java b81942a itests/hive-unit/src/test/java/org/apache/hadoop/hive/thrift/TestDBTokenStore.java 8860d30 itests/hive-unit/src/test/java/org/apache/hadoop/hive/thrift/TestZooKeeperTokenStore.java 83a80b4 metastore/src/java/org/apache/hadoop/hive/metastore/HiveMetaStore.java 3cf43a9 pom.xml c694980 ql/src/java/org/apache/hadoop/hive/ql/util/ZooKeeperHiveHelper.java 11dd962 service/src/java/org/apache/hive/service/auth/HiveAuthFactory.java ab34d2d service/src/java/org/apache/hive/service/server/HiveServer2.java 0aab3f9 shims/0.20/src/main/java/org/apache/hadoop/hive/shims/Hadoop20Shims.java d18ae44 shims/common-secure/pom.xml 98b5ca1 shims/common-secure/src/main/java/org/apache/hadoop/hive/shims/HadoopShimsSecure.java 606f973 shims/common-secure/src/main/java/org/apache/hadoop/hive/thrift/DBTokenStore.java 0bb2763 shims/common-secure/src/main/java/org/apache/hadoop/hive/thrift/DelegationTokenStore.java f3c2e48 shims/common-secure/src/main/java/org/apache/hadoop/hive/thrift/HadoopThriftAuthBridge20S.java 56735d8 shims/common-secure/src/main/java/org/apache/hadoop/hive/thrift/MemoryTokenStore.java 9908aa4 shims/common-secure/src/main/java/org/apache/hadoop/hive/thrift/TokenStoreDelegationTokenSecretManager.java 4ccf895 shims/common-secure/src/main/java/org/apache/hadoop/hive/thrift/ZooKeeperTokenStore.java 8683496 shims/common/src/main/java/org/apache/hadoop/hive/shims/HadoopShims.java 9850405 shims/common/src/main/java/org/apache/hadoop/hive/thrift/HadoopThriftAuthBridge.java d0d6c7b Diff: https://reviews.apache.org/r/27216/diff/ Testing --- Existing tests excercised, manually tested in a cluster. Thanks, Thejas Nair
[jira] [Commented] (HIVE-8557) automatically setup ZooKeeperTokenStore to use kerberos authentication when kerberos is enabled
[ https://issues.apache.org/jira/browse/HIVE-8557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14187963#comment-14187963 ] Vaibhav Gumashta commented on HIVE-8557: +1 automatically setup ZooKeeperTokenStore to use kerberos authentication when kerberos is enabled --- Key: HIVE-8557 URL: https://issues.apache.org/jira/browse/HIVE-8557 Project: Hive Issue Type: Bug Reporter: Thejas M Nair Assignee: Thejas M Nair Fix For: 0.14.0 Attachments: HIVE-8557.1.patch, HIVE-8557.2.patch, HIVE-8557.3.patch, HIVE-8557.4.patch ZooKeeperTokenStore does not automatically setup the zookeeper client to use kerberos authentication to talk to zookeeper, it requires additional configuration. If kerberos is enabled in the configuration, it makes sense to do this configuration for zookeeper client automatically. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HIVE-7353) HiveServer2 using embedded MetaStore leaks JDOPersistanceManager
[ https://issues.apache.org/jira/browse/HIVE-7353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14185840#comment-14185840 ] Vaibhav Gumashta commented on HIVE-7353: [~leftylev] Ah, didn't realize that a parameter was added here. Adding back the todoc tag. Thanks for pointing out! HiveServer2 using embedded MetaStore leaks JDOPersistanceManager Key: HIVE-7353 URL: https://issues.apache.org/jira/browse/HIVE-7353 Project: Hive Issue Type: Bug Components: HiveServer2 Affects Versions: 0.13.0 Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Fix For: 0.14.0 Attachments: HIVE-7353.1.patch, HIVE-7353.2.patch, HIVE-7353.3.patch, HIVE-7353.4.patch, HIVE-7353.5.patch, HIVE-7353.6.patch, HIVE-7353.7.patch, HIVE-7353.8.patch, HIVE-7353.9.patch While using embedded metastore, while creating background threads to run async operations, HiveServer2 ends up creating new instances of JDOPersistanceManager which are cached in JDOPersistanceManagerFactory. Even when the background thread is killed by the thread pool manager, the JDOPersistanceManager are never GCed because they are cached by JDOPersistanceManagerFactory. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-7353) HiveServer2 using embedded MetaStore leaks JDOPersistanceManager
[ https://issues.apache.org/jira/browse/HIVE-7353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-7353: --- Labels: TODOC14 (was: ) HiveServer2 using embedded MetaStore leaks JDOPersistanceManager Key: HIVE-7353 URL: https://issues.apache.org/jira/browse/HIVE-7353 Project: Hive Issue Type: Bug Components: HiveServer2 Affects Versions: 0.13.0 Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Labels: TODOC14 Fix For: 0.14.0 Attachments: HIVE-7353.1.patch, HIVE-7353.2.patch, HIVE-7353.3.patch, HIVE-7353.4.patch, HIVE-7353.5.patch, HIVE-7353.6.patch, HIVE-7353.7.patch, HIVE-7353.8.patch, HIVE-7353.9.patch While using embedded metastore, while creating background threads to run async operations, HiveServer2 ends up creating new instances of JDOPersistanceManager which are cached in JDOPersistanceManagerFactory. Even when the background thread is killed by the thread pool manager, the JDOPersistanceManager are never GCed because they are cached by JDOPersistanceManagerFactory. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [ANNOUNCE] New Hive PMC Member - Alan Gates
Congratulations Alan! On Mon, Oct 27, 2014 at 3:54 PM, Chris Drome cdr...@yahoo-inc.com wrote: Congratulations Alan! From: Carl Steinbach c...@apache.org Reply-To: u...@hive.apache.org u...@hive.apache.org Date: Monday, October 27, 2014 at 3:38 PM To: dev@hive.apache.org dev@hive.apache.org, u...@hive.apache.org u...@hive.apache.org, ga...@apache.org ga...@apache.org Subject: [ANNOUNCE] New Hive PMC Member - Alan Gates I am pleased to announce that Alan Gates has been elected to the Hive Project Management Committee. Please join me in congratulating Alan! Thanks. - Carl -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
[jira] [Commented] (HIVE-8596) HiveServer2 dynamic service discovery: ZK throws too many connections error
[
https://issues.apache.org/jira/browse/HIVE-8596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14184712#comment-14184712
]
Vaibhav Gumashta commented on HIVE-8596:
The failed test is flaky. I'll commit this shortly.
HiveServer2 dynamic service discovery: ZK throws too many connections error
---
Key: HIVE-8596
URL: https://issues.apache.org/jira/browse/HIVE-8596
Project: Hive
Issue Type: Bug
Components: HiveServer2, JDBC
Affects Versions: 0.14.0
Reporter: Vaibhav Gumashta
Assignee: Vaibhav Gumashta
Priority: Critical
Fix For: 0.14.0
Attachments: HIVE-8596.1.patch, HIVE-8596.2.patch
{noformat}
2014-10-23 07:55:44,221 - WARN
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@193] - Too
many connections from /172.31.47.11 - max is 60
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HIVE-8596) HiveServer2 dynamic service discovery: ZK throws too many connections error
[
https://issues.apache.org/jira/browse/HIVE-8596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vaibhav Gumashta updated HIVE-8596:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and 14. Thanks for reviewing [~thejas]!
HiveServer2 dynamic service discovery: ZK throws too many connections error
---
Key: HIVE-8596
URL: https://issues.apache.org/jira/browse/HIVE-8596
Project: Hive
Issue Type: Bug
Components: HiveServer2, JDBC
Affects Versions: 0.14.0
Reporter: Vaibhav Gumashta
Assignee: Vaibhav Gumashta
Priority: Critical
Fix For: 0.14.0
Attachments: HIVE-8596.1.patch, HIVE-8596.2.patch
{noformat}
2014-10-23 07:55:44,221 - WARN
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@193] - Too
many connections from /172.31.47.11 - max is 60
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HIVE-8568) Add HS2 API to fetch Job IDs for a given query
[ https://issues.apache.org/jira/browse/HIVE-8568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14184337#comment-14184337 ] Vaibhav Gumashta commented on HIVE-8568: [~mohitsabharwal] Thanks for the useful work. I just begun reviewing the patch and will go over the entire patch soon. I have one preliminary comment on the design: did you consider expanding the GetOperationStatus call? On a quick pass it seems that it will be better to expand the GetOperationStatus method rather than adding a new API method. At a high level, GetOperationStatus is also meant ( used) to poll on a running Operation and get its execution status. Add HS2 API to fetch Job IDs for a given query -- Key: HIVE-8568 URL: https://issues.apache.org/jira/browse/HIVE-8568 Project: Hive Issue Type: Bug Reporter: Mohit Sabharwal Assignee: Mohit Sabharwal Attachments: HIVE-8568.1.patch, HIVE-8568.patch Fetching Job IDs corresponding to all running MR/Tez tasks is useful for clients like Hue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HIVE-8596) HiveServer2 dynamic service discovery: ZK throws too many connections error
Vaibhav Gumashta created HIVE-8596:
--
Summary: HiveServer2 dynamic service discovery: ZK throws too many
connections error
Key: HIVE-8596
URL: https://issues.apache.org/jira/browse/HIVE-8596
Project: Hive
Issue Type: Bug
Components: HiveServer2, JDBC
Affects Versions: 0.14.0
Reporter: Vaibhav Gumashta
Assignee: Vaibhav Gumashta
Priority: Critical
{noformat}
2014-10-23 07:55:44,221 - WARN
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@193] - Too many
connections from /172.31.47.11 - max is 60
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HIVE-8596) HiveServer2 dynamic service discovery: ZK throws too many connections error
[
https://issues.apache.org/jira/browse/HIVE-8596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14183169#comment-14183169
]
Vaibhav Gumashta commented on HIVE-8596:
[~vikram.dixit] This will be an issue with concurrent use. I feel this should
be resolved in 14.
cc [~thejas]
HiveServer2 dynamic service discovery: ZK throws too many connections error
---
Key: HIVE-8596
URL: https://issues.apache.org/jira/browse/HIVE-8596
Project: Hive
Issue Type: Bug
Components: HiveServer2, JDBC
Affects Versions: 0.14.0
Reporter: Vaibhav Gumashta
Assignee: Vaibhav Gumashta
Priority: Critical
{noformat}
2014-10-23 07:55:44,221 - WARN
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@193] - Too
many connections from /172.31.47.11 - max is 60
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HIVE-8596) HiveServer2 dynamic service discovery: ZK throws too many connections error
[
https://issues.apache.org/jira/browse/HIVE-8596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vaibhav Gumashta updated HIVE-8596:
---
Fix Version/s: 0.14.0
HiveServer2 dynamic service discovery: ZK throws too many connections error
---
Key: HIVE-8596
URL: https://issues.apache.org/jira/browse/HIVE-8596
Project: Hive
Issue Type: Bug
Components: HiveServer2, JDBC
Affects Versions: 0.14.0
Reporter: Vaibhav Gumashta
Assignee: Vaibhav Gumashta
Priority: Critical
Fix For: 0.14.0
{noformat}
2014-10-23 07:55:44,221 - WARN
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@193] - Too
many connections from /172.31.47.11 - max is 60
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HIVE-8596) HiveServer2 dynamic service discovery: ZK throws too many connections error
[
https://issues.apache.org/jira/browse/HIVE-8596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vaibhav Gumashta updated HIVE-8596:
---
Attachment: HIVE-8596.1.patch
HiveServer2 dynamic service discovery: ZK throws too many connections error
---
Key: HIVE-8596
URL: https://issues.apache.org/jira/browse/HIVE-8596
Project: Hive
Issue Type: Bug
Components: HiveServer2, JDBC
Affects Versions: 0.14.0
Reporter: Vaibhav Gumashta
Assignee: Vaibhav Gumashta
Priority: Critical
Fix For: 0.14.0
Attachments: HIVE-8596.1.patch
{noformat}
2014-10-23 07:55:44,221 - WARN
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@193] - Too
many connections from /172.31.47.11 - max is 60
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HIVE-8596) HiveServer2 dynamic service discovery: ZK throws too many connections error
[
https://issues.apache.org/jira/browse/HIVE-8596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vaibhav Gumashta updated HIVE-8596:
---
Attachment: HIVE-8596.2.patch
[~thejas] Done.
HiveServer2 dynamic service discovery: ZK throws too many connections error
---
Key: HIVE-8596
URL: https://issues.apache.org/jira/browse/HIVE-8596
Project: Hive
Issue Type: Bug
Components: HiveServer2, JDBC
Affects Versions: 0.14.0
Reporter: Vaibhav Gumashta
Assignee: Vaibhav Gumashta
Priority: Critical
Fix For: 0.14.0
Attachments: HIVE-8596.1.patch, HIVE-8596.2.patch
{noformat}
2014-10-23 07:55:44,221 - WARN
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@193] - Too
many connections from /172.31.47.11 - max is 60
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HIVE-8596) HiveServer2 dynamic service discovery: ZK throws too many connections error
[
https://issues.apache.org/jira/browse/HIVE-8596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vaibhav Gumashta updated HIVE-8596:
---
Status: Patch Available (was: Open)
HiveServer2 dynamic service discovery: ZK throws too many connections error
---
Key: HIVE-8596
URL: https://issues.apache.org/jira/browse/HIVE-8596
Project: Hive
Issue Type: Bug
Components: HiveServer2, JDBC
Affects Versions: 0.14.0
Reporter: Vaibhav Gumashta
Assignee: Vaibhav Gumashta
Priority: Critical
Fix For: 0.14.0
Attachments: HIVE-8596.1.patch, HIVE-8596.2.patch
{noformat}
2014-10-23 07:55:44,221 - WARN
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@193] - Too
many connections from /172.31.47.11 - max is 60
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HIVE-7353) HiveServer2 using embedded MetaStore leaks JDOPersistanceManager
[ https://issues.apache.org/jira/browse/HIVE-7353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-7353: --- Labels: (was: TODOC14) HiveServer2 using embedded MetaStore leaks JDOPersistanceManager Key: HIVE-7353 URL: https://issues.apache.org/jira/browse/HIVE-7353 Project: Hive Issue Type: Bug Components: HiveServer2 Affects Versions: 0.13.0 Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Fix For: 0.14.0 Attachments: HIVE-7353.1.patch, HIVE-7353.2.patch, HIVE-7353.3.patch, HIVE-7353.4.patch, HIVE-7353.5.patch, HIVE-7353.6.patch, HIVE-7353.7.patch, HIVE-7353.8.patch, HIVE-7353.9.patch While using embedded metastore, while creating background threads to run async operations, HiveServer2 ends up creating new instances of JDOPersistanceManager which are cached in JDOPersistanceManagerFactory. Even when the background thread is killed by the thread pool manager, the JDOPersistanceManager are never GCed because they are cached by JDOPersistanceManagerFactory. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HIVE-6801) beeline kerberos authentication fails if the client principal name has hostname part
[ https://issues.apache.org/jira/browse/HIVE-6801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta resolved HIVE-6801. Resolution: Duplicate Fixed by HIVE-8246 beeline kerberos authentication fails if the client principal name has hostname part Key: HIVE-6801 URL: https://issues.apache.org/jira/browse/HIVE-6801 Project: Hive Issue Type: Improvement Components: Clients Reporter: Dilli Arumugam Assignee: Dilli Arumugam Kinited as gu...@example.com Connected successfully with beeline using command !connect jdbc:hive2://hdps.example.com:10001/default;principal=hive/hdps.example@example.com;hive.server2.proxy.user=guest?hive.server2.transport.mode=http;hive.server2.thrift.http.path=cliservice dummy dummy-pass org.apache.hive.jdbc.HiveDriver Kinited as bob/hdps.exmaple@example.com !connect jdbc:hive2://hdps.example.com:10001/default;principal=hive/hdps.example@example.com;hive.server2.proxy.user=guest?hive.server2.transport.mode=http;hive.server2.thrift.http.path=cliservice dummy dummy-pass org.apache.hive.jdbc.HiveDriver Failed with stack trace Error: Could not establish connection to jdbc:hive2://hdps.example.com:10001/default;principal=hive/hdps.example@example.com;hive.server2.proxy.user=guest?hive.server2.transport.mode=http;hive.server2.thrift.http.path=cliservice: org.apache.http.client.ClientProtocolException (state=08S01,code=0) java.sql.SQLException: Could not establish connection to jdbc:hive2://hdps.example.com:10001/default;principal=hive/hdps.example@example.com;hive.server2.proxy.user=guest?hive.server2.transport.mode=http;hive.server2.thrift.http.path=cliservice: org.apache.http.client.ClientProtocolException at org.apache.hive.jdbc.HiveConnection.openSession(HiveConnection.java:426) at org.apache.hive.jdbc.HiveConnection.init(HiveConnection.java:193) at org.apache.hive.jdbc.HiveDriver.connect(HiveDriver.java:105) at java.sql.DriverManager.getConnection(DriverManager.java:582) at java.sql.DriverManager.getConnection(DriverManager.java:154) at org.apache.hive.beeline.DatabaseConnection.connect(DatabaseConnection.java:145) at org.apache.hive.beeline.DatabaseConnection.getConnection(DatabaseConnection.java:186) at org.apache.hive.beeline.Commands.connect(Commands.java:959) at org.apache.hive.beeline.Commands.connect(Commands.java:880) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.hive.beeline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:44) at org.apache.hive.beeline.BeeLine.dispatch(BeeLine.java:792) at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:659) at org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:368) at org.apache.hive.beeline.BeeLine.main(BeeLine.java:351) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.hadoop.util.RunJar.main(RunJar.java:212) Caused by: org.apache.thrift.transport.TTransportException: org.apache.http.client.ClientProtocolException at org.apache.thrift.transport.THttpClient.flushUsingHttpClient(THttpClient.java:281) at org.apache.thrift.transport.THttpClient.flush(THttpClient.java:297) at org.apache.thrift.TServiceClient.sendBase(TServiceClient.java:65) at org.apache.hive.service.cli.thrift.TCLIService$Client.send_OpenSession(TCLIService.java:150) at org.apache.hive.service.cli.thrift.TCLIService$Client.OpenSession(TCLIService.java:142) at org.apache.hive.jdbc.HiveConnection.openSession(HiveConnection.java:415) ... 22 more Caused by: org.apache.http.client.ClientProtocolException at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:909) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:827) at org.apache.thrift.transport.THttpClient.flushUsingHttpClient(THttpClient.java:235) ... 27 more Caused by: org.apache.http.HttpException at org.apache.hive.jdbc.HttpKerberosRequestInterceptor.process(HttpKerberosRequestInterceptor.java:67
[jira] [Updated] (HIVE-8544) Beeline SeparatedValuesOutputFormat (csv/tsv/dsv) wraps the results with extra double quotes
[
https://issues.apache.org/jira/browse/HIVE-8544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vaibhav Gumashta updated HIVE-8544:
---
Fix Version/s: 0.14.0
Beeline SeparatedValuesOutputFormat (csv/tsv/dsv) wraps the results with
extra double quotes
--
Key: HIVE-8544
URL: https://issues.apache.org/jira/browse/HIVE-8544
Project: Hive
Issue Type: Bug
Components: CLI, JDBC
Affects Versions: 0.14.0
Reporter: Vaibhav Gumashta
Assignee: Vaibhav Gumashta
Fix For: 0.14.0
Attachments: HIVE-8544.1.patch
Noticed additional double quotes in select * complex datatypes output
while running it through HiveServer2/Beeline
Actual
{noformat}
[18,19] {col1:alice brown,col2:18}{alice
brown:18}
[18,19] {col1:alice garcia,col2:18} {alice
garcia:18}
[18,19] {col1:alice garcia,col2:18} {alice
garcia:18}
[18,19] {col1:alice thompson,col2:18} {alice
thompson:18}
[18,19] {col1:alice xylophone,col2:18}{alice
xylophone:18}
[18,19] {col1:bob hernandez,col2:18} {bob
hernandez:18}
[18,19] {col1:bob ichabod,col2:18}{bob
ichabod:18}
{noformat}
Expected
{noformat}
[18,19] {col1:alice brown,col2:18}{alice brown:18}
[18,19] {col1:alice garcia,col2:18} {alice garcia:18}
[18,19] {col1:alice garcia,col2:18} {alice garcia:18}
[18,19] {col1:alice thompson,col2:18} {alice thompson:18}
[18,19] {col1:alice xylophone,col2:18}{alice xylophone:18}
[18,19] {col1:bob hernandez,col2:18} {bob hernandez:18}
[18,19] {col1:bob ichabod,col2:18}{bob ichabod:18}
{noformat}
Run these queries through HiveServer2 to reproduce the issue:
{noformat}
create table insert_9 (a arrayint, b structcol1:string,col2:int, c
mapstring, int);
insert overwrite table insert_9 select array(age, age+1), struct(name, age),
map(name, age) from studenttab10k;
select * from insert_9;
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HIVE-8544) Beeline SeparatedValuesOutputFormat (csv/tsv/dsv) wraps the results with extra double quotes
[
https://issues.apache.org/jira/browse/HIVE-8544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vaibhav Gumashta updated HIVE-8544:
---
Attachment: HIVE-8544.1.patch
Beeline SeparatedValuesOutputFormat (csv/tsv/dsv) wraps the results with
extra double quotes
--
Key: HIVE-8544
URL: https://issues.apache.org/jira/browse/HIVE-8544
Project: Hive
Issue Type: Bug
Components: CLI, JDBC
Affects Versions: 0.14.0
Reporter: Vaibhav Gumashta
Assignee: Vaibhav Gumashta
Fix For: 0.14.0
Attachments: HIVE-8544.1.patch
Noticed additional double quotes in select * complex datatypes output
while running it through HiveServer2/Beeline
Actual
{noformat}
[18,19] {col1:alice brown,col2:18}{alice
brown:18}
[18,19] {col1:alice garcia,col2:18} {alice
garcia:18}
[18,19] {col1:alice garcia,col2:18} {alice
garcia:18}
[18,19] {col1:alice thompson,col2:18} {alice
thompson:18}
[18,19] {col1:alice xylophone,col2:18}{alice
xylophone:18}
[18,19] {col1:bob hernandez,col2:18} {bob
hernandez:18}
[18,19] {col1:bob ichabod,col2:18}{bob
ichabod:18}
{noformat}
Expected
{noformat}
[18,19] {col1:alice brown,col2:18}{alice brown:18}
[18,19] {col1:alice garcia,col2:18} {alice garcia:18}
[18,19] {col1:alice garcia,col2:18} {alice garcia:18}
[18,19] {col1:alice thompson,col2:18} {alice thompson:18}
[18,19] {col1:alice xylophone,col2:18}{alice xylophone:18}
[18,19] {col1:bob hernandez,col2:18} {bob hernandez:18}
[18,19] {col1:bob ichabod,col2:18}{bob ichabod:18}
{noformat}
Run these queries through HiveServer2 to reproduce the issue:
{noformat}
create table insert_9 (a arrayint, b structcol1:string,col2:int, c
mapstring, int);
insert overwrite table insert_9 select array(age, age+1), struct(name, age),
map(name, age) from studenttab10k;
select * from insert_9;
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HIVE-8544) Beeline SeparatedValuesOutputFormat (csv/tsv/dsv) wraps the results with extra double quotes
[
https://issues.apache.org/jira/browse/HIVE-8544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vaibhav Gumashta updated HIVE-8544:
---
Status: Patch Available (was: Open)
Beeline SeparatedValuesOutputFormat (csv/tsv/dsv) wraps the results with
extra double quotes
--
Key: HIVE-8544
URL: https://issues.apache.org/jira/browse/HIVE-8544
Project: Hive
Issue Type: Bug
Components: CLI, JDBC
Affects Versions: 0.14.0
Reporter: Vaibhav Gumashta
Assignee: Vaibhav Gumashta
Fix For: 0.14.0
Attachments: HIVE-8544.1.patch
Noticed additional double quotes in select * complex datatypes output
while running it through HiveServer2/Beeline
Actual
{noformat}
[18,19] {col1:alice brown,col2:18}{alice
brown:18}
[18,19] {col1:alice garcia,col2:18} {alice
garcia:18}
[18,19] {col1:alice garcia,col2:18} {alice
garcia:18}
[18,19] {col1:alice thompson,col2:18} {alice
thompson:18}
[18,19] {col1:alice xylophone,col2:18}{alice
xylophone:18}
[18,19] {col1:bob hernandez,col2:18} {bob
hernandez:18}
[18,19] {col1:bob ichabod,col2:18}{bob
ichabod:18}
{noformat}
Expected
{noformat}
[18,19] {col1:alice brown,col2:18}{alice brown:18}
[18,19] {col1:alice garcia,col2:18} {alice garcia:18}
[18,19] {col1:alice garcia,col2:18} {alice garcia:18}
[18,19] {col1:alice thompson,col2:18} {alice thompson:18}
[18,19] {col1:alice xylophone,col2:18}{alice xylophone:18}
[18,19] {col1:bob hernandez,col2:18} {bob hernandez:18}
[18,19] {col1:bob ichabod,col2:18}{bob ichabod:18}
{noformat}
Run these queries through HiveServer2 to reproduce the issue:
{noformat}
create table insert_9 (a arrayint, b structcol1:string,col2:int, c
mapstring, int);
insert overwrite table insert_9 select array(age, age+1), struct(name, age),
map(name, age) from studenttab10k;
select * from insert_9;
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HIVE-8544) Beeline SeparatedValuesOutputFormat (csv/tsv/dsv) wraps the results with extra double quotes
[
https://issues.apache.org/jira/browse/HIVE-8544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14180296#comment-14180296
]
Vaibhav Gumashta commented on HIVE-8544:
Test failure is not related.
cc [~thejas]
Beeline SeparatedValuesOutputFormat (csv/tsv/dsv) wraps the results with
extra double quotes
--
Key: HIVE-8544
URL: https://issues.apache.org/jira/browse/HIVE-8544
Project: Hive
Issue Type: Bug
Components: CLI, JDBC
Affects Versions: 0.14.0
Reporter: Vaibhav Gumashta
Assignee: Vaibhav Gumashta
Fix For: 0.14.0
Attachments: HIVE-8544.1.patch
Noticed additional double quotes in select * complex datatypes output
while running it through HiveServer2/Beeline
Actual
{noformat}
[18,19] {col1:alice brown,col2:18}{alice
brown:18}
[18,19] {col1:alice garcia,col2:18} {alice
garcia:18}
[18,19] {col1:alice garcia,col2:18} {alice
garcia:18}
[18,19] {col1:alice thompson,col2:18} {alice
thompson:18}
[18,19] {col1:alice xylophone,col2:18}{alice
xylophone:18}
[18,19] {col1:bob hernandez,col2:18} {bob
hernandez:18}
[18,19] {col1:bob ichabod,col2:18}{bob
ichabod:18}
{noformat}
Expected
{noformat}
[18,19] {col1:alice brown,col2:18}{alice brown:18}
[18,19] {col1:alice garcia,col2:18} {alice garcia:18}
[18,19] {col1:alice garcia,col2:18} {alice garcia:18}
[18,19] {col1:alice thompson,col2:18} {alice thompson:18}
[18,19] {col1:alice xylophone,col2:18}{alice xylophone:18}
[18,19] {col1:bob hernandez,col2:18} {bob hernandez:18}
[18,19] {col1:bob ichabod,col2:18}{bob ichabod:18}
{noformat}
Run these queries through HiveServer2 to reproduce the issue:
{noformat}
create table insert_9 (a arrayint, b structcol1:string,col2:int, c
mapstring, int);
insert overwrite table insert_9 select array(age, age+1), struct(name, age),
map(name, age) from studenttab10k;
select * from insert_9;
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HIVE-8544) Beeline SeparatedValuesOutputFormat (csv/tsv/dsv) wraps the results with extra double quotes
Vaibhav Gumashta created HIVE-8544:
--
Summary: Beeline SeparatedValuesOutputFormat (csv/tsv/dsv) wraps
the results with extra double quotes
Key: HIVE-8544
URL: https://issues.apache.org/jira/browse/HIVE-8544
Project: Hive
Issue Type: Bug
Components: CLI, JDBC
Affects Versions: 0.14.0
Reporter: Vaibhav Gumashta
Assignee: Vaibhav Gumashta
Noticed additional double quotes in select * complex datatypes output while
running it through HiveServer2/Beeline
Actual
{noformat}
[18,19] {col1:alice brown,col2:18}{alice brown:18}
[18,19] {col1:alice garcia,col2:18} {alice garcia:18}
[18,19] {col1:alice garcia,col2:18} {alice garcia:18}
[18,19] {col1:alice thompson,col2:18} {alice
thompson:18}
[18,19] {col1:alice xylophone,col2:18}{alice
xylophone:18}
[18,19] {col1:bob hernandez,col2:18} {bob hernandez:18}
[18,19] {col1:bob ichabod,col2:18}{bob ichabod:18}
{noformat}
Expected
{noformat}
[18,19] {col1:alice brown,col2:18}{alice brown:18}
[18,19] {col1:alice garcia,col2:18} {alice garcia:18}
[18,19] {col1:alice garcia,col2:18} {alice garcia:18}
[18,19] {col1:alice thompson,col2:18} {alice thompson:18}
[18,19] {col1:alice xylophone,col2:18}{alice xylophone:18}
[18,19] {col1:bob hernandez,col2:18} {bob hernandez:18}
[18,19] {col1:bob ichabod,col2:18}{bob ichabod:18}
{noformat}
Run these queries through HiveServer2 to reproduce the issue:
{noformat}
create table insert_9 (a arrayint, b structcol1:string,col2:int, c
mapstring, int);
insert overwrite table insert_9 select array(age, age+1), struct(name, age),
map(name, age) from studenttab10k;
select * from insert_9;
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HIVE-8544) Beeline SeparatedValuesOutputFormat (csv/tsv/dsv) wraps the results with extra double quotes
[
https://issues.apache.org/jira/browse/HIVE-8544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14179011#comment-14179011
]
Vaibhav Gumashta commented on HIVE-8544:
[~vikram.dixit] This might cause some issues with code written by some clients.
Possible to have it in 14?
Beeline SeparatedValuesOutputFormat (csv/tsv/dsv) wraps the results with
extra double quotes
--
Key: HIVE-8544
URL: https://issues.apache.org/jira/browse/HIVE-8544
Project: Hive
Issue Type: Bug
Components: CLI, JDBC
Affects Versions: 0.14.0
Reporter: Vaibhav Gumashta
Assignee: Vaibhav Gumashta
Noticed additional double quotes in select * complex datatypes output
while running it through HiveServer2/Beeline
Actual
{noformat}
[18,19] {col1:alice brown,col2:18}{alice
brown:18}
[18,19] {col1:alice garcia,col2:18} {alice
garcia:18}
[18,19] {col1:alice garcia,col2:18} {alice
garcia:18}
[18,19] {col1:alice thompson,col2:18} {alice
thompson:18}
[18,19] {col1:alice xylophone,col2:18}{alice
xylophone:18}
[18,19] {col1:bob hernandez,col2:18} {bob
hernandez:18}
[18,19] {col1:bob ichabod,col2:18}{bob
ichabod:18}
{noformat}
Expected
{noformat}
[18,19] {col1:alice brown,col2:18}{alice brown:18}
[18,19] {col1:alice garcia,col2:18} {alice garcia:18}
[18,19] {col1:alice garcia,col2:18} {alice garcia:18}
[18,19] {col1:alice thompson,col2:18} {alice thompson:18}
[18,19] {col1:alice xylophone,col2:18}{alice xylophone:18}
[18,19] {col1:bob hernandez,col2:18} {bob hernandez:18}
[18,19] {col1:bob ichabod,col2:18}{bob ichabod:18}
{noformat}
Run these queries through HiveServer2 to reproduce the issue:
{noformat}
create table insert_9 (a arrayint, b structcol1:string,col2:int, c
mapstring, int);
insert overwrite table insert_9 select array(age, age+1), struct(name, age),
map(name, age) from studenttab10k;
select * from insert_9;
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HIVE-7390) Make quote character optional and configurable in BeeLine CSV/TSV output
[ https://issues.apache.org/jira/browse/HIVE-7390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14179089#comment-14179089 ] Vaibhav Gumashta commented on HIVE-7390: This seems like a backward incompatible change as it breaks old client behavior. I've created HIVE-8544 for addressing the issue. Make quote character optional and configurable in BeeLine CSV/TSV output Key: HIVE-7390 URL: https://issues.apache.org/jira/browse/HIVE-7390 Project: Hive Issue Type: New Feature Components: Clients Affects Versions: 0.13.1 Reporter: Jim Halfpenny Assignee: Ferdinand Xu Labels: TODOC14 Fix For: 0.14.0 Attachments: HIVE-7390.1.patch, HIVE-7390.2.patch, HIVE-7390.3.patch, HIVE-7390.4.patch, HIVE-7390.5.patch, HIVE-7390.6.patch, HIVE-7390.7.patch, HIVE-7390.8.patch, HIVE-7390.9.patch, HIVE-7390.patch Currently when either the CSV or TSV output formats are used in beeline each column is wrapped in single quotes. Quote wrapping of columns should be optional and the user should be able to choose the character used to wrap the columns. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-8173) HiveServer2 dynamic service discovery: figure out best ZooKeeper ACLs for security
[ https://issues.apache.org/jira/browse/HIVE-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-8173: --- Resolution: Fixed Status: Resolved (was: Patch Available) Patch committed to trunk and 14. Thanks for reviewing [~thejas]! HiveServer2 dynamic service discovery: figure out best ZooKeeper ACLs for security -- Key: HIVE-8173 URL: https://issues.apache.org/jira/browse/HIVE-8173 Project: Hive Issue Type: Sub-task Components: HiveServer2, JDBC Affects Versions: 0.14.0 Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Priority: Critical Labels: TODOC14 Fix For: 0.14.0 Attachments: HIVE-8173.1.patch, HIVE-8173.2.patch, HIVE-8173.3.patch Currently while creating a znode for the ZooKeeper namespace and for server instances, the create mode is: OPEN_ACL_UNSAFE - meaning anyone can read-write. Need to figure out how a more restrictive model can be used: ideally the creator should be read/write/delete and others should be read only -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-8377) Enable Kerberized SSL for HiveServer2 in http mode
[ https://issues.apache.org/jira/browse/HIVE-8377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-8377: --- Resolution: Fixed Status: Resolved (was: Patch Available) Patch committed to trunk 14. Thanks for reviewing [~thejas]. Enable Kerberized SSL for HiveServer2 in http mode -- Key: HIVE-8377 URL: https://issues.apache.org/jira/browse/HIVE-8377 Project: Hive Issue Type: Sub-task Components: HiveServer2 Affects Versions: 0.14.0 Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Priority: Critical Labels: TODOC14 Fix For: 0.14.0 Attachments: HIVE-8377.1.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-8529) HiveSessionImpl#fetchResults should not try to fetch operation log when hive.server2.logging.operation.enabled is false.
[
https://issues.apache.org/jira/browse/HIVE-8529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vaibhav Gumashta updated HIVE-8529:
---
Component/s: JDBC
HiveServer2
HiveSessionImpl#fetchResults should not try to fetch operation log when
hive.server2.logging.operation.enabled is false.
Key: HIVE-8529
URL: https://issues.apache.org/jira/browse/HIVE-8529
Project: Hive
Issue Type: Bug
Components: HiveServer2, JDBC
Reporter: Vaibhav Gumashta
Assignee: Vaibhav Gumashta
Fix For: 0.15.0
Throws this even when it is disabled:
{code}
14/10/20 15:53:14 [HiveServer2-Handler-Pool: Thread-53]: DEBUG
security.UserGroupInformation: PrivilegedActionException as:vgumashta
(auth:SIMPLE) cause:org.apache.hive.service.cli.HiveSQLException: Couldn't
find log associated with operation handle: OperationHandle
[opType=EXECUTE_STATEMENT,
getHandleIdentifier()=b3d05ca6-e3e8-4bef-b869-0ea0732c3ac5]
14/10/20 15:53:14 [HiveServer2-Handler-Pool: Thread-53]: WARN
thrift.ThriftCLIService: Error fetching results:
org.apache.hive.service.cli.HiveSQLException: Couldn't find log associated
with operation handle: OperationHandle [opType=EXECUTE_STATEMENT,
getHandleIdentifier()=b3d05ca6-e3e8-4bef-b869-0ea0732c3ac5]
at
org.apache.hive.service.cli.operation.OperationManager.getOperationLogRowSet(OperationManager.java:240)
at
org.apache.hive.service.cli.session.HiveSessionImpl.fetchResults(HiveSessionImpl.java:665)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.hive.service.cli.session.HiveSessionProxy.invoke(HiveSessionProxy.java:79)
at
org.apache.hive.service.cli.session.HiveSessionProxy.access$000(HiveSessionProxy.java:37)
at
org.apache.hive.service.cli.session.HiveSessionProxy$1.run(HiveSessionProxy.java:64)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:394)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1548)
at
org.apache.hadoop.hive.shims.HadoopShimsSecure.doAs(HadoopShimsSecure.java:508)
at
org.apache.hive.service.cli.session.HiveSessionProxy.invoke(HiveSessionProxy.java:60)
at com.sun.proxy.$Proxy20.fetchResults(Unknown Source)
at
org.apache.hive.service.cli.CLIService.fetchResults(CLIService.java:427)
at
org.apache.hive.service.cli.thrift.ThriftCLIService.FetchResults(ThriftCLIService.java:582)
at
org.apache.hive.service.cli.thrift.TCLIService$Processor$FetchResults.getResult(TCLIService.java:1553)
at
org.apache.hive.service.cli.thrift.TCLIService$Processor$FetchResults.getResult(TCLIService.java:1538)
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
at
org.apache.hive.service.auth.TSetIpAddressProcessor.process(TSetIpAddressProcessor.java:56)
at
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:206)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:695)
14/10/20 15:53:14 [HiveServer2-Handler-Pool: Thread-53]: DEBUG
transport.TSaslTransport: writing data length: 2525
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HIVE-8529) HiveSessionImpl#fetchResults should not try to fetch operation log when hive.server2.logging.operation.enabled is false.
Vaibhav Gumashta created HIVE-8529:
--
Summary: HiveSessionImpl#fetchResults should not try to fetch
operation log when hive.server2.logging.operation.enabled is false.
Key: HIVE-8529
URL: https://issues.apache.org/jira/browse/HIVE-8529
Project: Hive
Issue Type: Bug
Reporter: Vaibhav Gumashta
Assignee: Vaibhav Gumashta
Throws this even when it is disabled:
{code}
14/10/20 15:53:14 [HiveServer2-Handler-Pool: Thread-53]: DEBUG
security.UserGroupInformation: PrivilegedActionException as:vgumashta
(auth:SIMPLE) cause:org.apache.hive.service.cli.HiveSQLException: Couldn't find
log associated with operation handle: OperationHandle
[opType=EXECUTE_STATEMENT,
getHandleIdentifier()=b3d05ca6-e3e8-4bef-b869-0ea0732c3ac5]
14/10/20 15:53:14 [HiveServer2-Handler-Pool: Thread-53]: WARN
thrift.ThriftCLIService: Error fetching results:
org.apache.hive.service.cli.HiveSQLException: Couldn't find log associated with
operation handle: OperationHandle [opType=EXECUTE_STATEMENT,
getHandleIdentifier()=b3d05ca6-e3e8-4bef-b869-0ea0732c3ac5]
at
org.apache.hive.service.cli.operation.OperationManager.getOperationLogRowSet(OperationManager.java:240)
at
org.apache.hive.service.cli.session.HiveSessionImpl.fetchResults(HiveSessionImpl.java:665)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.hive.service.cli.session.HiveSessionProxy.invoke(HiveSessionProxy.java:79)
at
org.apache.hive.service.cli.session.HiveSessionProxy.access$000(HiveSessionProxy.java:37)
at
org.apache.hive.service.cli.session.HiveSessionProxy$1.run(HiveSessionProxy.java:64)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:394)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1548)
at
org.apache.hadoop.hive.shims.HadoopShimsSecure.doAs(HadoopShimsSecure.java:508)
at
org.apache.hive.service.cli.session.HiveSessionProxy.invoke(HiveSessionProxy.java:60)
at com.sun.proxy.$Proxy20.fetchResults(Unknown Source)
at
org.apache.hive.service.cli.CLIService.fetchResults(CLIService.java:427)
at
org.apache.hive.service.cli.thrift.ThriftCLIService.FetchResults(ThriftCLIService.java:582)
at
org.apache.hive.service.cli.thrift.TCLIService$Processor$FetchResults.getResult(TCLIService.java:1553)
at
org.apache.hive.service.cli.thrift.TCLIService$Processor$FetchResults.getResult(TCLIService.java:1538)
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
at
org.apache.hive.service.auth.TSetIpAddressProcessor.process(TSetIpAddressProcessor.java:56)
at
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:206)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:695)
14/10/20 15:53:14 [HiveServer2-Handler-Pool: Thread-53]: DEBUG
transport.TSaslTransport: writing data length: 2525
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HIVE-8529) HiveSessionImpl#fetchResults should not try to fetch operation log when hive.server2.logging.operation.enabled is false.
[
https://issues.apache.org/jira/browse/HIVE-8529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vaibhav Gumashta updated HIVE-8529:
---
Fix Version/s: 0.15.0
HiveSessionImpl#fetchResults should not try to fetch operation log when
hive.server2.logging.operation.enabled is false.
Key: HIVE-8529
URL: https://issues.apache.org/jira/browse/HIVE-8529
Project: Hive
Issue Type: Bug
Components: HiveServer2, JDBC
Reporter: Vaibhav Gumashta
Assignee: Vaibhav Gumashta
Fix For: 0.15.0
Throws this even when it is disabled:
{code}
14/10/20 15:53:14 [HiveServer2-Handler-Pool: Thread-53]: DEBUG
security.UserGroupInformation: PrivilegedActionException as:vgumashta
(auth:SIMPLE) cause:org.apache.hive.service.cli.HiveSQLException: Couldn't
find log associated with operation handle: OperationHandle
[opType=EXECUTE_STATEMENT,
getHandleIdentifier()=b3d05ca6-e3e8-4bef-b869-0ea0732c3ac5]
14/10/20 15:53:14 [HiveServer2-Handler-Pool: Thread-53]: WARN
thrift.ThriftCLIService: Error fetching results:
org.apache.hive.service.cli.HiveSQLException: Couldn't find log associated
with operation handle: OperationHandle [opType=EXECUTE_STATEMENT,
getHandleIdentifier()=b3d05ca6-e3e8-4bef-b869-0ea0732c3ac5]
at
org.apache.hive.service.cli.operation.OperationManager.getOperationLogRowSet(OperationManager.java:240)
at
org.apache.hive.service.cli.session.HiveSessionImpl.fetchResults(HiveSessionImpl.java:665)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.hive.service.cli.session.HiveSessionProxy.invoke(HiveSessionProxy.java:79)
at
org.apache.hive.service.cli.session.HiveSessionProxy.access$000(HiveSessionProxy.java:37)
at
org.apache.hive.service.cli.session.HiveSessionProxy$1.run(HiveSessionProxy.java:64)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:394)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1548)
at
org.apache.hadoop.hive.shims.HadoopShimsSecure.doAs(HadoopShimsSecure.java:508)
at
org.apache.hive.service.cli.session.HiveSessionProxy.invoke(HiveSessionProxy.java:60)
at com.sun.proxy.$Proxy20.fetchResults(Unknown Source)
at
org.apache.hive.service.cli.CLIService.fetchResults(CLIService.java:427)
at
org.apache.hive.service.cli.thrift.ThriftCLIService.FetchResults(ThriftCLIService.java:582)
at
org.apache.hive.service.cli.thrift.TCLIService$Processor$FetchResults.getResult(TCLIService.java:1553)
at
org.apache.hive.service.cli.thrift.TCLIService$Processor$FetchResults.getResult(TCLIService.java:1538)
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
at
org.apache.hive.service.auth.TSetIpAddressProcessor.process(TSetIpAddressProcessor.java:56)
at
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:206)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:695)
14/10/20 15:53:14 [HiveServer2-Handler-Pool: Thread-53]: DEBUG
transport.TSaslTransport: writing data length: 2525
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HIVE-8529) HiveSessionImpl#fetchResults should not try to fetch operation log when hive.server2.logging.operation.enabled is false.
[
https://issues.apache.org/jira/browse/HIVE-8529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vaibhav Gumashta updated HIVE-8529:
---
Assignee: (was: Vaibhav Gumashta)
HiveSessionImpl#fetchResults should not try to fetch operation log when
hive.server2.logging.operation.enabled is false.
Key: HIVE-8529
URL: https://issues.apache.org/jira/browse/HIVE-8529
Project: Hive
Issue Type: Bug
Components: HiveServer2, JDBC
Reporter: Vaibhav Gumashta
Fix For: 0.15.0
Throws this even when it is disabled:
{code}
14/10/20 15:53:14 [HiveServer2-Handler-Pool: Thread-53]: DEBUG
security.UserGroupInformation: PrivilegedActionException as:vgumashta
(auth:SIMPLE) cause:org.apache.hive.service.cli.HiveSQLException: Couldn't
find log associated with operation handle: OperationHandle
[opType=EXECUTE_STATEMENT,
getHandleIdentifier()=b3d05ca6-e3e8-4bef-b869-0ea0732c3ac5]
14/10/20 15:53:14 [HiveServer2-Handler-Pool: Thread-53]: WARN
thrift.ThriftCLIService: Error fetching results:
org.apache.hive.service.cli.HiveSQLException: Couldn't find log associated
with operation handle: OperationHandle [opType=EXECUTE_STATEMENT,
getHandleIdentifier()=b3d05ca6-e3e8-4bef-b869-0ea0732c3ac5]
at
org.apache.hive.service.cli.operation.OperationManager.getOperationLogRowSet(OperationManager.java:240)
at
org.apache.hive.service.cli.session.HiveSessionImpl.fetchResults(HiveSessionImpl.java:665)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.hive.service.cli.session.HiveSessionProxy.invoke(HiveSessionProxy.java:79)
at
org.apache.hive.service.cli.session.HiveSessionProxy.access$000(HiveSessionProxy.java:37)
at
org.apache.hive.service.cli.session.HiveSessionProxy$1.run(HiveSessionProxy.java:64)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:394)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1548)
at
org.apache.hadoop.hive.shims.HadoopShimsSecure.doAs(HadoopShimsSecure.java:508)
at
org.apache.hive.service.cli.session.HiveSessionProxy.invoke(HiveSessionProxy.java:60)
at com.sun.proxy.$Proxy20.fetchResults(Unknown Source)
at
org.apache.hive.service.cli.CLIService.fetchResults(CLIService.java:427)
at
org.apache.hive.service.cli.thrift.ThriftCLIService.FetchResults(ThriftCLIService.java:582)
at
org.apache.hive.service.cli.thrift.TCLIService$Processor$FetchResults.getResult(TCLIService.java:1553)
at
org.apache.hive.service.cli.thrift.TCLIService$Processor$FetchResults.getResult(TCLIService.java:1538)
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
at
org.apache.hive.service.auth.TSetIpAddressProcessor.process(TSetIpAddressProcessor.java:56)
at
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:206)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:695)
14/10/20 15:53:14 [HiveServer2-Handler-Pool: Thread-53]: DEBUG
transport.TSaslTransport: writing data length: 2525
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Review Request 26844: HiveServer2 dynamic service discovery: figure out best ZooKeeper ACLs for security
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26844/ --- (Updated Oct. 17, 2014, 10:43 a.m.) Review request for hive, dilli dorai, Eugene Koifman, and Thejas Nair. Bugs: HIVE-8173 https://issues.apache.org/jira/browse/HIVE-8173 Repository: hive-git Description --- https://issues.apache.org/jira/browse/HIVE-8173 Diffs (updated) - jdbc/src/java/org/apache/hive/jdbc/Utils.java 9b08fd9 ql/src/java/org/apache/hadoop/hive/ql/util/ZooKeeperHiveHelper.java d9faa45 service/src/java/org/apache/hive/service/server/HiveServer2.java 8691fcc shims/0.20/src/main/java/org/apache/hadoop/hive/shims/Hadoop20Shims.java 3c7d2af shims/common-secure/src/main/java/org/apache/hadoop/hive/shims/HadoopShimsSecure.java 6e1ad03 shims/common/src/main/java/org/apache/hadoop/hive/shims/HadoopShims.java 99a2bcf Diff: https://reviews.apache.org/r/26844/diff/ Testing --- Thanks, Vaibhav Gumashta
[jira] [Updated] (HIVE-8173) HiveServer2 dynamic service discovery: figure out best ZooKeeper ACLs for security
[ https://issues.apache.org/jira/browse/HIVE-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-8173: --- Attachment: HIVE-8173.2.patch HiveServer2 dynamic service discovery: figure out best ZooKeeper ACLs for security -- Key: HIVE-8173 URL: https://issues.apache.org/jira/browse/HIVE-8173 Project: Hive Issue Type: Sub-task Components: HiveServer2, JDBC Affects Versions: 0.14.0 Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Priority: Critical Labels: TODOC14 Fix For: 0.14.0 Attachments: HIVE-8173.1.patch, HIVE-8173.2.patch Currently while creating a znode for the ZooKeeper namespace and for server instances, the create mode is: OPEN_ACL_UNSAFE - meaning anyone can read-write. Need to figure out how a more restrictive model can be used: ideally the creator should be read/write/delete and others should be read only -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HIVE-8173) HiveServer2 dynamic service discovery: figure out best ZooKeeper ACLs for security
[ https://issues.apache.org/jira/browse/HIVE-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14175326#comment-14175326 ] Vaibhav Gumashta commented on HIVE-8173: [~thejas] Test failures are unrelated. HiveServer2 dynamic service discovery: figure out best ZooKeeper ACLs for security -- Key: HIVE-8173 URL: https://issues.apache.org/jira/browse/HIVE-8173 Project: Hive Issue Type: Sub-task Components: HiveServer2, JDBC Affects Versions: 0.14.0 Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Priority: Critical Labels: TODOC14 Fix For: 0.14.0 Attachments: HIVE-8173.1.patch, HIVE-8173.2.patch Currently while creating a znode for the ZooKeeper namespace and for server instances, the create mode is: OPEN_ACL_UNSAFE - meaning anyone can read-write. Need to figure out how a more restrictive model can be used: ideally the creator should be read/write/delete and others should be read only -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 26844: HiveServer2 dynamic service discovery: figure out best ZooKeeper ACLs for security
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26844/ --- (Updated Oct. 17, 2014, 9:04 p.m.) Review request for hive, dilli dorai, Eugene Koifman, and Thejas Nair. Bugs: HIVE-8173 https://issues.apache.org/jira/browse/HIVE-8173 Repository: hive-git Description --- https://issues.apache.org/jira/browse/HIVE-8173 Diffs (updated) - jdbc/src/java/org/apache/hive/jdbc/Utils.java 9b08fd9 ql/src/java/org/apache/hadoop/hive/ql/util/ZooKeeperHiveHelper.java d9faa45 service/src/java/org/apache/hive/service/server/HiveServer2.java 8691fcc shims/0.20/src/main/java/org/apache/hadoop/hive/shims/Hadoop20Shims.java 3c7d2af shims/common-secure/src/main/java/org/apache/hadoop/hive/shims/HadoopShimsSecure.java 6e1ad03 shims/common/src/main/java/org/apache/hadoop/hive/shims/HadoopShims.java 99a2bcf Diff: https://reviews.apache.org/r/26844/diff/ Testing --- Thanks, Vaibhav Gumashta
[jira] [Updated] (HIVE-8173) HiveServer2 dynamic service discovery: figure out best ZooKeeper ACLs for security
[ https://issues.apache.org/jira/browse/HIVE-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-8173: --- Attachment: HIVE-8173.3.patch HiveServer2 dynamic service discovery: figure out best ZooKeeper ACLs for security -- Key: HIVE-8173 URL: https://issues.apache.org/jira/browse/HIVE-8173 Project: Hive Issue Type: Sub-task Components: HiveServer2, JDBC Affects Versions: 0.14.0 Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Priority: Critical Labels: TODOC14 Fix For: 0.14.0 Attachments: HIVE-8173.1.patch, HIVE-8173.2.patch, HIVE-8173.3.patch Currently while creating a znode for the ZooKeeper namespace and for server instances, the create mode is: OPEN_ACL_UNSAFE - meaning anyone can read-write. Need to figure out how a more restrictive model can be used: ideally the creator should be read/write/delete and others should be read only -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-8377) Enable Kerberized SSL for HiveServer2 in http mode
[ https://issues.apache.org/jira/browse/HIVE-8377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-8377: --- Attachment: HIVE-8377.1.patch Enable Kerberized SSL for HiveServer2 in http mode -- Key: HIVE-8377 URL: https://issues.apache.org/jira/browse/HIVE-8377 Project: Hive Issue Type: Sub-task Components: HiveServer2 Affects Versions: 0.14.0 Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Fix For: 0.14.0 Attachments: HIVE-8377.1.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Review Request 26893: Enable Kerberized SSL for HiveServer2 in http mode
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26893/ --- Review request for hive and Thejas Nair. Bugs: HIVE-8377 https://issues.apache.org/jira/browse/HIVE-8377 Repository: hive-git Description --- https://issues.apache.org/jira/browse/HIVE-8377 Diffs - jdbc/src/java/org/apache/hive/jdbc/HiveConnection.java e4ec0c6 service/src/java/org/apache/hive/service/cli/thrift/ThriftHttpCLIService.java cfa7284 Diff: https://reviews.apache.org/r/26893/diff/ Testing --- Thanks, Vaibhav Gumashta
[jira] [Commented] (HIVE-8377) Enable Kerberized SSL for HiveServer2 in http mode
[ https://issues.apache.org/jira/browse/HIVE-8377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14175614#comment-14175614 ] Vaibhav Gumashta commented on HIVE-8377: cc [~thejas] Enable Kerberized SSL for HiveServer2 in http mode -- Key: HIVE-8377 URL: https://issues.apache.org/jira/browse/HIVE-8377 Project: Hive Issue Type: Sub-task Components: HiveServer2 Affects Versions: 0.14.0 Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Fix For: 0.14.0 Attachments: HIVE-8377.1.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-8377) Enable Kerberized SSL for HiveServer2 in http mode
[ https://issues.apache.org/jira/browse/HIVE-8377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-8377: --- Priority: Critical (was: Major) Enable Kerberized SSL for HiveServer2 in http mode -- Key: HIVE-8377 URL: https://issues.apache.org/jira/browse/HIVE-8377 Project: Hive Issue Type: Sub-task Components: HiveServer2 Affects Versions: 0.14.0 Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Priority: Critical Fix For: 0.14.0 Attachments: HIVE-8377.1.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-8377) Enable Kerberized SSL for HiveServer2 in http mode
[ https://issues.apache.org/jira/browse/HIVE-8377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-8377: --- Labels: TODOC14 (was: ) Enable Kerberized SSL for HiveServer2 in http mode -- Key: HIVE-8377 URL: https://issues.apache.org/jira/browse/HIVE-8377 Project: Hive Issue Type: Sub-task Components: HiveServer2 Affects Versions: 0.14.0 Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Priority: Critical Labels: TODOC14 Fix For: 0.14.0 Attachments: HIVE-8377.1.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-8377) Enable Kerberized SSL for HiveServer2 in http mode
[ https://issues.apache.org/jira/browse/HIVE-8377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-8377: --- Status: Patch Available (was: Open) Enable Kerberized SSL for HiveServer2 in http mode -- Key: HIVE-8377 URL: https://issues.apache.org/jira/browse/HIVE-8377 Project: Hive Issue Type: Sub-task Components: HiveServer2 Affects Versions: 0.14.0 Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Priority: Critical Labels: TODOC14 Fix For: 0.14.0 Attachments: HIVE-8377.1.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Review Request 26844: HiveServer2 dynamic service discovery: figure out best ZooKeeper ACLs for security
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26844/ --- Review request for hive and Thejas Nair. Bugs: HIVE-8173 https://issues.apache.org/jira/browse/HIVE-8173 Repository: hive-git Description --- https://issues.apache.org/jira/browse/HIVE-8173 Diffs - jdbc/src/java/org/apache/hive/jdbc/Utils.java 9b08fd9 ql/src/java/org/apache/hadoop/hive/ql/util/ZooKeeperHiveHelper.java d9faa45 service/src/java/org/apache/hive/service/server/HiveServer2.java 8691fcc shims/0.20/src/main/java/org/apache/hadoop/hive/shims/Hadoop20Shims.java 3c7d2af shims/common-secure/src/main/java/org/apache/hadoop/hive/shims/HadoopShimsSecure.java 6e1ad03 shims/common/src/main/java/org/apache/hadoop/hive/shims/HadoopShims.java 99a2bcf Diff: https://reviews.apache.org/r/26844/diff/ Testing --- Thanks, Vaibhav Gumashta
[jira] [Updated] (HIVE-8173) HiveServer2 dynamic service discovery: figure out best ZooKeeper ACLs for security
[ https://issues.apache.org/jira/browse/HIVE-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-8173: --- Attachment: HIVE-8173.1.patch HiveServer2 dynamic service discovery: figure out best ZooKeeper ACLs for security -- Key: HIVE-8173 URL: https://issues.apache.org/jira/browse/HIVE-8173 Project: Hive Issue Type: Sub-task Components: HiveServer2, JDBC Affects Versions: 0.14.0 Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Priority: Critical Labels: TODOC14 Fix For: 0.14.0 Attachments: HIVE-8173.1.patch Currently while creating a znode for the ZooKeeper namespace and for server instances, the create mode is: OPEN_ACL_UNSAFE - meaning anyone can read-write. Need to figure out how a more restrictive model can be used: ideally the creator should be read/write/delete and others should be read only -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-8173) HiveServer2 dynamic service discovery: figure out best ZooKeeper ACLs for security
[ https://issues.apache.org/jira/browse/HIVE-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-8173: --- Status: Patch Available (was: Open) HiveServer2 dynamic service discovery: figure out best ZooKeeper ACLs for security -- Key: HIVE-8173 URL: https://issues.apache.org/jira/browse/HIVE-8173 Project: Hive Issue Type: Sub-task Components: HiveServer2, JDBC Affects Versions: 0.14.0 Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Priority: Critical Labels: TODOC14 Fix For: 0.14.0 Attachments: HIVE-8173.1.patch Currently while creating a znode for the ZooKeeper namespace and for server instances, the create mode is: OPEN_ACL_UNSAFE - meaning anyone can read-write. Need to figure out how a more restrictive model can be used: ideally the creator should be read/write/delete and others should be read only -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 26844: HiveServer2 dynamic service discovery: figure out best ZooKeeper ACLs for security
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26844/ --- (Updated Oct. 16, 2014, 11:52 p.m.) Review request for hive, Eugene Koifman and Thejas Nair. Bugs: HIVE-8173 https://issues.apache.org/jira/browse/HIVE-8173 Repository: hive-git Description --- https://issues.apache.org/jira/browse/HIVE-8173 Diffs - jdbc/src/java/org/apache/hive/jdbc/Utils.java 9b08fd9 ql/src/java/org/apache/hadoop/hive/ql/util/ZooKeeperHiveHelper.java d9faa45 service/src/java/org/apache/hive/service/server/HiveServer2.java 8691fcc shims/0.20/src/main/java/org/apache/hadoop/hive/shims/Hadoop20Shims.java 3c7d2af shims/common-secure/src/main/java/org/apache/hadoop/hive/shims/HadoopShimsSecure.java 6e1ad03 shims/common/src/main/java/org/apache/hadoop/hive/shims/HadoopShims.java 99a2bcf Diff: https://reviews.apache.org/r/26844/diff/ Testing --- Thanks, Vaibhav Gumashta
[jira] [Commented] (HIVE-8173) HiveServer2 dynamic service discovery: figure out best ZooKeeper ACLs for security
[ https://issues.apache.org/jira/browse/HIVE-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14174490#comment-14174490 ] Vaibhav Gumashta commented on HIVE-8173: cc [~thejas] [~ekoifman] [~dillidorai] HiveServer2 dynamic service discovery: figure out best ZooKeeper ACLs for security -- Key: HIVE-8173 URL: https://issues.apache.org/jira/browse/HIVE-8173 Project: Hive Issue Type: Sub-task Components: HiveServer2, JDBC Affects Versions: 0.14.0 Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Priority: Critical Labels: TODOC14 Fix For: 0.14.0 Attachments: HIVE-8173.1.patch Currently while creating a znode for the ZooKeeper namespace and for server instances, the create mode is: OPEN_ACL_UNSAFE - meaning anyone can read-write. Need to figure out how a more restrictive model can be used: ideally the creator should be read/write/delete and others should be read only -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 26844: HiveServer2 dynamic service discovery: figure out best ZooKeeper ACLs for security
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26844/ --- (Updated Oct. 16, 2014, 11:54 p.m.) Review request for hive, dilli dorai, Eugene Koifman, and Thejas Nair. Bugs: HIVE-8173 https://issues.apache.org/jira/browse/HIVE-8173 Repository: hive-git Description --- https://issues.apache.org/jira/browse/HIVE-8173 Diffs - jdbc/src/java/org/apache/hive/jdbc/Utils.java 9b08fd9 ql/src/java/org/apache/hadoop/hive/ql/util/ZooKeeperHiveHelper.java d9faa45 service/src/java/org/apache/hive/service/server/HiveServer2.java 8691fcc shims/0.20/src/main/java/org/apache/hadoop/hive/shims/Hadoop20Shims.java 3c7d2af shims/common-secure/src/main/java/org/apache/hadoop/hive/shims/HadoopShimsSecure.java 6e1ad03 shims/common/src/main/java/org/apache/hadoop/hive/shims/HadoopShims.java 99a2bcf Diff: https://reviews.apache.org/r/26844/diff/ Testing --- Thanks, Vaibhav Gumashta
Re: Review Request 26844: HiveServer2 dynamic service discovery: figure out best ZooKeeper ACLs for security
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26844/#review57060 --- ql/src/java/org/apache/hadoop/hive/ql/util/ZooKeeperHiveHelper.java https://reviews.apache.org/r/26844/#comment97541 I'll turn the debug mode off. - Vaibhav Gumashta On Oct. 16, 2014, 11:54 p.m., Vaibhav Gumashta wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26844/ --- (Updated Oct. 16, 2014, 11:54 p.m.) Review request for hive, dilli dorai, Eugene Koifman, and Thejas Nair. Bugs: HIVE-8173 https://issues.apache.org/jira/browse/HIVE-8173 Repository: hive-git Description --- https://issues.apache.org/jira/browse/HIVE-8173 Diffs - jdbc/src/java/org/apache/hive/jdbc/Utils.java 9b08fd9 ql/src/java/org/apache/hadoop/hive/ql/util/ZooKeeperHiveHelper.java d9faa45 service/src/java/org/apache/hive/service/server/HiveServer2.java 8691fcc shims/0.20/src/main/java/org/apache/hadoop/hive/shims/Hadoop20Shims.java 3c7d2af shims/common-secure/src/main/java/org/apache/hadoop/hive/shims/HadoopShimsSecure.java 6e1ad03 shims/common/src/main/java/org/apache/hadoop/hive/shims/HadoopShims.java 99a2bcf Diff: https://reviews.apache.org/r/26844/diff/ Testing --- Thanks, Vaibhav Gumashta
[jira] [Commented] (HIVE-8445) TestColumnAccess, TestReadEntityDirect use same table names
[ https://issues.apache.org/jira/browse/HIVE-8445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14173381#comment-14173381 ] Vaibhav Gumashta commented on HIVE-8445: +1 TestColumnAccess, TestReadEntityDirect use same table names --- Key: HIVE-8445 URL: https://issues.apache.org/jira/browse/HIVE-8445 Project: Hive Issue Type: Bug Components: Tests Reporter: Jason Dere Assignee: Jason Dere Attachments: HIVE-8445.1.patch Running both test in the same run results in Table t1 already exists for one test or the other. Tables should be cleaned up after the test. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HIVE-8475) add test case for use of index from not-current database
[
https://issues.apache.org/jira/browse/HIVE-8475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14173380#comment-14173380
]
Vaibhav Gumashta commented on HIVE-8475:
+1
add test case for use of index from not-current database
Key: HIVE-8475
URL: https://issues.apache.org/jira/browse/HIVE-8475
Project: Hive
Issue Type: Bug
Components: Indexing
Reporter: Thejas M Nair
Assignee: Thejas M Nair
Attachments: HIVE-8475-0.13.1.patch, HIVE-8475.1.patch
In hive 0.13, the following sequence fails -
{code:sql}
create database index_test_db;
use index_test_db;
create table testtb (id int, name string);
create index id_index on table testtb (id) as 'COMPACT' WITH DEFERRED REBUILD
in table testdb_id_idx_tb;
use default;
select * from index_test_db.testtb where id2;
-- fails here with error Table not found testdb_id_idx_tb
{code}
HIVE-4064 fixed the problem. It will be useful to have a test case that
verifies the fix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HIVE-6972) jdbc HTTP configuration options should be part of sessionConf part of connection string
[
https://issues.apache.org/jira/browse/HIVE-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14169885#comment-14169885
]
Vaibhav Gumashta commented on HIVE-6972:
[~leftylev] Done. Thanks again!
jdbc HTTP configuration options should be part of sessionConf part of
connection string
---
Key: HIVE-6972
URL: https://issues.apache.org/jira/browse/HIVE-6972
Project: Hive
Issue Type: Bug
Components: HiveServer2, JDBC
Affects Versions: 0.13.0
Reporter: Thejas M Nair
Assignee: Vaibhav Gumashta
Labels: TODOC14
Fix For: 0.14.0
Attachments: HIVE-6972.1.patch, HIVE-6972.2.patch, HIVE-6972.3.patch,
HIVE-6972.4.patch
The http connection parameters are currently part of the HiveConf section of
the connection string. It should ideally be part of SessionConf section, as
that is where rest of the connection parameters are.
HTTP transport parameters are not part of the hiveconfiguration parameters
that need to be set.
ie
instead of
jdbc:hive2://host:port/db?hive.server2.transport.mode=http;hive.server2.thrift.http.path=http_endpoint
it should be -
jdbc:hive2://host:port/db;transportMode=http;httpPath=http_endpoint
*Release Note:*
The JDBC Uri for HiveServer2 has the form:
{code}
jdbc:hive2://host1:port1,host2:port2/dbName;sess_var_list?hive_conf_list#hive_var_list
{code}
Ideally, sess_var_list is supposed to be used to pass parameters that will be
used within the JDBC Driver. However, some of the http mode parameters were
being passed in the hive_conf_list which we've fixed now (in a backward
compatible way).
Additionally, JDBC Driver has a naming convention for the parameters in the
JDBC Uri which were not followed to the sasl.qop parameter. We've renamed it
in a backward compatible way.
Details:
*1. HTTP Mode params:*
*Old example uri:*
{code}
jdbc:hive2://host:port/dbName;user=username;password=password?hive.server2.transport.mode=http;hive.server2.thrift.http.path=httpEndpoint
{code}
*New example uri:*
{code}
jdbc:hive2://host:port/dbName;user=username;password=password;transportMode=http;httpPath=httpEndpoint?hive.server2.logging.operation.enabled=false
{code}
As you can see above, {{hive.server2.transport.mode}} has been renamed to
{{transportMode}}, {{hive.server2.thrift.http.path}} has been renamed to
{{httpPath}} and both have been moved from {{hive_conf_list}} to
{{sess_var_list}}.
*2. Sasl qop renaming:*
*Old example uri:*
{code}
jdbc:hive2://host:port/dbName;principal=hiveserver2KerberosPrincipal;sasl.qop=qopValue
{code}
*New example uri:*
{code}
jdbc:hive2://host:port/dbName;principal=hiveserver2KerberosPrincipal;saslQop=qopValue
{code}
As you can see {{sasl.qop}} has been renamed to {{saslQop}}.
Note: all changes are backward compatible and print a deprecation message
like the following:
{code}
0: jdbc:hive2://localhost:10001 !connect
jdbc:hive2://localhost:10001/;sasl.qop=auth?hive.server2.transport.mode=http;hive.server2.thrift.http.path=cliservice
username password org.apache.hive.jdbc.HiveDriver
Connecting to
jdbc:hive2://localhost:10007/;sasl.qop=auth?hive.server2.transport.mode=http;hive.server2.thrift.http.path=cliservice
14/10/07 16:22:24 INFO jdbc.Utils: Supplied authorities: localhost:10001
14/10/07 16:22:24 WARN jdbc.Utils: * JDBC param deprecation *
14/10/07 16:22:24 WARN jdbc.Utils: The use of sasl.qop is deprecated.
14/10/07 16:22:24 WARN jdbc.Utils: Please use saslQop like so:
jdbc:hive2://host:port/dbName;saslQop=qop_value
14/10/07 16:22:24 WARN jdbc.Utils: * JDBC param deprecation *
14/10/07 16:22:24 WARN jdbc.Utils: The use of hive.server2.transport.mode is
deprecated.
14/10/07 16:22:24 WARN jdbc.Utils: Please use transportMode like so:
jdbc:hive2://host:port/dbName;transportMode=transport_mode_value
14/10/07 16:22:24 WARN jdbc.Utils: * JDBC param deprecation *
14/10/07 16:22:24 WARN jdbc.Utils: The use of hive.server2.thrift.http.path
is deprecated.
14/10/07 16:22:24 WARN jdbc.Utils: Please use httpPath like so:
jdbc:hive2://host:port/dbName;httpPath=http_path_value
Connected to: Apache Hive (version 0.14.0-SNAPSHOT)
Driver: Hive JDBC (version 0.14.0-SNAPSHOT)
Transaction isolation: TRANSACTION_REPEATABLE_READ
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HIVE-6972) jdbc HTTP configuration options should be part of sessionConf part of connection string
[
https://issues.apache.org/jira/browse/HIVE-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vaibhav Gumashta updated HIVE-6972:
---
Release Note: Check jira description.
jdbc HTTP configuration options should be part of sessionConf part of
connection string
---
Key: HIVE-6972
URL: https://issues.apache.org/jira/browse/HIVE-6972
Project: Hive
Issue Type: Bug
Components: HiveServer2, JDBC
Affects Versions: 0.13.0
Reporter: Thejas M Nair
Assignee: Vaibhav Gumashta
Labels: TODOC14
Fix For: 0.14.0
Attachments: HIVE-6972.1.patch, HIVE-6972.2.patch, HIVE-6972.3.patch,
HIVE-6972.4.patch
The http connection parameters are currently part of the HiveConf section of
the connection string. It should ideally be part of SessionConf section, as
that is where rest of the connection parameters are.
HTTP transport parameters are not part of the hiveconfiguration parameters
that need to be set.
ie
instead of
jdbc:hive2://host:port/db?hive.server2.transport.mode=http;hive.server2.thrift.http.path=http_endpoint
it should be -
jdbc:hive2://host:port/db;transportMode=http;httpPath=http_endpoint
*Release Note:*
The JDBC Uri for HiveServer2 has the form:
{code}
jdbc:hive2://host1:port1,host2:port2/dbName;sess_var_list?hive_conf_list#hive_var_list
{code}
Ideally, sess_var_list is supposed to be used to pass parameters that will be
used within the JDBC Driver. However, some of the http mode parameters were
being passed in the hive_conf_list which we've fixed now (in a backward
compatible way).
Additionally, JDBC Driver has a naming convention for the parameters in the
JDBC Uri which were not followed to the sasl.qop parameter. We've renamed it
in a backward compatible way.
Details:
*1. HTTP Mode params:*
*Old example uri:*
{code}
jdbc:hive2://host:port/dbName;user=username;password=password?hive.server2.transport.mode=http;hive.server2.thrift.http.path=httpEndpoint
{code}
*New example uri:*
{code}
jdbc:hive2://host:port/dbName;user=username;password=password;transportMode=http;httpPath=httpEndpoint?hive.server2.logging.operation.enabled=false
{code}
As you can see above, {{hive.server2.transport.mode}} has been renamed to
{{transportMode}}, {{hive.server2.thrift.http.path}} has been renamed to
{{httpPath}} and both have been moved from {{hive_conf_list}} to
{{sess_var_list}}.
*2. Sasl qop renaming:*
*Old example uri:*
{code}
jdbc:hive2://host:port/dbName;principal=hiveserver2KerberosPrincipal;sasl.qop=qopValue
{code}
*New example uri:*
{code}
jdbc:hive2://host:port/dbName;principal=hiveserver2KerberosPrincipal;saslQop=qopValue
{code}
As you can see {{sasl.qop}} has been renamed to {{saslQop}}.
Note: all changes are backward compatible and print a deprecation message
like the following:
{code}
0: jdbc:hive2://localhost:10001 !connect
jdbc:hive2://localhost:10001/;sasl.qop=auth?hive.server2.transport.mode=http;hive.server2.thrift.http.path=cliservice
username password org.apache.hive.jdbc.HiveDriver
Connecting to
jdbc:hive2://localhost:10007/;sasl.qop=auth?hive.server2.transport.mode=http;hive.server2.thrift.http.path=cliservice
14/10/07 16:22:24 INFO jdbc.Utils: Supplied authorities: localhost:10001
14/10/07 16:22:24 WARN jdbc.Utils: * JDBC param deprecation *
14/10/07 16:22:24 WARN jdbc.Utils: The use of sasl.qop is deprecated.
14/10/07 16:22:24 WARN jdbc.Utils: Please use saslQop like so:
jdbc:hive2://host:port/dbName;saslQop=qop_value
14/10/07 16:22:24 WARN jdbc.Utils: * JDBC param deprecation *
14/10/07 16:22:24 WARN jdbc.Utils: The use of hive.server2.transport.mode is
deprecated.
14/10/07 16:22:24 WARN jdbc.Utils: Please use transportMode like so:
jdbc:hive2://host:port/dbName;transportMode=transport_mode_value
14/10/07 16:22:24 WARN jdbc.Utils: * JDBC param deprecation *
14/10/07 16:22:24 WARN jdbc.Utils: The use of hive.server2.thrift.http.path
is deprecated.
14/10/07 16:22:24 WARN jdbc.Utils: Please use httpPath like so:
jdbc:hive2://host:port/dbName;httpPath=http_path_value
Connected to: Apache Hive (version 0.14.0-SNAPSHOT)
Driver: Hive JDBC (version 0.14.0-SNAPSHOT)
Transaction isolation: TRANSACTION_REPEATABLE_READ
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HIVE-8427) Hive Streaming : secure streaming hangs leading to time outs.
[ https://issues.apache.org/jira/browse/HIVE-8427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170044#comment-14170044 ] Vaibhav Gumashta commented on HIVE-8427: +1 from my side. Hive Streaming : secure streaming hangs leading to time outs. -- Key: HIVE-8427 URL: https://issues.apache.org/jira/browse/HIVE-8427 Project: Hive Issue Type: Bug Components: HCatalog Affects Versions: 0.14.0 Reporter: Roshan Naik Assignee: Roshan Naik Labels: ACID, Streaming Fix For: 0.14.0 Attachments: HIVE-8427.patch Need to enable Thrift Sasl setting for secure mode communcation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-8427) Hive Streaming : secure streaming hangs leading to time outs.
[ https://issues.apache.org/jira/browse/HIVE-8427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-8427: --- Resolution: Fixed Status: Resolved (was: Patch Available) Patch committed to 14 and trunk. Thanks for the patch [~roshan_naik]! Hive Streaming : secure streaming hangs leading to time outs. -- Key: HIVE-8427 URL: https://issues.apache.org/jira/browse/HIVE-8427 Project: Hive Issue Type: Bug Components: HCatalog Affects Versions: 0.14.0 Reporter: Roshan Naik Assignee: Roshan Naik Labels: ACID, Streaming Fix For: 0.14.0 Attachments: HIVE-8427.patch Need to enable Thrift Sasl setting for secure mode communcation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-6972) jdbc HTTP configuration options should be part of sessionConf part of connection string
[
https://issues.apache.org/jira/browse/HIVE-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vaibhav Gumashta updated HIVE-6972:
---
Release Note:
The JDBC Uri for HiveServer2 has the form:
{code}
jdbc:hive2://host1:port1,host2:port2/dbName;sess_var_list?hive_conf_list#hive_var_list
{code}
Ideally, sess_var_list is supposed to be used to pass parameters that will be
used within the JDBC Driver. However, some of the http mode parameters were
being passed in the hive_conf_list which we've fixed now (in a backward
compatible way).
Additionally, JDBC Driver has a naming convention for the parameters in the
JDBC Uri which were not followed to the sasl.qop parameter. We've renamed it in
a backward compatible way.
Details:
*1. HTTP Mode params:*
*Old example uri:*
{code}
jdbc:hive2://host:port/db;user=username;password=password?hive.server2.transport.mode=http;hive.server2.thrift.http.path=http_endpoint
{code}
*New example uri:*
{code}
jdbc:hive2://host:port/db;user=username;password=password;transportMode=http;httpPath=http_endpoint?hive.server2.logging.operation.enabled=false
{code}
As you can see above, {{hive.server2.transport.mode}} has been renamed to
{{transportMode}}, {{hive.server2.thrift.http.path}} has been renamed to
{{httpPath}} and both have been moved from {{hive_conf_list}} to
{{sess_var_list}}.
*2. Sasl qop renaming:*
*Old example uri:*
{code}
jdbc:hive2://host:port/db;principal=hiveserver2_kerberos_principal;sasl.qop=qop_value
{code}
*New example uri:*
{code}
jdbc:hive2://host:port/db;principal=hiveserver2_kerberos_principal;saslQop=qop_value
{code}
As you can see {{sasl.qop}} has been renamed to {{saslQop}}.
Note: all changes are backward compatible and print a deprecation message like
the following:
{code}
0: jdbc:hive2://localhost:10001 !connect
jdbc:hive2://localhost:10001/;sasl.qop=auth?hive.server2.transport.mode=http;hive.server2.thrift.http.path=cliservice
username password org.apache.hive.jdbc.HiveDriver
Connecting to
jdbc:hive2://localhost:10007/;sasl.qop=auth?hive.server2.transport.mode=http;hive.server2.thrift.http.path=cliservice
14/10/07 16:22:24 INFO jdbc.Utils: Supplied authorities: localhost:10001
14/10/07 16:22:24 WARN jdbc.Utils: * JDBC param deprecation *
14/10/07 16:22:24 WARN jdbc.Utils: The use of sasl.qop is deprecated.
14/10/07 16:22:24 WARN jdbc.Utils: Please use saslQop like so:
jdbc:hive2://host:port/dbName;saslQop=qop_value
14/10/07 16:22:24 WARN jdbc.Utils: * JDBC param deprecation *
14/10/07 16:22:24 WARN jdbc.Utils: The use of hive.server2.transport.mode is
deprecated.
14/10/07 16:22:24 WARN jdbc.Utils: Please use transportMode like so:
jdbc:hive2://host:port/dbName;transportMode=transport_mode_value
14/10/07 16:22:24 WARN jdbc.Utils: * JDBC param deprecation *
14/10/07 16:22:24 WARN jdbc.Utils: The use of hive.server2.thrift.http.path is
deprecated.
14/10/07 16:22:24 WARN jdbc.Utils: Please use httpPath like so:
jdbc:hive2://host:port/dbName;httpPath=http_path_value
Connected to: Apache Hive (version 0.14.0-SNAPSHOT)
Driver: Hive JDBC (version 0.14.0-SNAPSHOT)
Transaction isolation: TRANSACTION_REPEATABLE_READ
{code}
jdbc HTTP configuration options should be part of sessionConf part of
connection string
---
Key: HIVE-6972
URL: https://issues.apache.org/jira/browse/HIVE-6972
Project: Hive
Issue Type: Bug
Components: HiveServer2, JDBC
Affects Versions: 0.13.0
Reporter: Thejas M Nair
Assignee: Vaibhav Gumashta
Fix For: 0.14.0
Attachments: HIVE-6972.1.patch, HIVE-6972.2.patch, HIVE-6972.3.patch,
HIVE-6972.4.patch
The http connection parameters are currently part of the HiveConf section of
the connection string. It should ideally be part of SessionConf section, as
that is where rest of the connection parameters are.
HTTP transport parameters are not part of the hiveconfiguration parameters
that need to be set.
ie
instead of
jdbc:hive2://host:port/db?hive.server2.transport.mode=http;hive.server2.thrift.http.path=http_endpoint
it should be -
jdbc:hive2://host:port/db;transportMode=http;httpPath=http_endpoint
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HIVE-6972) jdbc HTTP configuration options should be part of sessionConf part of connection string
[
https://issues.apache.org/jira/browse/HIVE-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vaibhav Gumashta updated HIVE-6972:
---
Release Note:
The JDBC Uri for HiveServer2 has the form:
{code}
jdbc:hive2://\host1\:\port1\,\host2\:\port2\/dbName;sess_var_list?hive_conf_list#hive_var_list
{code}
Ideally, sess_var_list is supposed to be used to pass parameters that will be
used within the JDBC Driver. However, some of the http mode parameters were
being passed in the hive_conf_list which we've fixed now (in a backward
compatible way).
Additionally, JDBC Driver has a naming convention for the parameters in the
JDBC Uri which were not followed to the sasl.qop parameter. We've renamed it in
a backward compatible way.
Details:
*1. HTTP Mode params:*
*Old example uri:*
{code}
jdbc:hive2://\host\:\port\/\db\;user=\username\;password=\password\?hive.server2.transport.mode=http;hive.server2.thrift.http.path=http_endpoint
{code}
*New example uri:*
{code}
jdbc:hive2://host:port/db;user=username;password=password;transportMode=http;httpPath=http_endpoint?hive.server2.logging.operation.enabled=false
{code}
As you can see above, {{hive.server2.transport.mode}} has been renamed to
{{transportMode}}, {{hive.server2.thrift.http.path}} has been renamed to
{{httpPath}} and both have been moved from {{hive_conf_list}} to
{{sess_var_list}}.
*2. Sasl qop renaming:*
*Old example uri:*
{code}
jdbc:hive2://host:port/db;principal=hiveserver2_kerberos_principal;sasl.qop=qop_value
{code}
*New example uri:*
{code}
jdbc:hive2://host:port/db;principal=hiveserver2_kerberos_principal;saslQop=qop_value
{code}
As you can see {{sasl.qop}} has been renamed to {{saslQop}}.
Note: all changes are backward compatible and print a deprecation message like
the following:
{code}
0: jdbc:hive2://localhost:10001 !connect
jdbc:hive2://localhost:10001/;sasl.qop=auth?hive.server2.transport.mode=http;hive.server2.thrift.http.path=cliservice
username password org.apache.hive.jdbc.HiveDriver
Connecting to
jdbc:hive2://localhost:10007/;sasl.qop=auth?hive.server2.transport.mode=http;hive.server2.thrift.http.path=cliservice
14/10/07 16:22:24 INFO jdbc.Utils: Supplied authorities: localhost:10001
14/10/07 16:22:24 WARN jdbc.Utils: * JDBC param deprecation *
14/10/07 16:22:24 WARN jdbc.Utils: The use of sasl.qop is deprecated.
14/10/07 16:22:24 WARN jdbc.Utils: Please use saslQop like so:
jdbc:hive2://host:port/dbName;saslQop=qop_value
14/10/07 16:22:24 WARN jdbc.Utils: * JDBC param deprecation *
14/10/07 16:22:24 WARN jdbc.Utils: The use of hive.server2.transport.mode is
deprecated.
14/10/07 16:22:24 WARN jdbc.Utils: Please use transportMode like so:
jdbc:hive2://host:port/dbName;transportMode=transport_mode_value
14/10/07 16:22:24 WARN jdbc.Utils: * JDBC param deprecation *
14/10/07 16:22:24 WARN jdbc.Utils: The use of hive.server2.thrift.http.path is
deprecated.
14/10/07 16:22:24 WARN jdbc.Utils: Please use httpPath like so:
jdbc:hive2://host:port/dbName;httpPath=http_path_value
Connected to: Apache Hive (version 0.14.0-SNAPSHOT)
Driver: Hive JDBC (version 0.14.0-SNAPSHOT)
Transaction isolation: TRANSACTION_REPEATABLE_READ
{code}
was:
The JDBC Uri for HiveServer2 has the form:
{code}
jdbc:hive2://host1:port1,host2:port2/dbName;sess_var_list?hive_conf_list#hive_var_list
{code}
Ideally, sess_var_list is supposed to be used to pass parameters that will be
used within the JDBC Driver. However, some of the http mode parameters were
being passed in the hive_conf_list which we've fixed now (in a backward
compatible way).
Additionally, JDBC Driver has a naming convention for the parameters in the
JDBC Uri which were not followed to the sasl.qop parameter. We've renamed it in
a backward compatible way.
Details:
*1. HTTP Mode params:*
*Old example uri:*
{code}
jdbc:hive2://host:port/db;user=username;password=password?hive.server2.transport.mode=http;hive.server2.thrift.http.path=http_endpoint
{code}
*New example uri:*
{code}
jdbc:hive2://host:port/db;user=username;password=password;transportMode=http;httpPath=http_endpoint?hive.server2.logging.operation.enabled=false
{code}
As you can see above, {{hive.server2.transport.mode}} has been renamed to
{{transportMode}}, {{hive.server2.thrift.http.path}} has been renamed to
{{httpPath}} and both have been moved from {{hive_conf_list}} to
{{sess_var_list}}.
*2. Sasl qop renaming:*
*Old example uri:*
{code}
jdbc:hive2://host:port/db;principal=hiveserver2_kerberos_principal;sasl.qop=qop_value
{code}
*New example uri:*
{code}
jdbc:hive2://host:port/db;principal=hiveserver2_kerberos_principal;saslQop=qop_value
{code}
As you can see {{sasl.qop}} has been renamed to {{saslQop}}.
Note: all changes are backward compatible and print a deprecation message like
the following:
{code}
0: jdbc:hive2://localhost:10001 !connect
jdbc:hive2://localhost:10001/;sasl.qop=auth?hive.server2.transport.mode
[jira] [Updated] (HIVE-6972) jdbc HTTP configuration options should be part of sessionConf part of connection string
[
https://issues.apache.org/jira/browse/HIVE-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vaibhav Gumashta updated HIVE-6972:
---
Release Note: (was: The JDBC Uri for HiveServer2 has the form:
{code}
jdbc:hive2://host1:port1,host2:port2/dbName;sess_var_list?hive_conf_list#hive_var_list
{code}
Ideally, sess_var_list is supposed to be used to pass parameters that will be
used within the JDBC Driver. However, some of the http mode parameters were
being passed in the hive_conf_list which we've fixed now (in a backward
compatible way).
Additionally, JDBC Driver has a naming convention for the parameters in the
JDBC Uri which were not followed to the sasl.qop parameter. We've renamed it in
a backward compatible way.
Details:
*1. HTTP Mode params:*
*Old example uri:*
{code}
jdbc:hive2://host:port/dbName;user=username;password=password?hive.server2.transport.mode=http;hive.server2.thrift.http.path=httpEndpoint
{code}
*New example uri:*
{code}
jdbc:hive2://host:port/dbName;user=username;password=password;transportMode=http;httpPath=httpEndpoint?hive.server2.logging.operation.enabled=false
{code}
As you can see above, {{hive.server2.transport.mode}} has been renamed to
{{transportMode}}, {{hive.server2.thrift.http.path}} has been renamed to
{{httpPath}} and both have been moved from {{hive_conf_list}} to
{{sess_var_list}}.
*2. Sasl qop renaming:*
*Old example uri:*
{code}
jdbc:hive2://host:port/dbName;principal=hiveserver2KerberosPrincipal;sasl.qop=qopValue
{code}
*New example uri:*
{code}
jdbc:hive2://host:port/dbName;principal=hiveserver2KerberosPrincipal;saslQop=qopValue
{code}
As you can see {{sasl.qop}} has been renamed to {{saslQop}}.
Note: all changes are backward compatible and print a deprecation message like
the following:
{code}
0: jdbc:hive2://localhost:10001 !connect
jdbc:hive2://localhost:10001/;sasl.qop=auth?hive.server2.transport.mode=http;hive.server2.thrift.http.path=cliservice
username password org.apache.hive.jdbc.HiveDriver
Connecting to
jdbc:hive2://localhost:10007/;sasl.qop=auth?hive.server2.transport.mode=http;hive.server2.thrift.http.path=cliservice
14/10/07 16:22:24 INFO jdbc.Utils: Supplied authorities: localhost:10001
14/10/07 16:22:24 WARN jdbc.Utils: * JDBC param deprecation *
14/10/07 16:22:24 WARN jdbc.Utils: The use of sasl.qop is deprecated.
14/10/07 16:22:24 WARN jdbc.Utils: Please use saslQop like so:
jdbc:hive2://host:port/dbName;saslQop=qop_value
14/10/07 16:22:24 WARN jdbc.Utils: * JDBC param deprecation *
14/10/07 16:22:24 WARN jdbc.Utils: The use of hive.server2.transport.mode is
deprecated.
14/10/07 16:22:24 WARN jdbc.Utils: Please use transportMode like so:
jdbc:hive2://host:port/dbName;transportMode=transport_mode_value
14/10/07 16:22:24 WARN jdbc.Utils: * JDBC param deprecation *
14/10/07 16:22:24 WARN jdbc.Utils: The use of hive.server2.thrift.http.path is
deprecated.
14/10/07 16:22:24 WARN jdbc.Utils: Please use httpPath like so:
jdbc:hive2://host:port/dbName;httpPath=http_path_value
Connected to: Apache Hive (version 0.14.0-SNAPSHOT)
Driver: Hive JDBC (version 0.14.0-SNAPSHOT)
Transaction isolation: TRANSACTION_REPEATABLE_READ
{code}
)
jdbc HTTP configuration options should be part of sessionConf part of
connection string
---
Key: HIVE-6972
URL: https://issues.apache.org/jira/browse/HIVE-6972
Project: Hive
Issue Type: Bug
Components: HiveServer2, JDBC
Affects Versions: 0.13.0
Reporter: Thejas M Nair
Assignee: Vaibhav Gumashta
Fix For: 0.14.0
Attachments: HIVE-6972.1.patch, HIVE-6972.2.patch, HIVE-6972.3.patch,
HIVE-6972.4.patch
The http connection parameters are currently part of the HiveConf section of
the connection string. It should ideally be part of SessionConf section, as
that is where rest of the connection parameters are.
HTTP transport parameters are not part of the hiveconfiguration parameters
that need to be set.
ie
instead of
jdbc:hive2://host:port/db?hive.server2.transport.mode=http;hive.server2.thrift.http.path=http_endpoint
it should be -
jdbc:hive2://host:port/db;transportMode=http;httpPath=http_endpoint
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HIVE-6972) jdbc HTTP configuration options should be part of sessionConf part of connection string
[
https://issues.apache.org/jira/browse/HIVE-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vaibhav Gumashta updated HIVE-6972:
---
Release Note:
The JDBC Uri for HiveServer2 has the form:
{code}
jdbc:hive2://host1:port1,host2:port2/dbName;sess_var_list?hive_conf_list#hive_var_list
{code}
Ideally, sess_var_list is supposed to be used to pass parameters that will be
used within the JDBC Driver. However, some of the http mode parameters were
being passed in the hive_conf_list which we've fixed now (in a backward
compatible way).
Additionally, JDBC Driver has a naming convention for the parameters in the
JDBC Uri which were not followed to the sasl.qop parameter. We've renamed it in
a backward compatible way.
Details:
*1. HTTP Mode params:*
*Old example uri:*
{code}
jdbc:hive2://host:port/dbName;user=username;password=password?hive.server2.transport.mode=http;hive.server2.thrift.http.path=httpEndpoint
{code}
*New example uri:*
{code}
jdbc:hive2://host:port/dbName;user=username;password=password;transportMode=http;httpPath=httpEndpoint?hive.server2.logging.operation.enabled=false
{code}
As you can see above, {{hive.server2.transport.mode}} has been renamed to
{{transportMode}}, {{hive.server2.thrift.http.path}} has been renamed to
{{httpPath}} and both have been moved from {{hive_conf_list}} to
{{sess_var_list}}.
*2. Sasl qop renaming:*
*Old example uri:*
{code}
jdbc:hive2://host:port/dbName;principal=hiveserver2KerberosPrincipal;sasl.qop=qopValue
{code}
*New example uri:*
{code}
jdbc:hive2://host:port/dbName;principal=hiveserver2KerberosPrincipal;saslQop=qopValue
{code}
As you can see {{sasl.qop}} has been renamed to {{saslQop}}.
Note: all changes are backward compatible and print a deprecation message like
the following:
{code}
0: jdbc:hive2://localhost:10001 !connect
jdbc:hive2://localhost:10001/;sasl.qop=auth?hive.server2.transport.mode=http;hive.server2.thrift.http.path=cliservice
username password org.apache.hive.jdbc.HiveDriver
Connecting to
jdbc:hive2://localhost:10007/;sasl.qop=auth?hive.server2.transport.mode=http;hive.server2.thrift.http.path=cliservice
14/10/07 16:22:24 INFO jdbc.Utils: Supplied authorities: localhost:10001
14/10/07 16:22:24 WARN jdbc.Utils: * JDBC param deprecation *
14/10/07 16:22:24 WARN jdbc.Utils: The use of sasl.qop is deprecated.
14/10/07 16:22:24 WARN jdbc.Utils: Please use saslQop like so:
jdbc:hive2://host:port/dbName;saslQop=qop_value
14/10/07 16:22:24 WARN jdbc.Utils: * JDBC param deprecation *
14/10/07 16:22:24 WARN jdbc.Utils: The use of hive.server2.transport.mode is
deprecated.
14/10/07 16:22:24 WARN jdbc.Utils: Please use transportMode like so:
jdbc:hive2://host:port/dbName;transportMode=transport_mode_value
14/10/07 16:22:24 WARN jdbc.Utils: * JDBC param deprecation *
14/10/07 16:22:24 WARN jdbc.Utils: The use of hive.server2.thrift.http.path is
deprecated.
14/10/07 16:22:24 WARN jdbc.Utils: Please use httpPath like so:
jdbc:hive2://host:port/dbName;httpPath=http_path_value
Connected to: Apache Hive (version 0.14.0-SNAPSHOT)
Driver: Hive JDBC (version 0.14.0-SNAPSHOT)
Transaction isolation: TRANSACTION_REPEATABLE_READ
{code}
was:
The JDBC Uri for HiveServer2 has the form:
{code}
jdbc:hive2://\host1\:\port1\,\host2\:\port2\/dbName;sess_var_list?hive_conf_list#hive_var_list
{code}
Ideally, sess_var_list is supposed to be used to pass parameters that will be
used within the JDBC Driver. However, some of the http mode parameters were
being passed in the hive_conf_list which we've fixed now (in a backward
compatible way).
Additionally, JDBC Driver has a naming convention for the parameters in the
JDBC Uri which were not followed to the sasl.qop parameter. We've renamed it in
a backward compatible way.
Details:
*1. HTTP Mode params:*
*Old example uri:*
{code}
jdbc:hive2://\host\:\port\/\db\;user=\username\;password=\password\?hive.server2.transport.mode=http;hive.server2.thrift.http.path=http_endpoint
{code}
*New example uri:*
{code}
jdbc:hive2://host:port/db;user=username;password=password;transportMode=http;httpPath=http_endpoint?hive.server2.logging.operation.enabled=false
{code}
As you can see above, {{hive.server2.transport.mode}} has been renamed to
{{transportMode}}, {{hive.server2.thrift.http.path}} has been renamed to
{{httpPath}} and both have been moved from {{hive_conf_list}} to
{{sess_var_list}}.
*2. Sasl qop renaming:*
*Old example uri:*
{code}
jdbc:hive2://host:port/db;principal=hiveserver2_kerberos_principal;sasl.qop=qop_value
{code}
*New example uri:*
{code}
jdbc:hive2://host:port/db;principal=hiveserver2_kerberos_principal;saslQop=qop_value
{code}
As you can see {{sasl.qop}} has been renamed to {{saslQop}}.
Note: all changes are backward compatible and print a deprecation message like
the following:
{code}
0: jdbc:hive2://localhost:10001 !connect
jdbc:hive2://localhost:10001/;sasl.qop=auth?hive.server2
[jira] [Updated] (HIVE-6972) jdbc HTTP configuration options should be part of sessionConf part of connection string
[
https://issues.apache.org/jira/browse/HIVE-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vaibhav Gumashta updated HIVE-6972:
---
Description:
The http connection parameters are currently part of the HiveConf section of
the connection string. It should ideally be part of SessionConf section, as
that is where rest of the connection parameters are.
HTTP transport parameters are not part of the hiveconfiguration parameters that
need to be set.
ie
instead of
jdbc:hive2://host:port/db?hive.server2.transport.mode=http;hive.server2.thrift.http.path=http_endpoint
it should be -
jdbc:hive2://host:port/db;transportMode=http;httpPath=http_endpoint
*Release Note:*
The JDBC Uri for HiveServer2 has the form:
{code}
jdbc:hive2://host1:port1,host2:port2/dbName;sess_var_list?hive_conf_list#hive_var_list
{code}
Ideally, sess_var_list is supposed to be used to pass parameters that will be
used within the JDBC Driver. However, some of the http mode parameters were
being passed in the hive_conf_list which we've fixed now (in a backward
compatible way).
Additionally, JDBC Driver has a naming convention for the parameters in the
JDBC Uri which were not followed to the sasl.qop parameter. We've renamed it in
a backward compatible way.
Details:
*1. HTTP Mode params:*
*Old example uri:*
{code}
jdbc:hive2://host:port/dbName;user=username;password=password?hive.server2.transport.mode=http;hive.server2.thrift.http.path=httpEndpoint
{code}
*New example uri:*
{code}
jdbc:hive2://host:port/dbName;user=username;password=password;transportMode=http;httpPath=httpEndpoint?hive.server2.logging.operation.enabled=false
{code}
As you can see above, {{hive.server2.transport.mode}} has been renamed to
{{transportMode}}, {{hive.server2.thrift.http.path}} has been renamed to
{{httpPath}} and both have been moved from {{hive_conf_list}} to
{{sess_var_list}}.
*2. Sasl qop renaming:*
*Old example uri:*
{code}
jdbc:hive2://host:port/dbName;principal=hiveserver2KerberosPrincipal;sasl.qop=qopValue
{code}
*New example uri:*
{code}
jdbc:hive2://host:port/dbName;principal=hiveserver2KerberosPrincipal;saslQop=qopValue
{code}
As you can see {{sasl.qop}} has been renamed to {{saslQop}}.
Note: all changes are backward compatible and print a deprecation message like
the following:
{code}
0: jdbc:hive2://localhost:10001 !connect
jdbc:hive2://localhost:10001/;sasl.qop=auth?hive.server2.transport.mode=http;hive.server2.thrift.http.path=cliservice
username password org.apache.hive.jdbc.HiveDriver
Connecting to
jdbc:hive2://localhost:10007/;sasl.qop=auth?hive.server2.transport.mode=http;hive.server2.thrift.http.path=cliservice
14/10/07 16:22:24 INFO jdbc.Utils: Supplied authorities: localhost:10001
14/10/07 16:22:24 WARN jdbc.Utils: * JDBC param deprecation *
14/10/07 16:22:24 WARN jdbc.Utils: The use of sasl.qop is deprecated.
14/10/07 16:22:24 WARN jdbc.Utils: Please use saslQop like so:
jdbc:hive2://host:port/dbName;saslQop=qop_value
14/10/07 16:22:24 WARN jdbc.Utils: * JDBC param deprecation *
14/10/07 16:22:24 WARN jdbc.Utils: The use of hive.server2.transport.mode is
deprecated.
14/10/07 16:22:24 WARN jdbc.Utils: Please use transportMode like so:
jdbc:hive2://host:port/dbName;transportMode=transport_mode_value
14/10/07 16:22:24 WARN jdbc.Utils: * JDBC param deprecation *
14/10/07 16:22:24 WARN jdbc.Utils: The use of hive.server2.thrift.http.path is
deprecated.
14/10/07 16:22:24 WARN jdbc.Utils: Please use httpPath like so:
jdbc:hive2://host:port/dbName;httpPath=http_path_value
Connected to: Apache Hive (version 0.14.0-SNAPSHOT)
Driver: Hive JDBC (version 0.14.0-SNAPSHOT)
Transaction isolation: TRANSACTION_REPEATABLE_READ
{code}
was:
The http connection parameters are currently part of the HiveConf section of
the connection string. It should ideally be part of SessionConf section, as
that is where rest of the connection parameters are.
HTTP transport parameters are not part of the hiveconfiguration parameters that
need to be set.
ie
instead of
jdbc:hive2://host:port/db?hive.server2.transport.mode=http;hive.server2.thrift.http.path=http_endpoint
it should be -
jdbc:hive2://host:port/db;transportMode=http;httpPath=http_endpoint
jdbc HTTP configuration options should be part of sessionConf part of
connection string
---
Key: HIVE-6972
URL: https://issues.apache.org/jira/browse/HIVE-6972
Project: Hive
Issue Type: Bug
Components: HiveServer2, JDBC
Affects Versions: 0.13.0
Reporter: Thejas M Nair
Assignee: Vaibhav Gumashta
Fix For: 0.14.0
Attachments: HIVE-6972.1.patch, HIVE-6972.2.patch, HIVE-6972.3.patch,
HIVE-6972.4.patch
The http connection parameters are currently part of the HiveConf section of
the connection
[jira] [Commented] (HIVE-6972) jdbc HTTP configuration options should be part of sessionConf part of connection string
[
https://issues.apache.org/jira/browse/HIVE-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14168810#comment-14168810
]
Vaibhav Gumashta commented on HIVE-6972:
[~leftylev] Just added the release note in the description (wasn't able to
format the release note text box properly).
jdbc HTTP configuration options should be part of sessionConf part of
connection string
---
Key: HIVE-6972
URL: https://issues.apache.org/jira/browse/HIVE-6972
Project: Hive
Issue Type: Bug
Components: HiveServer2, JDBC
Affects Versions: 0.13.0
Reporter: Thejas M Nair
Assignee: Vaibhav Gumashta
Fix For: 0.14.0
Attachments: HIVE-6972.1.patch, HIVE-6972.2.patch, HIVE-6972.3.patch,
HIVE-6972.4.patch
The http connection parameters are currently part of the HiveConf section of
the connection string. It should ideally be part of SessionConf section, as
that is where rest of the connection parameters are.
HTTP transport parameters are not part of the hiveconfiguration parameters
that need to be set.
ie
instead of
jdbc:hive2://host:port/db?hive.server2.transport.mode=http;hive.server2.thrift.http.path=http_endpoint
it should be -
jdbc:hive2://host:port/db;transportMode=http;httpPath=http_endpoint
*Release Note:*
The JDBC Uri for HiveServer2 has the form:
{code}
jdbc:hive2://host1:port1,host2:port2/dbName;sess_var_list?hive_conf_list#hive_var_list
{code}
Ideally, sess_var_list is supposed to be used to pass parameters that will be
used within the JDBC Driver. However, some of the http mode parameters were
being passed in the hive_conf_list which we've fixed now (in a backward
compatible way).
Additionally, JDBC Driver has a naming convention for the parameters in the
JDBC Uri which were not followed to the sasl.qop parameter. We've renamed it
in a backward compatible way.
Details:
*1. HTTP Mode params:*
*Old example uri:*
{code}
jdbc:hive2://host:port/dbName;user=username;password=password?hive.server2.transport.mode=http;hive.server2.thrift.http.path=httpEndpoint
{code}
*New example uri:*
{code}
jdbc:hive2://host:port/dbName;user=username;password=password;transportMode=http;httpPath=httpEndpoint?hive.server2.logging.operation.enabled=false
{code}
As you can see above, {{hive.server2.transport.mode}} has been renamed to
{{transportMode}}, {{hive.server2.thrift.http.path}} has been renamed to
{{httpPath}} and both have been moved from {{hive_conf_list}} to
{{sess_var_list}}.
*2. Sasl qop renaming:*
*Old example uri:*
{code}
jdbc:hive2://host:port/dbName;principal=hiveserver2KerberosPrincipal;sasl.qop=qopValue
{code}
*New example uri:*
{code}
jdbc:hive2://host:port/dbName;principal=hiveserver2KerberosPrincipal;saslQop=qopValue
{code}
As you can see {{sasl.qop}} has been renamed to {{saslQop}}.
Note: all changes are backward compatible and print a deprecation message
like the following:
{code}
0: jdbc:hive2://localhost:10001 !connect
jdbc:hive2://localhost:10001/;sasl.qop=auth?hive.server2.transport.mode=http;hive.server2.thrift.http.path=cliservice
username password org.apache.hive.jdbc.HiveDriver
Connecting to
jdbc:hive2://localhost:10007/;sasl.qop=auth?hive.server2.transport.mode=http;hive.server2.thrift.http.path=cliservice
14/10/07 16:22:24 INFO jdbc.Utils: Supplied authorities: localhost:10001
14/10/07 16:22:24 WARN jdbc.Utils: * JDBC param deprecation *
14/10/07 16:22:24 WARN jdbc.Utils: The use of sasl.qop is deprecated.
14/10/07 16:22:24 WARN jdbc.Utils: Please use saslQop like so:
jdbc:hive2://host:port/dbName;saslQop=qop_value
14/10/07 16:22:24 WARN jdbc.Utils: * JDBC param deprecation *
14/10/07 16:22:24 WARN jdbc.Utils: The use of hive.server2.transport.mode is
deprecated.
14/10/07 16:22:24 WARN jdbc.Utils: Please use transportMode like so:
jdbc:hive2://host:port/dbName;transportMode=transport_mode_value
14/10/07 16:22:24 WARN jdbc.Utils: * JDBC param deprecation *
14/10/07 16:22:24 WARN jdbc.Utils: The use of hive.server2.thrift.http.path
is deprecated.
14/10/07 16:22:24 WARN jdbc.Utils: Please use httpPath like so:
jdbc:hive2://host:port/dbName;httpPath=http_path_value
Connected to: Apache Hive (version 0.14.0-SNAPSHOT)
Driver: Hive JDBC (version 0.14.0-SNAPSHOT)
Transaction isolation: TRANSACTION_REPEATABLE_READ
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HIVE-6972) jdbc HTTP configuration options should be part of sessionConf part of connection string
[
https://issues.apache.org/jira/browse/HIVE-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14168280#comment-14168280
]
Vaibhav Gumashta commented on HIVE-6972:
[~thejas] I don't think the test failure is related, but since all tests are
not running, I'm not sure if this should be committed yet.
Although I do see all the test from the following packages pass:
{code}
org.apache.hive.jdbc
org.apache.hive.jdbc.authorization
org.apache.hive.jdbc.miniHS2
org.apache.hive.minikdc
org.apache.hive.service
org.apache.hive.service.auth
org.apache.hive.service.cli
org.apache.hive.service.cli.operation
org.apache.hive.service.cli.session
org.apache.hive.service.cli.thrift
org.apache.hive.service.server
{code}
I doubt if the patch affects any other tests.
jdbc HTTP configuration options should be part of sessionConf part of
connection string
---
Key: HIVE-6972
URL: https://issues.apache.org/jira/browse/HIVE-6972
Project: Hive
Issue Type: Bug
Components: HiveServer2, JDBC
Affects Versions: 0.13.0
Reporter: Thejas M Nair
Assignee: Vaibhav Gumashta
Fix For: 0.14.0
Attachments: HIVE-6972.1.patch, HIVE-6972.2.patch, HIVE-6972.3.patch,
HIVE-6972.4.patch
The http connection parameters are currently part of the HiveConf section of
the connection string. It should ideally be part of SessionConf section, as
that is where rest of the connection parameters are.
HTTP transport parameters are not part of the hiveconfiguration parameters
that need to be set.
ie
instead of
jdbc:hive2://host:port/db?hive.server2.transport.mode=http;hive.server2.thrift.http.path=http_endpoint
it should be -
jdbc:hive2://host:port/db;transportMode=http;httpPath=http_endpoint
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HIVE-6972) jdbc HTTP configuration options should be part of sessionConf part of connection string
[ https://issues.apache.org/jira/browse/HIVE-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-6972: --- Resolution: Fixed Status: Resolved (was: Patch Available) Patch committed to 14 and trunk as all of the tests for jdbc/HiveServer2 seem to be running . Thanks for reviewing [~thejas]! jdbc HTTP configuration options should be part of sessionConf part of connection string --- Key: HIVE-6972 URL: https://issues.apache.org/jira/browse/HIVE-6972 Project: Hive Issue Type: Bug Components: HiveServer2, JDBC Affects Versions: 0.13.0 Reporter: Thejas M Nair Assignee: Vaibhav Gumashta Fix For: 0.14.0 Attachments: HIVE-6972.1.patch, HIVE-6972.2.patch, HIVE-6972.3.patch, HIVE-6972.4.patch The http connection parameters are currently part of the HiveConf section of the connection string. It should ideally be part of SessionConf section, as that is where rest of the connection parameters are. HTTP transport parameters are not part of the hiveconfiguration parameters that need to be set. ie instead of jdbc:hive2://host:port/db?hive.server2.transport.mode=http;hive.server2.thrift.http.path=http_endpoint it should be - jdbc:hive2://host:port/db;transportMode=http;httpPath=http_endpoint -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HIVE-6972) jdbc HTTP configuration options should be part of sessionConf part of connection string
[ https://issues.apache.org/jira/browse/HIVE-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14168323#comment-14168323 ] Vaibhav Gumashta commented on HIVE-6972: Sorry missed out adding reviewed by. jdbc HTTP configuration options should be part of sessionConf part of connection string --- Key: HIVE-6972 URL: https://issues.apache.org/jira/browse/HIVE-6972 Project: Hive Issue Type: Bug Components: HiveServer2, JDBC Affects Versions: 0.13.0 Reporter: Thejas M Nair Assignee: Vaibhav Gumashta Fix For: 0.14.0 Attachments: HIVE-6972.1.patch, HIVE-6972.2.patch, HIVE-6972.3.patch, HIVE-6972.4.patch The http connection parameters are currently part of the HiveConf section of the connection string. It should ideally be part of SessionConf section, as that is where rest of the connection parameters are. HTTP transport parameters are not part of the hiveconfiguration parameters that need to be set. ie instead of jdbc:hive2://host:port/db?hive.server2.transport.mode=http;hive.server2.thrift.http.path=http_endpoint it should be - jdbc:hive2://host:port/db;transportMode=http;httpPath=http_endpoint -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: updating a patch while the precommit build is in Jenkins queue
AFAIK, it runs the latest patch. Thanks, --Vaibhav On Fri, Oct 10, 2014 at 12:53 PM, Sergey Shelukhin ser...@hortonworks.com wrote: Hi. I have a JIRA that is in Jenkins queue for precommit build. It won't run for a while. Does anyone know if the queued job will run the patch that triggered it, or the latest patch? I want to upload a new patch and want it to run w/that job. -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
[jira] [Commented] (HIVE-8427) Hive Streaming : secure streaming hangs leading to time outs.
[
https://issues.apache.org/jira/browse/HIVE-8427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14167614#comment-14167614
]
Vaibhav Gumashta commented on HIVE-8427:
How about you use {code} ShimLoader.getHadoopShims().isSecurityEnabled() {code}
to determine whether it's a secure cluster or not?
Hive Streaming : secure streaming hangs leading to time outs.
--
Key: HIVE-8427
URL: https://issues.apache.org/jira/browse/HIVE-8427
Project: Hive
Issue Type: Bug
Components: HCatalog
Affects Versions: 0.14.0
Reporter: Roshan Naik
Assignee: Roshan Naik
Labels: ACID, Streaming
Fix For: 0.14.0
Attachments: HIVE-8427.patch
Need to enable Thrift Sasl setting for secure mode communcation
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HIVE-8427) Hive Streaming : secure streaming hangs leading to time outs.
[ https://issues.apache.org/jira/browse/HIVE-8427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14167768#comment-14167768 ] Vaibhav Gumashta commented on HIVE-8427: [~roshan_naik] Makes sense. Thanks for the note. Hive Streaming : secure streaming hangs leading to time outs. -- Key: HIVE-8427 URL: https://issues.apache.org/jira/browse/HIVE-8427 Project: Hive Issue Type: Bug Components: HCatalog Affects Versions: 0.14.0 Reporter: Roshan Naik Assignee: Roshan Naik Labels: ACID, Streaming Fix For: 0.14.0 Attachments: HIVE-8427.patch Need to enable Thrift Sasl setting for secure mode communcation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 26429: jdbc HTTP configuration options should be part of sessionConf part of connection string
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26429/ --- (Updated Oct. 9, 2014, 7:48 a.m.) Review request for hive and Thejas Nair. Bugs: HIVE-6972 https://issues.apache.org/jira/browse/HIVE-6972 Repository: hive-git Description --- https://issues.apache.org/jira/browse/HIVE-6972 Diffs (updated) - itests/hive-unit/src/test/java/org/apache/hive/jdbc/TestJdbcDriver2.java 15ff1f4 jdbc/src/java/org/apache/hive/jdbc/HiveConnection.java e0d2d6d jdbc/src/java/org/apache/hive/jdbc/Utils.java 8961e2b Diff: https://reviews.apache.org/r/26429/diff/ Testing --- Deprecation messages print like this: 0: jdbc:hive2://localhost:10007 !connect jdbc:hive2://localhost:10007/;sasl.qop=auth?hive.server2.transport.mode=http;hive.server2.thrift.http.path=cliservice vgumashta vgumashta org.apache.hive.jdbc.HiveDriver Connecting to jdbc:hive2://localhost:10007/;sasl.qop=auth?hive.server2.transport.mode=http;hive.server2.thrift.http.path=cliservice 14/10/07 16:22:24 INFO jdbc.Utils: Supplied authorities: localhost:10007 14/10/07 16:22:24 WARN jdbc.Utils: * JDBC param deprecation * 14/10/07 16:22:24 WARN jdbc.Utils: The use of sasl.qop is deprecated. 14/10/07 16:22:24 WARN jdbc.Utils: Please use saslQop like so: jdbc:hive2://host:port/dbName;saslQop=qop_value 14/10/07 16:22:24 WARN jdbc.Utils: * JDBC param deprecation * 14/10/07 16:22:24 WARN jdbc.Utils: The use of hive.server2.transport.mode is deprecated. 14/10/07 16:22:24 WARN jdbc.Utils: Please use transportMode like so: jdbc:hive2://host:port/dbName;transportMode=transport_mode_value 14/10/07 16:22:24 WARN jdbc.Utils: * JDBC param deprecation * 14/10/07 16:22:24 WARN jdbc.Utils: The use of hive.server2.thrift.http.path is deprecated. 14/10/07 16:22:24 WARN jdbc.Utils: Please use httpPath like so: jdbc:hive2://host:port/dbName;httpPath=http_path_value Connected to: Apache Hive (version 0.14.0-SNAPSHOT) Driver: Hive JDBC (version 0.14.0-SNAPSHOT) Transaction isolation: TRANSACTION_REPEATABLE_READ Thanks, Vaibhav Gumashta
[jira] [Updated] (HIVE-6972) jdbc HTTP configuration options should be part of sessionConf part of connection string
[ https://issues.apache.org/jira/browse/HIVE-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-6972: --- Attachment: HIVE-6972.4.patch Fixes test failure. jdbc HTTP configuration options should be part of sessionConf part of connection string --- Key: HIVE-6972 URL: https://issues.apache.org/jira/browse/HIVE-6972 Project: Hive Issue Type: Bug Components: HiveServer2, JDBC Affects Versions: 0.13.0 Reporter: Thejas M Nair Assignee: Vaibhav Gumashta Fix For: 0.14.0 Attachments: HIVE-6972.1.patch, HIVE-6972.2.patch, HIVE-6972.3.patch, HIVE-6972.4.patch The http connection parameters are currently part of the HiveConf section of the connection string. It should ideally be part of SessionConf section, as that is where rest of the connection parameters are. HTTP transport parameters are not part of the hiveconfiguration parameters that need to be set. ie instead of jdbc:hive2://host:port/db?hive.server2.transport.mode=http;hive.server2.thrift.http.path=http_endpoint it should be - jdbc:hive2://host:port/db;transportMode=http;httpPath=http_endpoint -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HIVE-8376) Umbrella Jira for HiveServer2 dynamic service discovery
[ https://issues.apache.org/jira/browse/HIVE-8376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14164930#comment-14164930 ] Vaibhav Gumashta commented on HIVE-8376: I'll also update the wiki soon and ping [~leftylev] for review. Umbrella Jira for HiveServer2 dynamic service discovery --- Key: HIVE-8376 URL: https://issues.apache.org/jira/browse/HIVE-8376 Project: Hive Issue Type: New Feature Components: HiveServer2, JDBC Affects Versions: 0.14.0 Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Labels: TODOC14 Fix For: 0.14.0 Attachments: HiveServer2DynamicServiceDiscovery.pdf Creating an ☂ Jira for documentation purpose. I'll add a detailed doc for the implementation usage here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HIVE-8414) HiveConnection.openSession should throw exception if session handle is null
[ https://issues.apache.org/jira/browse/HIVE-8414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14165544#comment-14165544 ] Vaibhav Gumashta commented on HIVE-8414: [~cdrome] The current patch looks good - thanks for catching this. Let me know whenever you think it's ready for review. HiveConnection.openSession should throw exception if session handle is null --- Key: HIVE-8414 URL: https://issues.apache.org/jira/browse/HIVE-8414 Project: Hive Issue Type: Bug Components: JDBC Affects Versions: 0.14.0, 0.15.0 Reporter: Chris Drome Assignee: Chris Drome Priority: Minor Attachments: HIVE-8414-1.patch HiveConnection should verify the session handle in openSession and throw a SQLException if null. Ran into this problem by trying to send configs that change restricted params. Without a valid session handle, all subsequent operation with the connection will fail. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-5200) Write tests for state transitions of an operation in HS2
[ https://issues.apache.org/jira/browse/HIVE-5200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-5200: --- Fix Version/s: (was: 0.14.0) 0.15.0 Write tests for state transitions of an operation in HS2 Key: HIVE-5200 URL: https://issues.apache.org/jira/browse/HIVE-5200 Project: Hive Issue Type: Test Components: HiveServer2 Affects Versions: 0.12.0 Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Fix For: 0.15.0 The test should assert valid transitions for both synchronous and asynchronous execution. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-5305) A ResultSet object should be automatically closed when the Statement object that generated it is closed, re-executed, or used to retrieve the next result from a sequence o
[ https://issues.apache.org/jira/browse/HIVE-5305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-5305: --- Fix Version/s: (was: 0.14.0) 0.15.0 A ResultSet object should be automatically closed when the Statement object that generated it is closed, re-executed, or used to retrieve the next result from a sequence of multiple results. -- Key: HIVE-5305 URL: https://issues.apache.org/jira/browse/HIVE-5305 Project: Hive Issue Type: Bug Components: JDBC Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Fix For: 0.15.0 Per the API docs: http://docs.oracle.com/javase/7/docs/api/java/sql/ResultSet.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-5312) Let HiveServer2 run simultaneously in HTTP (over thrift) and Binary (normal thrift transport) mode
[ https://issues.apache.org/jira/browse/HIVE-5312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-5312: --- Fix Version/s: (was: 0.14.0) 0.15.0 Let HiveServer2 run simultaneously in HTTP (over thrift) and Binary (normal thrift transport) mode --- Key: HIVE-5312 URL: https://issues.apache.org/jira/browse/HIVE-5312 Project: Hive Issue Type: Sub-task Components: HiveServer2 Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Fix For: 0.15.0 [HIVE-4763|https://issues.apache.org/jira/browse/HIVE-4763] adds support for HTTP transport over thrift. With that, HS2 can be configured to run either using using HTTP or using normal thrift binary transport. Ideally HS2 should be supporting both modes simultaneously and the client should be able to specify the mode used in serving the request. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-6504) Refactor JDBC HiveConnection to use a factory to create client transport.
[ https://issues.apache.org/jira/browse/HIVE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-6504: --- Fix Version/s: (was: 0.14.0) 0.15.0 Refactor JDBC HiveConnection to use a factory to create client transport. - Key: HIVE-6504 URL: https://issues.apache.org/jira/browse/HIVE-6504 Project: Hive Issue Type: Improvement Components: JDBC Affects Versions: 0.13.0 Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Fix For: 0.15.0 The client transport creation is quite messy. Need to clean it up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-6286) HiveServer2 binary (raw thrift) ssl transport should also support PKCS12 keystore format
[ https://issues.apache.org/jira/browse/HIVE-6286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-6286: --- Assignee: (was: Vaibhav Gumashta) HiveServer2 binary (raw thrift) ssl transport should also support PKCS12 keystore format Key: HIVE-6286 URL: https://issues.apache.org/jira/browse/HIVE-6286 Project: Hive Issue Type: Bug Components: HiveServer2, JDBC Affects Versions: 0.13.0 Reporter: Vaibhav Gumashta Currently only supports the JKS keystore format , whereas Java supports both JKS and PKCS12. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-6535) jdbc async wait should happen during fetch for results
[ https://issues.apache.org/jira/browse/HIVE-6535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-6535: --- Fix Version/s: (was: 0.14.0) 0.15.0 jdbc async wait should happen during fetch for results -- Key: HIVE-6535 URL: https://issues.apache.org/jira/browse/HIVE-6535 Project: Hive Issue Type: Improvement Components: HiveServer2, JDBC Affects Versions: 0.14.0 Reporter: Thejas M Nair Assignee: Vaibhav Gumashta Fix For: 0.15.0 The hive jdbc client waits query completion during execute() call. It would be better to block in the jdbc for completion when the results are being fetched. This way the application using hive jdbc driver can do other tasks while asynchronous query execution is happening, until it needs to fetch the result set. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-6286) HiveServer2 binary (raw thrift) ssl transport should also support PKCS12 keystore format
[ https://issues.apache.org/jira/browse/HIVE-6286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-6286: --- Fix Version/s: (was: 0.14.0) HiveServer2 binary (raw thrift) ssl transport should also support PKCS12 keystore format Key: HIVE-6286 URL: https://issues.apache.org/jira/browse/HIVE-6286 Project: Hive Issue Type: Bug Components: HiveServer2, JDBC Affects Versions: 0.13.0 Reporter: Vaibhav Gumashta Currently only supports the JKS keystore format , whereas Java supports both JKS and PKCS12. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-5571) Add support for COMPILING state to OperationState in HiveServer2
[ https://issues.apache.org/jira/browse/HIVE-5571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-5571: --- Fix Version/s: (was: 0.14.0) 0.15.0 Add support for COMPILING state to OperationState in HiveServer2 Key: HIVE-5571 URL: https://issues.apache.org/jira/browse/HIVE-5571 Project: Hive Issue Type: Improvement Components: HiveServer2, JDBC Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Fix For: 0.15.0 [HIVE-5441|https://issues.apache.org/jira/browse/HIVE-5441] splits query execution into compile + run. However, compilation is synchronous whereas execution can be both synchronous asynchronous. We should add a new COMPILING state and expose that to the client as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-6926) HiveServer2 should use tcp instead of binary as the name of the transport mode
[ https://issues.apache.org/jira/browse/HIVE-6926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-6926: --- Fix Version/s: (was: 0.14.0) 0.15.0 HiveServer2 should use tcp instead of binary as the name of the transport mode -- Key: HIVE-6926 URL: https://issues.apache.org/jira/browse/HIVE-6926 Project: Hive Issue Type: Bug Components: HiveServer2 Affects Versions: 0.14.0 Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Fix For: 0.15.0 I think the name binary really doesn't convey anything. I'll make the change in a backward compatible way. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-7968) Merge tests in TestJdbcWithMiniMr with TestJdbcWithMiniHS2
[ https://issues.apache.org/jira/browse/HIVE-7968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-7968: --- Fix Version/s: (was: 0.14.0) 0.15.0 Merge tests in TestJdbcWithMiniMr with TestJdbcWithMiniHS2 -- Key: HIVE-7968 URL: https://issues.apache.org/jira/browse/HIVE-7968 Project: Hive Issue Type: Bug Components: HiveServer2, JDBC Affects Versions: 0.14.0 Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Fix For: 0.15.0 MiniHS2 uses MiniMr. Makes no sense to have two test cases for same setup when JDBC is the client api for HS2. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-7968) Merge tests in TestJdbcWithMiniMr with TestJdbcWithMiniHS2
[ https://issues.apache.org/jira/browse/HIVE-7968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-7968: --- Assignee: (was: Vaibhav Gumashta) Merge tests in TestJdbcWithMiniMr with TestJdbcWithMiniHS2 -- Key: HIVE-7968 URL: https://issues.apache.org/jira/browse/HIVE-7968 Project: Hive Issue Type: Bug Components: HiveServer2, JDBC Affects Versions: 0.14.0 Reporter: Vaibhav Gumashta Fix For: 0.15.0 MiniHS2 uses MiniMr. Makes no sense to have two test cases for same setup when JDBC is the client api for HS2. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-7224) Set incremental printing to true by default in Beeline
[ https://issues.apache.org/jira/browse/HIVE-7224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-7224: --- Fix Version/s: (was: 0.14.0) 0.15.0 Set incremental printing to true by default in Beeline -- Key: HIVE-7224 URL: https://issues.apache.org/jira/browse/HIVE-7224 Project: Hive Issue Type: Bug Components: Clients, JDBC Affects Versions: 0.13.0 Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Fix For: 0.15.0 Attachments: HIVE-7224.1.patch See HIVE-7221. By default beeline tries to buffer the entire output relation before printing it on stdout. This can cause OOM when the output relation is large. However, beeline has the option of incremental prints. We should keep that as the default. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-7968) Merge tests in TestJdbcWithMiniMr with TestJdbcWithMiniHS2
[ https://issues.apache.org/jira/browse/HIVE-7968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-7968: --- Priority: Major (was: Critical) Merge tests in TestJdbcWithMiniMr with TestJdbcWithMiniHS2 -- Key: HIVE-7968 URL: https://issues.apache.org/jira/browse/HIVE-7968 Project: Hive Issue Type: Bug Components: HiveServer2, JDBC Affects Versions: 0.14.0 Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Fix For: 0.15.0 MiniHS2 uses MiniMr. Makes no sense to have two test cases for same setup when JDBC is the client api for HS2. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-5373) Add concurrency tests to HiveServer2
[ https://issues.apache.org/jira/browse/HIVE-5373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-5373: --- Fix Version/s: 0.15.0 Add concurrency tests to HiveServer2 Key: HIVE-5373 URL: https://issues.apache.org/jira/browse/HIVE-5373 Project: Hive Issue Type: Test Components: HiveServer2, JDBC Reporter: Vaibhav Gumashta Assignee: Vaibhav Gumashta Fix For: 0.15.0 TestHiveServer2Concurrency.java has nothing as of now. It is important to have some measure of concurrency that we can support. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-7150) FileInputStream is not closed in HiveConnection#getHttpClient()
[
https://issues.apache.org/jira/browse/HIVE-7150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vaibhav Gumashta updated HIVE-7150:
---
Fix Version/s: 0.15.0
FileInputStream is not closed in HiveConnection#getHttpClient()
---
Key: HIVE-7150
URL: https://issues.apache.org/jira/browse/HIVE-7150
Project: Hive
Issue Type: Bug
Reporter: Ted Yu
Assignee: Vaibhav Gumashta
Fix For: 0.15.0
Here is related code:
{code}
sslTrustStore.load(new FileInputStream(sslTrustStorePath),
sslTrustStorePassword.toCharArray());
{code}
The FileInputStream is not closed upon returning from the method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HIVE-6857) Refactor HiveServer2 TSetIpAddressProcessor
[
https://issues.apache.org/jira/browse/HIVE-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vaibhav Gumashta updated HIVE-6857:
---
Fix Version/s: 0.15.0
Refactor HiveServer2 TSetIpAddressProcessor
---
Key: HIVE-6857
URL: https://issues.apache.org/jira/browse/HIVE-6857
Project: Hive
Issue Type: Bug
Components: HiveServer2
Reporter: Vaibhav Gumashta
Assignee: Vaibhav Gumashta
Fix For: 0.15.0
Excerpt from HIVE-6837 and related issues:
1. SessionManager#openSession:
{code}
public SessionHandle openSession(TProtocolVersion protocol, String username,
String password,
MapString, String sessionConf, boolean withImpersonation, String
delegationToken)
throws HiveSQLException {
HiveSession session;
if (withImpersonation) {
HiveSessionImplwithUGI hiveSessionUgi = new
HiveSessionImplwithUGI(protocol, username, password,
hiveConf, sessionConf, TSetIpAddressProcessor.getUserIpAddress(),
delegationToken);
session = HiveSessionProxy.getProxy(hiveSessionUgi,
hiveSessionUgi.getSessionUgi());
hiveSessionUgi.setProxySession(session);
} else {
session = new HiveSessionImpl(protocol, username, password, hiveConf,
sessionConf,
TSetIpAddressProcessor.getUserIpAddress());
}
session.setSessionManager(this);
session.setOperationManager(operationManager);
session.open();
handleToSession.put(session.getSessionHandle(), session);
try {
executeSessionHooks(session);
} catch (Exception e) {
throw new HiveSQLException(Failed to execute session hooks, e);
}
return session.getSessionHandle();
}
{code}
Notice that if withImpersonation is set to true, we're using
TSetIpAddressProcessor.getUserIpAddress() to get the IP address which is
wrong for a kerberized setup (should use HiveAuthFactory#getIpAddress).
2. Also, in case of a kerberized setup, we're wrapping the transport in a
doAs (with UGI of the HiveServer2 process) which doesn't make sense to me:
https://github.com/apache/hive/blob/trunk/shims/common-secure/src/main/java/org/apache/hadoop/hive/thrift/HadoopThriftAuthBridge20S.java#L335.
3. The name TSetIpAddressProcessor should be replaced with something more
meaningful like TPlainSASLProcessor.
4. Consolidate thread locals used for username, ipaddress
5. Do not directly use TSetIpAddressProcessor; get it via factory like here:
https://github.com/apache/hive/blob/trunk/service/src/java/org/apache/hive/service/auth/HiveAuthFactory.java#L161
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HIVE-7150) FileInputStream is not closed in HiveConnection#getHttpClient()
[
https://issues.apache.org/jira/browse/HIVE-7150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vaibhav Gumashta updated HIVE-7150:
---
Assignee: (was: Vaibhav Gumashta)
FileInputStream is not closed in HiveConnection#getHttpClient()
---
Key: HIVE-7150
URL: https://issues.apache.org/jira/browse/HIVE-7150
Project: Hive
Issue Type: Bug
Reporter: Ted Yu
Fix For: 0.15.0
Here is related code:
{code}
sslTrustStore.load(new FileInputStream(sslTrustStorePath),
sslTrustStorePassword.toCharArray());
{code}
The FileInputStream is not closed upon returning from the method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
