(flink) 01/01: [hotfix][docs] In match_recognize docs, remove extracting time attributes from list of limitations

[danderson]

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

danderson pushed a commit to branch danderson-hotfix-mr-docs
in repository https://gitbox.apache.org/repos/asf/flink.git

commit f6f062d61afa6d9b1a388336305bb456ab949ece
Author: David Anderson <da...@alpinegizmo.com>
AuthorDate: Wed Jan 1 14:11:06 2025 -0500

    [hotfix][docs] In match_recognize docs, remove extracting time attributes 
from list of limitations
---
 docs/content.zh/docs/dev/table/sql/queries/match_recognize.md | 1 -
 docs/content/docs/dev/table/sql/queries/match_recognize.md    | 2 --
 2 files changed, 3 deletions(-)

diff --git a/docs/content.zh/docs/dev/table/sql/queries/match_recognize.md 
b/docs/content.zh/docs/dev/table/sql/queries/match_recognize.md
index 9f3e15b0edd..29c78b4a4a3 100644
--- a/docs/content.zh/docs/dev/table/sql/queries/match_recognize.md
+++ b/docs/content.zh/docs/dev/table/sql/queries/match_recognize.md
@@ -1002,7 +1002,6 @@ Flink 对 `MATCH_RECOGNIZE` 子句实现是一项长期持续的工作，目前
   * `CLASSIFIER` 函数，尚不支持返回行映射到的模式变量。
 * `SUBSET` - 它允许创建模式变量的逻辑组，并在 `DEFINE` 和 `MEASURES` 子句中使用这些组。
 * Physical offsets - `PREV/NEXT`，它为所有可见事件建立索引，而不是仅将那些映射到模式变量的事件编入索引（如 [logical 
offsets](#logical-offsets) 的情况）。
-* 提取时间属性 - 目前无法为后续基于时间的操作提取时间属性。
 * `MATCH_RECOGNIZE` 仅 SQL 支持。Table API 中没有等效项。
 * Aggregations:
   * 不支持 distinct aggregations。
diff --git a/docs/content/docs/dev/table/sql/queries/match_recognize.md 
b/docs/content/docs/dev/table/sql/queries/match_recognize.md
index 5e3ec6c361d..e7267175869 100644
--- a/docs/content/docs/dev/table/sql/queries/match_recognize.md
+++ b/docs/content/docs/dev/table/sql/queries/match_recognize.md
@@ -1126,8 +1126,6 @@ Unsupported features include:
   the `DEFINE` and `MEASURES` clauses.
 * Physical offsets - `PREV/NEXT`, which indexes all events seen rather than 
only those that were
   mapped to a pattern variable (as in [logical offsets](#logical-offsets) 
case).
-* Extracting time attributes - there is currently no possibility to get a time 
attribute for
-  subsequent time-based operations.
 * `MATCH_RECOGNIZE` is supported only for SQL. There is no equivalent in the 
Table API.
 * Aggregations:
   * distinct aggregations are not supported.