此内容没有您所选择的语言版本。

13.2. Planning Overview


When the query engine receives an incoming SQL query it performs the following operations.
  1. Parsing - syntax is validated and converted to internal form.
  2. Resolving - all identifiers are linked to metadata, and functions are linked to the function library.
  3. Validating - SQL semantics are validated based on metadata references and type signatures.
  4. Rewriting - SQL is rewritten to simplify expressions and criteria.
  5. Logical plan optimization - the rewritten canonical SQL is converted into a logical plan for in-depth optimization. The JBoss Data Virtualization optimizer is predominantly rule-based. Based upon the query structure and hints, a certain rule set will be applied. These rules may in turn trigger the execution of more rules. Within several rules, JBoss Data Virtualization also takes advantage of costing information. The logical plan optimization steps can be seen by using the SHOWPLAN DEBUG clause and are described in Section 13.9.1, “Query Planner”.
  6. Processing plan conversion - the logic plan is converted into an executable form where the nodes are representative of basic processing operations. The final processing plan is displayed as the query plan. See Section 13.8.1, “Query Plans”.
The logical query plan is a tree of operations used to transform data in source tables to the expected result set. In the tree, data flows from the bottom (tables) to the top (output).
The primary logical operations and their SQL equivalents are:
  • select - select or filter rows based on a criteria,
  • project - project or compute column values,
  • join,
  • source - retrieve data from a table,
  • sort - ORDER BY,
  • duplicate removal - SELECT DISTINCT,
  • group - GROUP BY, and
  • union - UNION.
返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2025 Red Hat