commit | df45194268ffb10f9f7aae0ab4e3aec35a7b31d8 | [log] [tgz] |
---|---|---|
author | Taraka Rama Rao Lethavadla <tarakaramarao.lethavadla@gmail.com> | Tue Nov 07 19:06:27 2023 +0530 |
committer | Stamatis Zampetakis <zabetak@gmail.com> | Tue Mar 19 10:53:52 2024 +0100 |
tree | 03356cd77acfd1a7666a20c1cb0b8fbd2d0fc107 | |
parent | cf49f0eaeadd297e444fe6da42849c1e39bb869d [diff] |
HIVE-27848: Refactor Initiator hierarchy into CompactorUtil and fix failure in TestCrudCompactorOnTez (Taraka Rama Rao Lethavadla reviewed by Stamatis Zampetakis) The work started initially to fix the TestCrudCompactorOnTez.secondCompactionShouldBeRefusedBeforeEnqueueing. However, while changing the code to address the failure, the inheritance based design for the Initator that was chosen in HIVE-27598 revealed some weaknesses briefly outlined below. Due to inheritance the InitiatorBase class becomes a Thread something that doesn't really make sense and it comes with additional overhead every time we instantiate it. Moreover, the only class that currently extends InitiatorBase is the Initiator and it's difficult to imagine how we can make other extensions from InitiatorBase; the code becomes complex and any subtle change in InitiatorBase may have unpredictable effects on Initiator. Having a "Base" class that is not really meant to be extended and no instructions on how to do so is problematic. For the reasons above the focus of the work changed from just re-enabling the test to improving and addressing the shortcomings of the inheritance based design of Initiator. Close apache/hive#4859
The Apache Hive (TM) data warehouse software facilitates reading, writing, and managing large datasets residing in distributed storage using SQL. Built on top of Apache Hadoop (TM), it provides:
Tools to enable easy access to data via SQL, thus enabling data warehousing tasks such as extract/transform/load (ETL), reporting, and data analysis
A mechanism to impose structure on a variety of data formats
Access to files stored either directly in Apache HDFS (TM) or in other data storage systems such as Apache HBase (TM)
Query execution using Apache Hadoop MapReduce or Apache Tez frameworks.
Hive provides standard SQL functionality, including many of the later 2003 and 2011 features for analytics. These include OLAP functions, subqueries, common table expressions, and more. Hive's SQL can also be extended with user code via user defined functions (UDFs), user defined aggregates (UDAFs), and user defined table functions (UDTFs).
Hive users can choose between Apache Hadoop MapReduce or Apache Tez frameworks as their execution backend. Note that MapReduce framework has been deprecated since Hive 2, and Apache Tez is recommended. MapReduce is a mature framework that is proven at large scales. However, MapReduce is a purely batch framework, and queries using it may experience higher latencies (tens of seconds), even over small datasets. Apache Tez is designed for interactive query, and has substantially reduced overheads versus MapReduce.
Users are free to switch back and forth between these frameworks at any time. In each case, Hive is best suited for use cases where the amount of data processed is large enough to require a distributed system.
Hive is not designed for online transaction processing. It is best used for traditional data warehousing tasks. Hive is designed to maximize scalability (scale out with more machines added dynamically to the Hadoop cluster), performance, extensibility, fault-tolerance, and loose-coupling with its input formats.
For the latest information about Hive, please visit out website at:
Installation Instructions and a quick tutorial: https://cwiki.apache.org/confluence/display/Hive/GettingStarted
Instructions to build Hive from source: https://cwiki.apache.org/confluence/display/Hive/GettingStarted#GettingStarted-BuildingHivefromSource
A longer tutorial that covers more features of HiveQL: https://cwiki.apache.org/confluence/display/Hive/Tutorial
The HiveQL Language Manual: https://cwiki.apache.org/confluence/display/Hive/LanguageManual
Hive Version | Java Version |
---|---|
Hive 1.0 | Java 6 |
Hive 1.1 | Java 6 |
Hive 1.2 | Java 7 |
Hive 2.x | Java 7 |
Hive 3.x | Java 8 |
Hive 4.x | Java 8 |
Hive includes changes to the MetaStore schema. If you are upgrading from an earlier version of Hive it is imperative that you upgrade the MetaStore schema by running the appropriate schema upgrade scripts located in the scripts/metastore/upgrade directory.
We have provided upgrade scripts for MySQL, PostgreSQL, Oracle, Microsoft SQL Server, and Derby databases. If you are using a different database for your MetaStore you will need to provide your own upgrade script.
user@hive.apache.org - To discuss and ask usage questions. Send an empty email to user-subscribe@hive.apache.org in order to subscribe to this mailing list.
dev@hive.apache.org - For discussions about code, design and features. Send an empty email to dev-subscribe@hive.apache.org in order to subscribe to this mailing list.
commits@hive.apache.org - In order to monitor commits to the source repository. Send an empty email to commits-subscribe@hive.apache.org in order to subscribe to this mailing list.