Run Hive queries using the Data Lake tools for Visual Studio
Learn how to use the Data Lake tools for Visual Studio to query Apache Hive. The Data Lake tools allow you to easily create, submit, and monitor Hive queries to Hadoop on Azure HDInsight.
An Azure HDInsight (Hadoop on HDInsight) cluster
Linux is the only operating system used on HDInsight version 3.4 or greater. For more information, see HDInsight retirement on Windows.
Visual Studio (one of the following versions):
Visual Studio 2013 Community/Professional/Premium/Ultimate with Update 4
Visual Studio 2015 (any edition)
Visual Studio 2017 (any edition)
HDInsight tools for Visual Studio or Azure Data Lake tools for Visual Studio. See Get started using Visual Studio Hadoop tools for HDInsight for information on installing and configuring the tools.
Run Hive queries using the Visual Studio
Open Visual Studio and select New > Project > Azure Data Lake > HIVE > Hive Application. Provide a name for this project.
Open the Script.hql file that is created with this project, and paste in 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 '/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: If the table exists, this statement deletes it.
CREATE EXTERNAL TABLE: Creates a new 'external' table in Hive. External tables only store 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. For example, a MapReduce job or Azure service.
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 that the data is stored in the example/data directory, and that it is stored as text.
SELECT: Select a count of all rows where column
t4contains the value
[ERROR]. This statement returns a value of
3because 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 clause restricts the search to the sample.log file that contains the data.
From the toolbar, select the HDInsight Cluster that you want to use for this query. Select Submit to run the statements as a Hive job.
The Hive Job Summary appears and displays information about the running job. Use the Refresh link to refresh the job information, until the Job Status changes to Completed.
Use the Job Output link to view the output of this job. It displays
[ERROR] 3, which is the value returned by this query.
You can also run Hive queries without creating a project. Using Server Explorer, expand Azure > HDInsight, right-click your HDInsight server, and then select Write a Hive Query.
In the temp.hql document that appears, add the following HiveQL statements:
set hive.execution.engine=tez; CREATE TABLE IF NOT EXISTS errorLogs (t1 string, t2 string, t3 string, t4 string, t5 string, t6 string, t7 string) STORED AS ORC; INSERT OVERWRITE TABLE errorLogs SELECT t1, t2, t3, t4, t5, t6, t7 FROM log4jLogs WHERE t4 = '[ERROR]' AND INPUT__FILE__NAME LIKE '%.log';
These statements perform the following actions:
CREATE TABLE IF NOT EXISTS: Creates a table if it does not already exist. Because the
EXTERNALkeyword is not used, this statement creates an internal table. Internal tables are stored in the Hive data warehouse and are managed by Hive.
EXTERNALtables, dropping an internal table also deletes the underlying data.
STORED AS ORC: Stores the data in optimized row columnar (ORC) format. ORC is a highly optimized and efficient format for storing Hive data.
INSERT OVERWRITE ... SELECT: Selects rows from the
log4jLogstable that contain
[ERROR], then inserts the data into the
From the toolbar, select Submit to run the job. Use the Job Status to determine that the job has completed successfully.
To verify that the job created the table, use Server Explorer and expand Azure > HDInsight > your HDInsight cluster > Hive Databases > default. The errorLogs table and the log4jLogs table are listed.
As you can see, the HDInsight tools for Visual Studio provide an easy way to work with Hive queries on HDInsight.
For general information about Hive in HDInsight:
For information about other ways you can work with Hadoop on HDInsight:
For more information about the HDInsight tools for Visual Studio: