[jira] [Commented] (HIVE-19744) In Beeline if -u is specified the default connection should not be tried at all
[ https://issues.apache.org/jira/browse/HIVE-19744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16512340#comment-16512340 ] Peter Vary commented on HIVE-19744: --- +1 LGTM > In Beeline if -u is specified the default connection should not be tried at > all > --- > > Key: HIVE-19744 > URL: https://issues.apache.org/jira/browse/HIVE-19744 > Project: Hive > Issue Type: Bug > Components: Beeline >Reporter: Zoltan Haindrich >Assignee: Zoltan Haindrich >Priority: Major > Attachments: HIVE-19744.01.patch > > > I wanted to explicitly connect to a hiveserver by specifying {{-u}} but that > didn't work because it was not running/etc... > The strange thing is that somehow the default connection is activated...and > tried > The possible "hazard" here is that if someone specifies {{-u $MY_DEV_HS2 -f > recreate_db.sql}} to run some sql script...beeline may connect somewhere else > and run the commands there - which might have serious consequences (in > the above case having default as production might be interesting) > {code} > beeline -u jdbc:hive2://localhost:10502/;transportMode=binary -n hrt_qa > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in > [jar:file:/usr/hdp/3.0.0.0-1406/hive/lib/log4j-slf4j-impl-2.10.0.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in > [jar:file:/usr/hdp/3.0.0.0-1406/hadoop/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an > explanation. > SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory] > Connecting to jdbc:hive2://localhost:10502/ > 18/05/31 07:51:20 [main]: WARN jdbc.HiveConnection: Failed to connect to > localhost:10502 > Unknown HS2 problem when communicating with Thrift server. > Error: Could not open client transport with JDBC Uri: > jdbc:hive2://localhost:10502/: Invalid status 72 (state=08S01,code=0) > Connecting to > jdbc:hive2://ctr-e138-1518143905142-336795-01-16.hwx.site:2181,ctr-e138-1518143905142-336795-01-08.hwx.site:2181,ctr-e138-1518143905142-336795-01-14.hwx.site:2181,ctr-e138-1518143905142-336795-01-09.hwx.site:2181,ctr-e138-1518143905142-336795-01-15.hwx.site:2181/default;httpPath=cliservice;principal=hive/_h...@example.com;serviceDiscoveryMode=zooKeeper;ssl=true;transportMode=http;zooKeeperNamespace=hiveserver2 > 18/05/31 07:51:21 [main]: INFO jdbc.HiveConnection: Connected to > ctr-e138-1518143905142-336795-01-03.hwx.site:10001 > 18/05/31 07:51:21 [main]: ERROR jdbc.HiveConnection: Error opening session > org.apache.thrift.transport.TTransportException: > javax.net.ssl.SSLHandshakeException: > sun.security.validator.ValidatorException: PKIX path validation failed: > java.security.cert.CertPathValidatorException: signature check failed > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HIVE-19744) In Beeline if -u is specified the default connection should not be tried at all
[ https://issues.apache.org/jira/browse/HIVE-19744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16511980#comment-16511980 ] Zoltan Haindrich commented on HIVE-19744: - [~thejas], [~vgumashta]: Could you please take a look? > In Beeline if -u is specified the default connection should not be tried at > all > --- > > Key: HIVE-19744 > URL: https://issues.apache.org/jira/browse/HIVE-19744 > Project: Hive > Issue Type: Bug > Components: Beeline >Reporter: Zoltan Haindrich >Assignee: Zoltan Haindrich >Priority: Major > Attachments: HIVE-19744.01.patch > > > I wanted to explicitly connect to a hiveserver by specifying {{-u}} but that > didn't work because it was not running/etc... > The strange thing is that somehow the default connection is activated...and > tried > The possible "hazard" here is that if someone specifies {{-u $MY_DEV_HS2 -f > recreate_db.sql}} to run some sql script...beeline may connect somewhere else > and run the commands there - which might have serious consequences (in > the above case having default as production might be interesting) > {code} > beeline -u jdbc:hive2://localhost:10502/;transportMode=binary -n hrt_qa > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in > [jar:file:/usr/hdp/3.0.0.0-1406/hive/lib/log4j-slf4j-impl-2.10.0.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in > [jar:file:/usr/hdp/3.0.0.0-1406/hadoop/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an > explanation. > SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory] > Connecting to jdbc:hive2://localhost:10502/ > 18/05/31 07:51:20 [main]: WARN jdbc.HiveConnection: Failed to connect to > localhost:10502 > Unknown HS2 problem when communicating with Thrift server. > Error: Could not open client transport with JDBC Uri: > jdbc:hive2://localhost:10502/: Invalid status 72 (state=08S01,code=0) > Connecting to > jdbc:hive2://ctr-e138-1518143905142-336795-01-16.hwx.site:2181,ctr-e138-1518143905142-336795-01-08.hwx.site:2181,ctr-e138-1518143905142-336795-01-14.hwx.site:2181,ctr-e138-1518143905142-336795-01-09.hwx.site:2181,ctr-e138-1518143905142-336795-01-15.hwx.site:2181/default;httpPath=cliservice;principal=hive/_h...@example.com;serviceDiscoveryMode=zooKeeper;ssl=true;transportMode=http;zooKeeperNamespace=hiveserver2 > 18/05/31 07:51:21 [main]: INFO jdbc.HiveConnection: Connected to > ctr-e138-1518143905142-336795-01-03.hwx.site:10001 > 18/05/31 07:51:21 [main]: ERROR jdbc.HiveConnection: Error opening session > org.apache.thrift.transport.TTransportException: > javax.net.ssl.SSLHandshakeException: > sun.security.validator.ValidatorException: PKIX path validation failed: > java.security.cert.CertPathValidatorException: signature check failed > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HIVE-19744) In Beeline if -u is specified the default connection should not be tried at all
[ https://issues.apache.org/jira/browse/HIVE-19744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16510650#comment-16510650 ] Zoltan Haindrich commented on HIVE-19744: - [~pvary] Could you please take a look? > In Beeline if -u is specified the default connection should not be tried at > all > --- > > Key: HIVE-19744 > URL: https://issues.apache.org/jira/browse/HIVE-19744 > Project: Hive > Issue Type: Bug > Components: Beeline >Reporter: Zoltan Haindrich >Assignee: Zoltan Haindrich >Priority: Major > Attachments: HIVE-19744.01.patch > > > I wanted to explicitly connect to a hiveserver by specifying {{-u}} but that > didn't work because it was not running/etc... > The strange thing is that somehow the default connection is activated...and > tried > The possible "hazard" here is that if someone specifies {{-u $MY_DEV_HS2 -f > recreate_db.sql}} to run some sql script...beeline may connect somewhere else > and run the commands there - which might have serious consequences (in > the above case having default as production might be interesting) > {code} > beeline -u jdbc:hive2://localhost:10502/;transportMode=binary -n hrt_qa > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in > [jar:file:/usr/hdp/3.0.0.0-1406/hive/lib/log4j-slf4j-impl-2.10.0.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in > [jar:file:/usr/hdp/3.0.0.0-1406/hadoop/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an > explanation. > SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory] > Connecting to jdbc:hive2://localhost:10502/ > 18/05/31 07:51:20 [main]: WARN jdbc.HiveConnection: Failed to connect to > localhost:10502 > Unknown HS2 problem when communicating with Thrift server. > Error: Could not open client transport with JDBC Uri: > jdbc:hive2://localhost:10502/: Invalid status 72 (state=08S01,code=0) > Connecting to > jdbc:hive2://ctr-e138-1518143905142-336795-01-16.hwx.site:2181,ctr-e138-1518143905142-336795-01-08.hwx.site:2181,ctr-e138-1518143905142-336795-01-14.hwx.site:2181,ctr-e138-1518143905142-336795-01-09.hwx.site:2181,ctr-e138-1518143905142-336795-01-15.hwx.site:2181/default;httpPath=cliservice;principal=hive/_h...@example.com;serviceDiscoveryMode=zooKeeper;ssl=true;transportMode=http;zooKeeperNamespace=hiveserver2 > 18/05/31 07:51:21 [main]: INFO jdbc.HiveConnection: Connected to > ctr-e138-1518143905142-336795-01-03.hwx.site:10001 > 18/05/31 07:51:21 [main]: ERROR jdbc.HiveConnection: Error opening session > org.apache.thrift.transport.TTransportException: > javax.net.ssl.SSLHandshakeException: > sun.security.validator.ValidatorException: PKIX path validation failed: > java.security.cert.CertPathValidatorException: signature check failed > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HIVE-19744) In Beeline if -u is specified the default connection should not be tried at all
[ https://issues.apache.org/jira/browse/HIVE-19744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16507713#comment-16507713 ] Zoltan Haindrich commented on HIVE-19744: - [~ashutoshc] could you take a look? > In Beeline if -u is specified the default connection should not be tried at > all > --- > > Key: HIVE-19744 > URL: https://issues.apache.org/jira/browse/HIVE-19744 > Project: Hive > Issue Type: Bug > Components: Beeline >Reporter: Zoltan Haindrich >Assignee: Zoltan Haindrich >Priority: Major > Attachments: HIVE-19744.01.patch > > > I wanted to explicitly connect to a hiveserver by specifying {{-u}} but that > didn't work because it was not running/etc... > The strange thing is that somehow the default connection is activated...and > tried > The possible "hazard" here is that if someone specifies {{-u $MY_DEV_HS2 -f > recreate_db.sql}} to run some sql script...beeline may connect somewhere else > and run the commands there - which might have serious consequences (in > the above case having default as production might be interesting) > {code} > beeline -u jdbc:hive2://localhost:10502/;transportMode=binary -n hrt_qa > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in > [jar:file:/usr/hdp/3.0.0.0-1406/hive/lib/log4j-slf4j-impl-2.10.0.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in > [jar:file:/usr/hdp/3.0.0.0-1406/hadoop/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an > explanation. > SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory] > Connecting to jdbc:hive2://localhost:10502/ > 18/05/31 07:51:20 [main]: WARN jdbc.HiveConnection: Failed to connect to > localhost:10502 > Unknown HS2 problem when communicating with Thrift server. > Error: Could not open client transport with JDBC Uri: > jdbc:hive2://localhost:10502/: Invalid status 72 (state=08S01,code=0) > Connecting to > jdbc:hive2://ctr-e138-1518143905142-336795-01-16.hwx.site:2181,ctr-e138-1518143905142-336795-01-08.hwx.site:2181,ctr-e138-1518143905142-336795-01-14.hwx.site:2181,ctr-e138-1518143905142-336795-01-09.hwx.site:2181,ctr-e138-1518143905142-336795-01-15.hwx.site:2181/default;httpPath=cliservice;principal=hive/_h...@example.com;serviceDiscoveryMode=zooKeeper;ssl=true;transportMode=http;zooKeeperNamespace=hiveserver2 > 18/05/31 07:51:21 [main]: INFO jdbc.HiveConnection: Connected to > ctr-e138-1518143905142-336795-01-03.hwx.site:10001 > 18/05/31 07:51:21 [main]: ERROR jdbc.HiveConnection: Error opening session > org.apache.thrift.transport.TTransportException: > javax.net.ssl.SSLHandshakeException: > sun.security.validator.ValidatorException: PKIX path validation failed: > java.security.cert.CertPathValidatorException: signature check failed > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HIVE-19744) In Beeline if -u is specified the default connection should not be tried at all
[ https://issues.apache.org/jira/browse/HIVE-19744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16507226#comment-16507226 ] Hive QA commented on HIVE-19744: Here are the results of testing the latest attachment: https://issues.apache.org/jira/secure/attachment/12927112/HIVE-19744.01.patch {color:green}SUCCESS:{color} +1 due to 3 test(s) being added or modified. {color:green}SUCCESS:{color} +1 due to 14514 tests passed Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/11668/testReport Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/11668/console Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-11668/ Messages: {noformat} Executing org.apache.hive.ptest.execution.TestCheckPhase Executing org.apache.hive.ptest.execution.PrepPhase Executing org.apache.hive.ptest.execution.YetusPhase Executing org.apache.hive.ptest.execution.ExecutionPhase Executing org.apache.hive.ptest.execution.ReportingPhase {noformat} This message is automatically generated. ATTACHMENT ID: 12927112 - PreCommit-HIVE-Build > In Beeline if -u is specified the default connection should not be tried at > all > --- > > Key: HIVE-19744 > URL: https://issues.apache.org/jira/browse/HIVE-19744 > Project: Hive > Issue Type: Bug > Components: Beeline >Reporter: Zoltan Haindrich >Assignee: Zoltan Haindrich >Priority: Major > Attachments: HIVE-19744.01.patch > > > I wanted to explicitly connect to a hiveserver by specifying {{-u}} but that > didn't work because it was not running/etc... > The strange thing is that somehow the default connection is activated...and > tried > The possible "hazard" here is that if someone specifies {{-u $MY_DEV_HS2 -f > recreate_db.sql}} to run some sql script...beeline may connect somewhere else > and run the commands there - which might have serious consequences (in > the above case having default as production might be interesting) > {code} > beeline -u jdbc:hive2://localhost:10502/;transportMode=binary -n hrt_qa > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in > [jar:file:/usr/hdp/3.0.0.0-1406/hive/lib/log4j-slf4j-impl-2.10.0.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in > [jar:file:/usr/hdp/3.0.0.0-1406/hadoop/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an > explanation. > SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory] > Connecting to jdbc:hive2://localhost:10502/ > 18/05/31 07:51:20 [main]: WARN jdbc.HiveConnection: Failed to connect to > localhost:10502 > Unknown HS2 problem when communicating with Thrift server. > Error: Could not open client transport with JDBC Uri: > jdbc:hive2://localhost:10502/: Invalid status 72 (state=08S01,code=0) > Connecting to > jdbc:hive2://ctr-e138-1518143905142-336795-01-16.hwx.site:2181,ctr-e138-1518143905142-336795-01-08.hwx.site:2181,ctr-e138-1518143905142-336795-01-14.hwx.site:2181,ctr-e138-1518143905142-336795-01-09.hwx.site:2181,ctr-e138-1518143905142-336795-01-15.hwx.site:2181/default;httpPath=cliservice;principal=hive/_h...@example.com;serviceDiscoveryMode=zooKeeper;ssl=true;transportMode=http;zooKeeperNamespace=hiveserver2 > 18/05/31 07:51:21 [main]: INFO jdbc.HiveConnection: Connected to > ctr-e138-1518143905142-336795-01-03.hwx.site:10001 > 18/05/31 07:51:21 [main]: ERROR jdbc.HiveConnection: Error opening session > org.apache.thrift.transport.TTransportException: > javax.net.ssl.SSLHandshakeException: > sun.security.validator.ValidatorException: PKIX path validation failed: > java.security.cert.CertPathValidatorException: signature check failed > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HIVE-19744) In Beeline if -u is specified the default connection should not be tried at all
[ https://issues.apache.org/jira/browse/HIVE-19744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16507216#comment-16507216 ] Hive QA commented on HIVE-19744: | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || || || || || {color:brown} Prechecks {color} || | {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s{color} | {color:green} The patch does not contain any @author tags. {color} | || || || || {color:brown} master Compile Tests {color} || | {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 35s{color} | {color:blue} Maven dependency ordering for branch {color} | | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 6m 27s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 50s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 24s{color} | {color:green} master passed {color} | | {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m 28s{color} | {color:blue} beeline in master has 70 extant Findbugs warnings. {color} | | {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m 32s{color} | {color:blue} itests/hive-unit in master has 2 extant Findbugs warnings. {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 30s{color} | {color:green} master passed {color} | || || || || {color:brown} Patch Compile Tests {color} || | {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 8s{color} | {color:blue} Maven dependency ordering for patch {color} | | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m 50s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 49s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 49s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 10s{color} | {color:green} beeline: The patch generated 0 new + 46 unchanged - 1 fixed = 46 total (was 47) {color} | | {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 0m 13s{color} | {color:red} itests/hive-unit: The patch generated 9 new + 6 unchanged - 7 fixed = 15 total (was 13) {color} | | {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 0s{color} | {color:green} The patch has no whitespace issues. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 12s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 28s{color} | {color:green} the patch passed {color} | || || || || {color:brown} Other Tests {color} || | {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 11s{color} | {color:green} The patch does not generate ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black} 14m 18s{color} | {color:black} {color} | \\ \\ || Subsystem || Report/Notes || | Optional Tests | asflicense javac javadoc findbugs checkstyle compile | | uname | Linux hiveptest-server-upstream 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux | | Build tool | maven | | Personality | /data/hiveptest/working/yetus_PreCommit-HIVE-Build-11668/dev-support/hive-personality.sh | | git revision | master / 95ea9f5 | | Default Java | 1.8.0_111 | | findbugs | v3.0.0 | | checkstyle | http://104.198.109.242/logs//PreCommit-HIVE-Build-11668/yetus/diff-checkstyle-itests_hive-unit.txt | | modules | C: beeline itests/hive-unit U: . | | Console output | http://104.198.109.242/logs//PreCommit-HIVE-Build-11668/yetus.txt | | Powered by | Apache Yetushttp://yetus.apache.org | This message was automatically generated. > In Beeline if -u is specified the default connection should not be tried at > all > --- > > Key: HIVE-19744 > URL: https://issues.apache.org/jira/browse/HIVE-19744 > Project: Hive > Issue Type: Bug > Components: Beeline >Reporter: Zoltan Haindrich >Assignee: Zoltan Haindrich >Priority: Major > Attachments: HIVE-19744.01.patch > > > I wanted to explicitly connect to a hiveserver by specifying {{-u}} but that > didn't work because it was not running/etc... > The strange thing is that somehow the default connection is activated...and > tried > The possible "hazard" here is that if someone specifies {{-u $MY_DEV_HS2 -f > recreate_db.sql}} to run some sql
[jira] [Commented] (HIVE-19744) In Beeline if -u is specified the default connection should not be tried at all
[ https://issues.apache.org/jira/browse/HIVE-19744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16504632#comment-16504632 ] Zoltan Haindrich commented on HIVE-19744: - cc: [~ashutoshc] > In Beeline if -u is specified the default connection should not be tried at > all > --- > > Key: HIVE-19744 > URL: https://issues.apache.org/jira/browse/HIVE-19744 > Project: Hive > Issue Type: Bug > Components: Beeline >Reporter: Zoltan Haindrich >Priority: Major > > I wanted to explicitly connect to a hiveserver by specifying {{-u}} but that > didn't work because it was not running/etc... > The strange thing is that somehow the default connection is activated...and > tried > The possible "hazard" here is that if someone specifies {{-u $MY_DEV_HS2 -f > recreate_db.sql}} to run some sql script...beeline may connect somewhere else > and run the commands there - which might have serious consequences (in > the above case having default as production might be interesting) > {code} > beeline -u jdbc:hive2://localhost:10502/;transportMode=binary -n hrt_qa > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in > [jar:file:/usr/hdp/3.0.0.0-1406/hive/lib/log4j-slf4j-impl-2.10.0.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in > [jar:file:/usr/hdp/3.0.0.0-1406/hadoop/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an > explanation. > SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory] > Connecting to jdbc:hive2://localhost:10502/ > 18/05/31 07:51:20 [main]: WARN jdbc.HiveConnection: Failed to connect to > localhost:10502 > Unknown HS2 problem when communicating with Thrift server. > Error: Could not open client transport with JDBC Uri: > jdbc:hive2://localhost:10502/: Invalid status 72 (state=08S01,code=0) > Connecting to > jdbc:hive2://ctr-e138-1518143905142-336795-01-16.hwx.site:2181,ctr-e138-1518143905142-336795-01-08.hwx.site:2181,ctr-e138-1518143905142-336795-01-14.hwx.site:2181,ctr-e138-1518143905142-336795-01-09.hwx.site:2181,ctr-e138-1518143905142-336795-01-15.hwx.site:2181/default;httpPath=cliservice;principal=hive/_h...@example.com;serviceDiscoveryMode=zooKeeper;ssl=true;transportMode=http;zooKeeperNamespace=hiveserver2 > 18/05/31 07:51:21 [main]: INFO jdbc.HiveConnection: Connected to > ctr-e138-1518143905142-336795-01-03.hwx.site:10001 > 18/05/31 07:51:21 [main]: ERROR jdbc.HiveConnection: Error opening session > org.apache.thrift.transport.TTransportException: > javax.net.ssl.SSLHandshakeException: > sun.security.validator.ValidatorException: PKIX path validation failed: > java.security.cert.CertPathValidatorException: signature check failed > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HIVE-19744) In Beeline if -u is specified the default connection should not be tried at all
[ https://issues.apache.org/jira/browse/HIVE-19744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16504631#comment-16504631 ] Zoltan Haindrich commented on HIVE-19744: - I've just logged into a different hiveserver than I wanted to because of this > In Beeline if -u is specified the default connection should not be tried at > all > --- > > Key: HIVE-19744 > URL: https://issues.apache.org/jira/browse/HIVE-19744 > Project: Hive > Issue Type: Bug > Components: Beeline >Reporter: Zoltan Haindrich >Priority: Major > > I wanted to explicitly connect to a hiveserver by specifying {{-u}} but that > didn't work because it was not running/etc... > The strange thing is that somehow the default connection is activated...and > tried > The possible "hazard" here is that if someone specifies {{-u $MY_DEV_HS2 -f > recreate_db.sql}} to run some sql script...beeline may connect somewhere else > and run the commands there - which might have serious consequences (in > the above case having default as production might be interesting) > {code} > beeline -u jdbc:hive2://localhost:10502/;transportMode=binary -n hrt_qa > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in > [jar:file:/usr/hdp/3.0.0.0-1406/hive/lib/log4j-slf4j-impl-2.10.0.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in > [jar:file:/usr/hdp/3.0.0.0-1406/hadoop/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an > explanation. > SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory] > Connecting to jdbc:hive2://localhost:10502/ > 18/05/31 07:51:20 [main]: WARN jdbc.HiveConnection: Failed to connect to > localhost:10502 > Unknown HS2 problem when communicating with Thrift server. > Error: Could not open client transport with JDBC Uri: > jdbc:hive2://localhost:10502/: Invalid status 72 (state=08S01,code=0) > Connecting to > jdbc:hive2://ctr-e138-1518143905142-336795-01-16.hwx.site:2181,ctr-e138-1518143905142-336795-01-08.hwx.site:2181,ctr-e138-1518143905142-336795-01-14.hwx.site:2181,ctr-e138-1518143905142-336795-01-09.hwx.site:2181,ctr-e138-1518143905142-336795-01-15.hwx.site:2181/default;httpPath=cliservice;principal=hive/_h...@example.com;serviceDiscoveryMode=zooKeeper;ssl=true;transportMode=http;zooKeeperNamespace=hiveserver2 > 18/05/31 07:51:21 [main]: INFO jdbc.HiveConnection: Connected to > ctr-e138-1518143905142-336795-01-03.hwx.site:10001 > 18/05/31 07:51:21 [main]: ERROR jdbc.HiveConnection: Error opening session > org.apache.thrift.transport.TTransportException: > javax.net.ssl.SSLHandshakeException: > sun.security.validator.ValidatorException: PKIX path validation failed: > java.security.cert.CertPathValidatorException: signature check failed > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)