[
https://issues.apache.org/jira/browse/HIVE-19744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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-000016.hwx.site:2181,ctr-e138-1518143905142-336795-01-000008.hwx.site:2181,ctr-e138-1518143905142-336795-01-000014.hwx.site:2181,ctr-e138-1518143905142-336795-01-000009.hwx.site:2181,ctr-e138-1518143905142-336795-01-000015.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-000003.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)
