Help Center/ MapReduce Service/ Developer Guide (Normal_3.x)/ Impala Development Guide (Security Mode)/ Application Commissioning/ Commissioning an Impala JDBC Application on Windows
Updated on 2025-10-23 GMT+08:00
View PDF

Commissioning an Impala JDBC Application on Windows

  1. Run the sample project.

    After importing and modifying the sample, right-click JDBCExample.java in the development environment and choose Run 'JDBCExample.main()' to run the corresponding application project.

    You can use either of the following method to access an MRS cluster to operate Impala on Windows.

    Method 1: Apply for a Windows ECS to access the MRS cluster to operate Impala. Run the sample code after the development environment is installed.

    1. On the Active Clusters page, click the name of an existing cluster.

      On the cluster details page, record the AZ and VPC of the cluster, as well as the default security group of the Master node.

    2. On the ECS console, create an ECS.

      The AZ, VPC, and security group of the ECS must be the same as those of the cluster to be accessed.

      Select a public Windows image.

      For details about other parameters, see Purchasing an ECS in Custom Config Mode.

    Method 2: Use the local host to access the MRS cluster to operate Impala. After installing the development environment and completing the following steps, run the sample code.

    1. Bind an EIP address to any Core node. Then, configure the IP address in the impala-server configuration item in the client.properties file of the development sample to access the Impala service and submit SQL statements.
      1. Assign an EIP on the EIP page and bind the EIP to any Core node in the cluster. For details, see Assigning an EIP.
      2. Configure security group rules for the MRS cluster. Add security group rules to the security groups of Master and Core nodes in the cluster so that the ECS can access the cluster. For details, see Configuring Security Group Rules.
    2. Change the IP addresses of the kdc, admin_server, and kpasswd_server parameters in the krb5.conf file of the imported sample to the related EIPs of the KrbServer service. (The Kerberos service is deployed on the Master node by default. The EIP of the Master node is used here.)

    The client.properties configuration in the sample is as follows:

    auth = KERBEROS    ##Kerberos mode
principal = impala/node-ana-corexphm@10530B19_8446_4846_97BD_87880A2535DF.COM  ##Principal used by the Impalad instance to be connected
impala-server = XX.XX.XX.XX:21050   ##Specifies the service address bound to the Core node where the Impalad instance to be connected is located. If method 2 is used, enter the EIP bound in step 1.

  2. View the execution result.

    View the Impala SQL query results in the sample code. If the following information is displayed, the execution is successful.

    Result:

    Create table success!
_c0
0
Delete table success!