You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by tw...@apache.org on 2021/02/26 11:56:52 UTC

[flink] 02/02: [hotfix][docs] Fix computed columns documentation

This is an automated email from the ASF dual-hosted git repository.

twalthr pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/flink.git

commit ebde3abd3357b1489b219fe3269048c1f4ec41b7
Author: Timo Walther <tw...@apache.org>
AuthorDate: Thu Feb 25 18:28:24 2021 +0100

    [hotfix][docs] Fix computed columns documentation
---
 docs/content.zh/docs/dev/table/sql/create.md | 6 +++---
 docs/content/docs/dev/table/sql/create.md    | 6 +++---
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/content.zh/docs/dev/table/sql/create.md b/docs/content.zh/docs/dev/table/sql/create.md
index 5426ae1..0101285 100644
--- a/docs/content.zh/docs/dev/table/sql/create.md
+++ b/docs/content.zh/docs/dev/table/sql/create.md
@@ -304,9 +304,9 @@ MyTable(`timestamp` BIGINT, `user_id` BIGINT, `name` STRING)
 Computed columns are virtual columns that are generated using the syntax `column_name AS computed_column_expression`.
 
 A computed column evaluates an expression that can reference other columns declared in the same table.
-Both physical columns and metadata columns can be accessed if they preceed the computed column in the
-schema declaration. The column itself is not physically stored within the table. The column's data type
-is derived automatically from the given expression and does not have to be declared manually.
+Both physical columns and metadata columns can be accessed. The column itself is not physically stored
+within the table. The column's data type is derived automatically from the given expression and does
+not have to be declared manually.
 
 The planner will transform computed columns into a regular projection after the source. For optimization
 or [watermark strategy push down]({{< ref "docs/dev/table/sourcesSinks" >}}), the evaluation might be spread
diff --git a/docs/content/docs/dev/table/sql/create.md b/docs/content/docs/dev/table/sql/create.md
index 4bc822e..0e7e2e9 100644
--- a/docs/content/docs/dev/table/sql/create.md
+++ b/docs/content/docs/dev/table/sql/create.md
@@ -304,9 +304,9 @@ MyTable(`timestamp` BIGINT, `user_id` BIGINT, `name` STRING)
 Computed columns are virtual columns that are generated using the syntax `column_name AS computed_column_expression`.
 
 A computed column evaluates an expression that can reference other columns declared in the same table.
-Both physical columns and metadata columns can be accessed if they preceed the computed column in the
-schema declaration. The column itself is not physically stored within the table. The column's data type
-is derived automatically from the given expression and does not have to be declared manually.
+Both physical columns and metadata columns can be accessed. The column itself is not physically stored
+within the table. The column's data type is derived automatically from the given expression and does
+not have to be declared manually.
 
 The planner will transform computed columns into a regular projection after the source. For optimization
 or [watermark strategy push down]({{< ref "docs/dev/table/sourcesSinks" >}}), the evaluation might be spread