# Specifying Your Query Engine

You can specify the query engine for Treasure Data. This setting specifies the query engine to be selected for queries in the TD Console. Your choices are:

* [*Presto*](https://api-docs.treasuredata.com/en/tools/presto/quickstart/#how-presto-works) for ad hoc and shorter batch workloads. Presto provides low-latency SQL access to the data set.
* [*Hive*](https://api-docs.treasuredata.com/en/tools/hive/quickstart/#about-the-hive-engine) for large or complex batch workloads. Hive is a MapReduce-based SQL engine. This engine is really powerful when you do large data processing and heavy JOINs. Often used for ETL or sessionization.


# About Hive Version Features

| Hive 0.13 | Hive 2019.1 (Hive 2) | Hive 2020.1 (Hive 2) | Hive 2023.1 (Hive 4) |
|  --- | --- | --- | --- |
| It runs on the MapReduce processing framework.It contains features and fixes back ported from more recent versions of Hive.It uses HiveQL, a non-ANSI compliant SQL like language.It supports many UDFs unique to TD. | It is based on Hive 2.3.2 and laterIt is fully ANSI-compliant SQLIt runs on the MapReduce processing frameworkIt supports the same UDFs used for TD in Hive 0.13This version is being discontinued in favor of 2020.1. | It is based on Hive 2.3.2 and laterIt is fully ANSI-compliant SQLIt runs on the Tez processing frameworkIt supports the same UDFs used for TD in Hive 0.13 | Enhanced performanceNew Hive capabilities |


* [Manually Specifying the Query Engine in TD Console](/products/customer-data-platform/data-workbench/queries/specifying-the-query-engine-for-a-specific-query)
* [Specifying the Account-Wide Query Engine](/products/control-panel/specifying-the-account-wide-query-engine)