configuration
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
configuration [2017/09/04 18:09] dmtolpeko [hplsql.conn.default] |
configuration [2017/09/04 18:20] dmtolpeko [hplsql.conn.convert.hiveconn] |
||
|---|---|---|---|
| Line 36: | Line 36: | ||
| Version: HPL/SQL 0.1 | Version: HPL/SQL 0.1 | ||
| + | |||
| + | ===== hplsql.conn.hive2conn ===== | ||
| + | |||
| + | The //hplsql.conn.hive2conn// option specifies the connection profile for HiveServer2 JDBC: | ||
| + | |||
| + | <HTML> | ||
| + | <property> | ||
| + | <name>hplsql.conn.hive2conn</name> | ||
| + | <value>org.apache.hive.jdbc.HiveDriver;jdbc:hive2://localhost:10000;user;pwd</value> | ||
| + | </property> | ||
| + | </HTML> | ||
| + | |||
| + | You can use this profile when you run HPL/SQL tool on a remote host. | ||
| + | |||
| + | Version: HPL/SQL 0.3.1 | ||
| + | |||
| + | ===== hplsql.conn.init.hive2conn ===== | ||
| + | |||
| + | The //hplsql.conn.init.hive2conn// option defines SQL statements to execute after establishing a connection to the [[configuration#hplsqlconnhive2conn|hive2conn]] profile. You can use this option to specify job queue, execution engines in Hive etc. | ||
| + | |||
| + | For example: | ||
| + | |||
| + | <HTML> | ||
| + | <property> | ||
| + | <name>hplsql.conn.init.hiveconn2</name> | ||
| + | <value> | ||
| + | set mapred.job.queue.name=dev; | ||
| + | set hive.execution.engine=mr; | ||
| + | use sales_db; | ||
| + | </value> | ||
| + | </property> | ||
| + | </HTML> | ||
| + | |||
| + | Version: HPL/SQL 0.3.1 | ||
| + | |||
| + | ===== hplsql.conn.convert.hive2conn ===== | ||
| + | |||
| + | The //hplsql.conn.convert.hive2conn// option defines whether on-the-fly SQL conversion is enabled for the [[configuration#hplsqlconnhiveconn|hive2conn]] profile. The default value is //true//. | ||
| + | |||
| + | For example: | ||
| + | |||
| + | <HTML> | ||
| + | <property> | ||
| + | <name>hplsql.conn.convert.hive2conn</name> | ||
| + | <value>true</value> | ||
| + | </property> | ||
| + | </HTML> | ||
| + | |||
| + | Version: HPL/SQL 0.3.1 | ||
| ===== hplsql.conn.hiveconn ===== | ===== hplsql.conn.hiveconn ===== | ||
| - | The //hplsql.conn.hiveconn// option specifies the connection profile for Hive embedded JDBC connection (not requiring a HiveServer): | + | The //hplsql.conn.hiveconn// option specifies the connection profile for HiveServer 2 embedded connection (local connection): |
| <HTML> | <HTML> | ||
| <property> | <property> | ||
| <name>hplsql.conn.hiveconn</name> | <name>hplsql.conn.hiveconn</name> | ||
| - | <value>org.apache.hadoop.hive.jdbc.HiveDriver;jdbc:hive://</value> | + | <value>org.apache.hive.jdbc.HiveDriver;jdbc:hive2://</value> |
| </property> | </property> | ||
| </HTML> | </HTML> | ||
| - | You can use this profile when you run HPL/SQL tool on a host containing the Hive client (typically, a node of the Hadoop cluster). | + | You can use this profile when you run HPL/SQL tool on a host running the HiveServer2. |
| Version: HPL/SQL 0.3.1 | Version: HPL/SQL 0.3.1 | ||
| Line 86: | Line 135: | ||
| Version: HPL/SQL 0.3.1 | Version: HPL/SQL 0.3.1 | ||
| - | ===== hplsql.conn.hive2conn ===== | + | ===== hplsql.conn.hive1conn ===== |
| - | The //hplsql.conn.hive2conn// option specifies the connection profile for HiveServer2 JDBC: | + | The //hplsql.conn.hiveconn// option specifies the connection profile for Hive embedded JDBC connection (not requiring a HiveServer): |
| <HTML> | <HTML> | ||
| <property> | <property> | ||
| - | <name>hplsql.conn.hive2conn</name> | + | <name>hplsql.conn.hiveconn</name> |
| - | <value>org.apache.hive.jdbc.HiveDriver;jdbc:hive2://localhost:10000;user;pwd</value> | + | <value>org.apache.hadoop.hive.jdbc.HiveDriver;jdbc:hive://</value> |
| </property> | </property> | ||
| </HTML> | </HTML> | ||
| - | You can use this profile when you run HPL/SQL tool on a remote host. | + | You can use this profile when you run HPL/SQL tool on a host containing the Hive client (typically, a node of the Hadoop cluster). Note that this connection mode is deprecated. |
| Version: HPL/SQL 0.3.1 | Version: HPL/SQL 0.3.1 | ||
| - | ===== hplsql.conn.init.hive2conn ===== | + | ===== hplsql.conn.init.hive1conn ===== |
| - | The //hplsql.conn.init.hive2conn// option defines SQL statements to execute after establishing a connection to the [[configuration#hplsqlconnhive2conn|hive2conn]] profile. You can use this option to specify job queue, execution engines in Hive etc. | + | The //hplsql.conn.init.hive1conn// option defines SQL statements to execute after establishing a connection to the [[configuration#hplsqlconnhive1conn|hive1conn]] profile. You can use this option to specify job queue, execution engines in Hive etc. |
| For example: | For example: | ||
| Line 109: | Line 158: | ||
| <HTML> | <HTML> | ||
| <property> | <property> | ||
| - | <name>hplsql.conn.init.hiveconn2</name> | + | <name>hplsql.conn.init.hive1conn</name> |
| <value> | <value> | ||
| set mapred.job.queue.name=dev; | set mapred.job.queue.name=dev; | ||
| Line 120: | Line 169: | ||
| Version: HPL/SQL 0.3.1 | Version: HPL/SQL 0.3.1 | ||
| - | ===== hplsql.conn.convert.hive2conn ===== | + | ===== hplsql.conn.convert.hive1conn ===== |
| - | The //hplsql.conn.convert.hive2conn// option defines whether on-the-fly SQL conversion is enabled for the [[configuration#hplsqlconnhiveconn|hive2conn]] profile. The default value is //true//. | + | The //hplsql.conn.convert.hive1conn// option defines whether on-the-fly SQL conversion is enabled for the [[configuration#hplsqlconnhive1conn|hiveconn]] profile. The default value is //true//. |
| For example: | For example: | ||
| Line 128: | Line 177: | ||
| <HTML> | <HTML> | ||
| <property> | <property> | ||
| - | <name>hplsql.conn.convert.hive2conn</name> | + | <name>hplsql.conn.convert.hive1conn</name> |
| <value>true</value> | <value>true</value> | ||
| </property> | </property> | ||
Page Tools
