This is an automated email from the ASF dual-hosted git repository.
luoc pushed a commit to branch gh-pages
in repository https://gitbox.apache.org/repos/asf/drill.git
The following commit(s) were added to refs/heads/gh-pages by this push:
new af902d3 Rename Optiq framework to Calcite
af902d3 is described below
commit af902d3e3640c742b6413aec286eeefa9e07a4de
Author: Rymar Maksym <[email protected]>
AuthorDate: Fri Apr 30 15:10:11 2021 +0300
Rename Optiq framework to Calcite
---
architecture.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/architecture.html b/architecture.html
index 0f51006..963d8b6 100644
--- a/architecture.html
+++ b/architecture.html
@@ -32,7 +32,7 @@ description: Apache Drill is a low latency distributed query
engine for large-sc
<img src="{{ site.baseurl }}/images/arc-2.jpg" alt="Drillbit components"
width="525">
<p>• RPC end point: Drill exposes a low overhead protobuf-based RPC protocol
to communicate with the clients. Additionally, a C++ and Java API layers are
also available for the client applications to interact with Drill. Clients can
communicate to a specific Drillbit directly or go through a ZooKeeper quorum to
discover the available Drillbits before submitting queries. It is recommended
that the clients always go through ZooKeeper to shield clients from the
intricacies of cluster mana [...]
- <p>• SQL parser: Drill uses Optiq, the open source framework, to parse
incoming queries. The output of the parser component is a language agnostic,
computer-friendly logical plan that represents the query.</p>
+ <p>• SQL parser: Drill uses Calcite, the open source framework, to parse
incoming queries. The output of the parser component is a language agnostic,
computer-friendly logical plan that represents the query.</p>
<p>• Optimizer: Drill uses various standard database optimizations such as
rule based/cost based, as well as data locality and other optimization rules
exposed by the storage engine to re-write and split the query. The output of
the optimizer is a distributed physical query plan that represents the most
efficient and fastest way to execute the query across different nodes in the
cluster.</p>
<p>• Execution engine: Drill provides a MPP execution engine built to
perform distributed query processing across the various nodes in the cluster.
</p>
<p>• Storage plugin interfaces: Drill serves as a query layer on top of
several data sources. Storage plugins in Drill represent the abstractions that
Drill uses to interact with the data sources. Storage plugins provide Drill
with the following information:</p>
