...
As of Hive 2.1 via
| Jira |
|---|
| server | ASF JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 5aa69414-a9e9-3523-82ec-879b028fb15b |
|---|
| key | HIVE-13670 |
|---|
|
, Beeline now also supports named url connect strings via usage of environment variables. If you try to do a
\"!connect
" to a name that does not look like a URL, then beeline will attempt to see if there is an env variable called BEELINE_URL_<name>. For instance, if you specify "!connect blue", it will look for BEELINE_URL_BLUE, and use that to connect. This should make it easier for sysadmins to specify env variables for users, and users need not type in the full URL each time to connect.
...
Traditionally, "!reconnect" has worked to refresh a connection that has already been established. It is not able to do a fresh connect after \"!close" has been run. As of Hive 2.1 via
| Jira |
|---|
| server | ASF JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 5aa69414-a9e9-3523-82ec-879b028fb15b |
|---|
| key | HIVE-13670 |
|---|
|
, Beeline remembers the last successful connected-to url in a session, and is able to reconnect even after
a \a "!close
" has been run. In addition, if a user does a
\"!save
", then this is saved in the beeline.properties file, which then allows
\"!reconnect
" to connect to this saved last-connected-to url across multiple beeline sessions. In addition, this then opens up a possible use of "beeline -r" from the commandline to do a
" reconnect on startup
".
Using JDBC
You can use JDBC to access data stored in a relational database or other tabular format.
...