In this article, you will learn how to use the HDInsight Query Console to run Hive queries on an HDInsight Hadoop cluster from your browser.
The HDInsight Query Console is only available on Windows-based HDInsight clusters. Linux is the only operating system used on HDInsight version 3.4 or greater. For more information, see HDInsight retirement on Windows.
For HDInsight 3.4 or greater, see Run Hive queries in Ambari Hive View for information on running Hive queries from a web browser.
To complete the steps in this article, you will need the following.
- A Windows-based HDInsight Hadoop cluster
- A modern web browser
- Open a web browser and navigate to https://CLUSTERNAME.azurehdinsight.net, where CLUSTERNAME is the name of your HDInsight cluster. If prompted, enter the user name and password that you used when you created the cluster.
From the links at the top of the page, select Hive Editor. This displays a form that can be used to enter the HiveQL statements that you want to run in the HDInsight cluster.
Replace the text
Select * from hivesampletablewith the following HiveQL statements:
set hive.execution.engine=tez; DROP TABLE log4jLogs; CREATE EXTERNAL TABLE log4jLogs (t1 string, t2 string, t3 string, t4 string, t5 string, t6 string, t7 string) ROW FORMAT DELIMITED FIELDS TERMINATED BY ' ' STORED AS TEXTFILE LOCATION 'wasbs:///example/data/'; SELECT t4 AS sev, COUNT(*) AS count FROM log4jLogs WHERE t4 = '[ERROR]' AND INPUT__FILE__NAME LIKE '%.log' GROUP BY t4;
These statements perform the following actions:
- DROP TABLE: Deletes the table and the data file if the table already exists.
CREATE EXTERNAL TABLE: Creates a new 'external' table in Hive. External tables store only the table definition in Hive; the data is left in the original location.
External tables should be used when you expect the underlying data to be updated by an external source (such as an automated data upload process) or by another MapReduce operation, but you always want Hive queries to use the latest data.
Dropping an external table does not delete the data, only the table definition.
- ROW FORMAT: Tells Hive how the data is formatted. In this case, the fields in each log are separated by a space.
- STORED AS TEXTFILE LOCATION: Tells Hive where the data is stored (the example/data directory) and that it is stored as text
- SELECT: Select a count of all rows where column t4 contain the value [ERROR]. This should return a value of 3 because there are three rows that contain this value.
- INPUT__FILE__NAME LIKE '%.log' - Tells Hive that we should only return data from files ending in .log. This restricts the search to the sample.log file that contains the data, and keeps it from returning data from other example data files that do not match the schema we defined.
- Click Submit. The Job Session at the bottom of the page should display details for the job.
- When the Status field changes to Completed, select View Details for the job. On the details page, the Job Output contains
[ERROR] 3. You can use the Download button under this field to download a file that contains the output of the job.
As you can see, the Query Console provides an easy way to run Hive queries in an HDInsight cluster, monitor the job status, and retrieve the output.
To learn more about using Hive Query Console to run Hive jobs, select Getting Started at the top of the Query Console, then use the samples that are provided. Each sample walks through the process of using Hive to analyze data, including explanations about the HiveQL statements used in the sample.
For general information about Hive in HDInsight:
For information about other ways you can work with Hadoop on HDInsight:
If you are using Tez with Hive, see the following documents for debugging information: