In this article, we will explore the topic of Apache Phoenix in depth, analyzing its origins, its relevance today, and its impact on different areas of society. Apache Phoenix has aroused great interest in the public, sparking debates and discussions around its implications and consequences. Through a multidisciplinary approach, we will examine all aspects related to Apache Phoenix, from its history to its possible future developments, with the aim of providing a comprehensive and updated view on this topic that has attracted so much attention in recent years.
![]() | |||||
Developer(s) | Apache Software Foundation | ||||
---|---|---|---|---|---|
Initial release | 15 April 2014 | ||||
Stable release |
| ||||
Repository | Phoenix Repository | ||||
Written in | Java, SQL | ||||
Operating system | Cross-platform | ||||
Type | SQL database | ||||
License | Apache License 2.0 | ||||
Website | phoenix |
Apache Phoenix is an open source, massively parallel, relational database engine supporting OLTP for Hadoop using Apache HBase as its backing store. Phoenix provides a JDBC driver that hides the intricacies of the NoSQL store enabling users to create, delete, and alter SQL tables, views, indexes, and sequences; insert and delete rows singly and in bulk; and query data through SQL.[1] Phoenix compiles queries and other statements into native NoSQL store APIs rather than using MapReduce enabling the building of low latency applications on top of NoSQL stores.[2]
Phoenix began as an internal project by the company salesforce.com out of a need to support a higher level, well understood, SQL language. It was originally open-sourced on GitHub[3] on 28 Jan 2014 and became a top-level Apache project on 22 May 2014.[4] Apache Phoenix is included in the Cloudera Data Platform 7.0 and above,[5] Hortonworks distribution for HDP 2.1 and above,[6] is available as part of Cloudera labs,[7] and is part of the Hadoop ecosystem.[8]