Username and Password Authentication Using HSBroker
Description
This section describes how to use HSBroker to connect to HetuEngine with the username and password, and assemble and send the SQL statements to HetuEngine for execution.
public class JDBCExampleBroker { private static Properties properties = new Properties(); private static void init() throws ClassNotFoundException { properties.setProperty("user", "YourUserName"); properties.setProperty("password", "YourPassword"); Class.forName("io.prestosql.jdbc.PrestoDriver"); } public static void main(String[] args){ Connection connection = null; ResultSet resultSet = null; PreparedStatement statement = null; String url = "jdbc:presto://192.168.1.130:29860,192.168.1.131:29860/hive/default?serviceDiscoveryMode=hsbroker"; try { init(); String sql = "show tables"; connection = DriverManager.getConnection(url, properties); statement = connection.prepareStatement(sql.trim()); resultSet = statement.executeQuery(); Integer colNum = resultSet.getMetaData().getColumnCount(); while (resultSet.next()) { for (int i = 1; i <= colNum; i++) { System.out.println(resultSet.getString(i) + "\t"); } } } catch (SQLException | ClassNotFoundException e) { e.printStackTrace(); } finally { if (resultSet != null) { try { resultSet.close(); } catch (SQLException e) { e.printStackTrace(); } } if (statement != null) { try { statement.close(); } catch (SQLException e) { e.printStackTrace(); } } if (connection != null) { try { connection.close(); } catch (SQLException e) { e.printStackTrace(); } } } } }
Table 1 describes the parameters in the preceding code.
Parameter |
Description |
---|---|
url |
jdbc:presto://HSBroker1_IP:HSBroker1_Port,HSBroker2_IP:HSBroker2_Port,HSBroker3_IP:HSBroker3_Port/catalog/schema?serviceDiscoveryMode=hsbroker
NOTE:
|
user |
Username for accessing HetuEngine, that is, the username of the human-machine user created in the cluster. |
password |
Password of the human-machine user created in the cluster. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.