[Feature] Dynamic Table. #725

avamingli · 2024-11-21T07:59:39Z

Dynamic Table is a an auto-refreshing materialized view which could be constructed by base tables, external tables, materialized views and dynamic tables.
And it could be used to answer query by AQUMV.
As normal tables in CBDB, dynamic tables could also have distribution keys.

The purpose of Dynamic Tables is to solve the problem often raised by customers who are big fans of a lakehouse architecture: how can we run queries on external tables as fast as internal tables?

See details in discussion #706 and more cases in tests.

Create Dynamic Table:

CREATE DYNAMIC TABLE dt0 SCHEDULE '5 * * * *' AS
  SELECT a, b, sum(c) FROM t1 GROUP BY a, b WITH NO DATA DISTRIBUTED BY(b);
CREATE DYNAMIC TABLE

\d
                 List of relations
 Schema | Name |     Type      |  Owner  | Storage
--------+------+---------------+---------+---------
 public | dt0  | dynamic table | gpadmin | heap
 public | t1   | table         | gpadmin | heap
(2 rows)

CREATE DYNAMIC TABLE xxx AS Query
The Query allows any valid SELECT SQL of Materialized Views: from single or multiple relations, base tables, materialized views, and dynamic tables as well, joins, subquery, aggregation, group by and etc.
However, if you want to use it to Answer Query, that is limited by AQUMV: currently we allow Select from single base table, aggregation on it or aggregation SQL replace directly #705

SCHEDULE:

A string used to schedule background job which auto-refreshes the dynamic table.
We follow the valid string of pg_cron extension which supports linux crontab, refer https://crontab.guru/ .

 ┌───────────── min (0 - 59)
 │ ┌────────────── hour (0 - 23)
 │ │ ┌─────────────── day of month (1 - 31) or last day of the month ($)
 │ │ │ ┌──────────────── month (1 - 12)
 │ │ │ │ ┌───────────────── day of week (0 - 6) (0 to 6 are Sunday to
 │ │ │ │ │                  Saturday, or use names; 7 is also Sunday)
 │ │ │ │ │
 │ │ │ │ │
 * * * * *

You can also use '[1-59] seconds' to schedule a job based on an interval.
The example creates a cron job refreshing the dynamic table at minute 5 of each hour.

User don't need to consider the auto-refresh job, however query on pg_task catalog if we want to see the task:

SELECT * FROM pg_task WHERE jobname LIKE 'gp_dynamic_table_refresh%' AND command LIKE '%dt0';
 jobid | schedule  |             command              | nodename  | nodeport | database | username | active |
   jobname
-------+-----------+----------------------------------+-----------+----------+----------+----------+--------+---------
-----------------------
 17398 | 5 * * * * | REFRESH DYNAMIC TABLE public.dt0 | 127.0.0.1 |     9000 | gpadmin  | gpadmin  | t      | gp_dynam
ic_table_refresh_17394
(1 row)

And a function pg_get_dynamic_table_schedule is provided for users to see the SCHEDULE info easily:

CREATE DYNAMIC TABLE dt_schedule SCHEDULE '1 2 3 4 5' AS SELECT * FROM t2;
SELECT pg_catalog.pg_get_dynamic_table_schedule('dt_schedule'::regclass::oid);
 pg_get_dynamic_table_schedule 
-------------------------------
 1 2 3 4 5
(1 row)

As Snowflake, Dynamic Tables should always have a auto-refresh process.
However, for convenience, I make SCHEDULE optional. If user didn't specific it, a default schedule is provided: maybe at every 5th minute(snowflake limit at most 5 minutes for dynamic table auto-refresh, not sure)?

WITH NO DATA:

Same as Materialized View, will create an empty Dynamic Table if specified.

DISTRIBUTED BY:

Same as normal tables in CBDB, Dynamic Tables could support distribution keys as materialized views.
Use \d+ to see the distribution keys and the Query SQL of Dynamic Tables.

\d+ dt0;
                                       Dynamic table "public.dt0"
 Column |  Type   | Collation | Nullable | Default | Storage | Compression | Stats target | Description
--------+---------+-----------+----------+---------+---------+-------------+--------------+-------------
 a      | integer |           |          |         | plain   |             |              |
 b      | integer |           |          |         | plain   |             |              |
 sum    | bigint  |           |          |         | plain   |             |              |
View definition:
 SELECT t1.a,
    t1.b,
    sum(t1.c) AS sum
   FROM t1
  GROUP BY t1.a, t1.b;
Distributed by: (b)
Access method: heap

Refresh Dynamic Table

As seen in pg_task, we put a command to auto-refresh dynamic tables.
However, if users want to do a REFRESH manually, exec command REFRESH DYNAMIC TABLE is also supported.

REFRESH DYNAMIC TABLE dt0;
REFRESH DYNAMIC TABLE

REFRESH WITH NO DATA;

Same as Materialized Views, Refresh with no data will truncate the Dynamic Table and make it unpopulated status.

REFRESH DYNAMIC TABLE dt0 WITH NO DATA;
REFRESH DYNAMIC TABLE

Drop Dynamic Table:

DROP DYNAMIC TABLE dt0;
DROP DYNAMIC TABLE

Drop a Dynamic Table will drop its scheduler job automatically.

SELECT * FROM pg_task WHERE jobname LIKE 'gp_dynamic_table_refresh%' AND command LIKE '%dt0';
 jobid | schedule | command | nodename | nodeport | database | username | active | jobname
-------+----------+---------+----------+----------+----------+----------+--------+---------
(0 rows)

Privileges

Same as Materialized Views in CBDB:

\z
                                Access privileges
 Schema | Name |     Type      | Access privileges | Column privileges | Policies
--------+------+---------------+-------------------+-------------------+----------
 public | dt1  | dynamic table |                   |                   |
 public | t1   | table         |                   |                   |
(2 rows)

Use Dynamic Tables to answer query

Like Materialized Views, Dynamic Tables could be used to answer query too:

CREATE DYNAMIC TABLE dt1  AS
  SELECT * FROM t1 WHERE a = 1 DISTRIBUTED BY(b);
ANALYZE dt1;
SELECT 2

SET enable_answer_query_using_materialized_views = ON;
EXPLAIN(COSTS OFF, VERBOSE)
SELECT * FROM t1 WHERE a = 1;
SELECT * FROM t1 WHERE a = 1;
SET
                                    QUERY PLAN
----------------------------------------------------------------------------------
 Gather Motion 3:1  (slice1; segments: 3)
   Output: a, b, c
   ->  Seq Scan on public.dt1
         Output: a, b, c
 Settings: enable_answer_query_using_materialized_views = 'on', optimizer = 'off'
 Optimizer: Postgres query optimizer
(6 rows)

 a | b | c
---+---+---
 1 | 2 | 3
 1 | 2 | 3
(2 rows)

Authored-by: Zhang Mingli [email protected]

Fixes #ISSUE_Number

What does this PR do?

Type of Change

Bug fix (non-breaking change)
New feature (non-breaking change)
Breaking change (fix or feature with breaking changes)
Documentation update

Breaking Changes

Test Plan

Unit tests added/updated
Integration tests added/updated
Passed make installcheck
Passed make -C src/test installcheck-cbdb-parallel

Impact

Performance:

User-facing changes:

Dependencies:

Checklist

Followed contribution guide
Added/updated documentation
Reviewed code for security implications
Requested review from cloudberry committers

Additional Context

src/bin/psql/describe.c

reshke · 2024-11-21T10:05:57Z

Hi! some initial review:

Patch miss tab-completion for DYNAMIC feature.

When trying to modify dynamic table

reshke=# insert into td values(1, 1);
ERROR:  cannot change materialized view "td"

Maybe some better error message here? we can check for relisdynamic and provide "cannot directly change dynamic table " with some errdetail, like "DETAIL: DYNAMIC TABLE data is automatically populated from its source query."

Im not sure if this a problem, but example:

reshke=# alter materialized view td rename TO tdd;
ALTER MATERIALIZED VIEW

td here is dynamic table. This all comes from fact that dynamic table relkind is 'm' (mat. view). I'm not entirely sure if this design is good. Although the implementation is undoubtedly simpler in this manner, it is at least perplexing that changing a dynamic table requires M.V. SQL syntax. Another case here:

reshke=# drop dynamic table tdd;
DROP DYNAMIC TABLE
reshke=# drop materialized view tdd ;
DROP MATERIALIZED VIEW

Both succeeds.

Maybe we should create this relation as CREATE DYNAMIC MATERIALIZED VIEW not TABLE? This should fix a lot of SQL ambiguity problems.

In any case, we should add this ALTER pattern to regression tests and have document them in some form.

I will take another look later.

avamingli · 2024-11-21T10:53:06Z

This all comes from fact that dynamic table relkind is 'm' (mat. view). I'm not entirely sure if this design is good. Although the implementation is undoubtedly simpler in this manner, it is at least perplexing that changing a dynamic table requires M.V. SQL syntax. Another case here:
reshke=# drop dynamic table tdd;
DROP DYNAMIC TABLE
reshke=# drop materialized view tdd ;
DROP MATERIALIZED VIEW
Both succeeds.

Yes, it's a materialized view actually.

Dynamic Table is a an auto-refreshing materialized view

Dynamic Table have all operations from Materialized Views, and it must do.
They are same as GPDB's external table and foreign table, if you have a try:

create external table ext1;
drop external table ext1;
drop foreign table ext1;

Both will succeed, external table is actually a foreign table.

We provide gram sugar for that CREATE/DROP, but not all command or all message infos, if users want to use Materialized Views command, that's no problem.

Maybe we should create this relation as CREATE DYNAMIC MATERIALIZED VIEW not TABLE? This should fix a lot of SQL ambiguity problems.

We follow Snowflake, customers want to have Snowflake Dynamic Tables in CBDB, better use the same word.

Please refer to Snowflake https://docs.snowflake.com/en/user-guide/dynamic-tables-intro and our discussion #706 for more details.

avamingli · 2024-11-21T10:54:07Z

In any case, we should add this ALTER pattern to regression tests and have document them in some form.

Request for discuss: #706 (comment)

avamingli · 2024-11-21T11:01:53Z

Patch miss tab-completion for DYNAMIC feature.

Oo, seems you'r big fans of tab-completion. It's ok to add them.
I'm not planing to add this right now, or at least not in this pr.
Maybe someone have interest could help.

avamingli · 2024-11-21T11:18:18Z

Dynamic Table have all operations from Materialized Views, and it must do. They are same as GPDB's external table and foreign table, if you have a try:
create external table ext1;
drop external table ext1;
drop foreign table ext1;
Both will succeed, external table is actually a foreign table.

exmaple:

CREATE READABLE EXTERNAL TABLE ext_r(id int)
    LOCATION('demoprot://dynamic_table_text_file.txt')
FORMAT 'text';
CREATE EXTERNAL TABLE
 \d
                 List of relations
 Schema | Name  |     Type      |  Owner  | Storage
--------+-------+---------------+---------+---------
 public | ext_r | foreign table | gpadmin |
(1 row)

 drop external table ext_r;
DROP FOREIGN TABLE
CREATE READABLE EXTERNAL TABLE ext_r(id int)
    LOCATION('demoprot://dynamic_table_text_file.txt')
FORMAT 'text';
CREATE EXTERNAL TABLE
 \d
                 List of relations
 Schema | Name  |     Type      |  Owner  | Storage
--------+-------+---------------+---------+---------
 public | ext_r | foreign table | gpadmin |
(1 row)

drop foreign table ext_r;
DROP FOREIGN TABLE

In summary, we'r doing the similar thing like external table with foreign table, for dynamic tables and materialized views.
We provide some command for it, and all valid commands on matview should work on dynamic tables too.
I'm not planing to copy lot's of duplicated codes from matview for just several tiny adjustment, that's pointless and the worse is: when postgres have some updated on matview command, we won't catch up and need copy the new changes too.
Since they are actually the same thing, let it be.

reshke · 2024-11-21T11:24:50Z

I'm not planing to copy lot's of duplicated codes from matview

Im not suggesting this, the thing i propose is to change CREATE DYNAMIC TABLE syntax to CREATE DYNAMIC MATERIALIZED VIEW for convenience

my-ship-it · 2024-11-26T03:37:33Z

I'm not planing to copy lot's of duplicated codes from matview

Im not suggesting this, the thing i propose is to change CREATE DYNAMIC TABLE syntax to CREATE DYNAMIC MATERIALIZED VIEW for convenience

How about we keep CREATE DYNAMIC TABLE? Since snowflake has this feature already and we follow the same term?.

avamingli · 2024-11-26T03:51:29Z

Will provide DOC soon.

avamingli · 2024-11-26T08:34:01Z

Will provide DOC soon.

Done, see
doc/src/sgml/ref/create_dynamic_table.sgml,
doc/src/sgml/ref/drop_dynamic_table.sgml,
doc/src/sgml/ref/refresh_dynamic_table.sgml

edespino · 2024-11-26T09:37:48Z

With catalog_change in play, I am assuming we are going to bump the version string to 2.0.0?

avamingli · 2024-11-26T09:50:00Z

With catalog_change in play, I am assuming we are going to bump the version string to 2.0.0?

Woo..that will make CBDB version grow up quickly, as we have lot's of codes to be open source with catalog changes.
In fact, we guarantee catalog no changed in patch versions in commercial ones.

Ask @my-ship-it for help about this topic, that should be another discussion outside of this PR.

When developers develop codes, they don't need to consider what the version should be, a catalog_change label is necessary if there was. That will help release team to decide version numbers and don't need to sync with authors which PR changed the catalog.

my-ship-it · 2024-11-26T09:51:24Z

With catalog_change in play, I am assuming we are going to bump the version string to 2.0.0?

Yes, it is.

my-ship-it · 2024-11-26T11:03:31Z

When mirror is promoted, should we launch auto task for Dynamic Table?

src/backend/commands/matview.c

my-ship-it

LGTM

avamingli · 2024-11-27T04:02:49Z

When mirror is promoted, should we launch auto task for Dynamic Table?

Synced with my colleague who is familiar with pg_task extension, and confirmed that pg_task could work on mirrors.

src/backend/commands/createas.c

src/backend/parser/gram.y

src/bin/psql/describe.c

avamingli · 2024-12-04T10:47:30Z

Patch miss tab-completion for DYNAMIC feature.

According to various feedback, I will enable this.
Perhaps within pg_dump patch of Dynamic Table.

avamingli · 2024-12-04T15:53:07Z

Patch miss tab-completion for DYNAMIC feature.

According to various feedback, I will enable this. Perhaps within pg_dump patch of Dynamic Table.

Tab-complete added in 80bfc73.
pg_dump added in 0b99585.

avamingli · 2024-12-04T16:38:34Z

Add commit: 7a13989
to give an example of Dynamic Table use case: how to query on external tables as fast as internal tables?

src/backend/commands/taskcmds.c

avamingli · 2024-12-06T05:16:18Z

Rebased and fixed: Bump catversion in dadeb84

Dynamic Table is a an auto-refreshing materialized view which could be constructed by base tables, external tables, materialized views and dynamic tables. And it could be used to answer query by AQUMV. As normal tables in CBDB, dynamic tables could also have distribution keys. The purpose of Dynamic Tables is to solve the problem often raised by customers who are big fans of a lakehouse architecture: how can we run queries on external tables as fast as internal tables? CREATE DYNAMIC TABLE: CREATE DYNAMIC TABLE dt0 SCHEDULE '5 * * * *' AS SELECT a, b, sum(c) FROM t1 GROUP BY a, b WITH NO DATA DISTRIBUTED BY(b); CREATE DYNAMIC TABLE \d List of relations Schema | Name | Type | Owner | Storage --------+------+---------------+---------+--------- public | dt0 | dynamic table | gpadmin | heap public | t1 | table | gpadmin | heap (2 rows) CREATE DYNAMIC TABLE xxx AS Query The Query allows any valid SELECT SQL of Materialized Views: from single or multiple relations, base tables, materialized views, and dynamic tables as well, joins, subquery, aggregation, group by and etc. SCHEDULE: A string used to schedule background job which auto-refreshes the dynamic table. We follow the valid string of pg_cron extension which supports linux crontab, refer https://crontab.guru ┌───────────── min (0 - 59) │ ┌────────────── hour (0 - 23) │ │ ┌─────────────── day of month (1 - 31) or last day of the month ($) │ │ │ ┌──────────────── month (1 - 12) │ │ │ │ ┌───────────────── day of week (0 - 6) (0 to 6 are Sunday to │ │ │ │ │ Saturday, or use names; 7 is also Sunday) │ │ │ │ │ │ │ │ │ │ * * * * * You can also use '[1-59] seconds' to schedule a job based on an interval. The example creates a cron job refreshing the dynamic table at minute 5 of each hour. For convenience, SCHEDULE is optional. If user didn't specific it, a default schedule is provided: at every 5th minute. WITH NO DATA: Same as Materialized View, will create an empty Dynamic Table if specified. DISTRIBUTED BY: Same as normal tables in CBDB, Dynamic Tables could support distribution keys as materialized views. Refresh Dynamic Table As seen in pg_task, we put a command to auto-refresh dynamic tables. However, if users want to do a REFRESH manually, exec command REFRESH DYNAMIC TABLE is also supported. REFRESH DYNAMIC TABLE dt0; REFRESH DYNAMIC TABLE Refresh WITH NO DATA Same as Materialized Views, Refresh with no data will truncate the Dynamic Table and make it unpopulated status. REFRESH DYNAMIC TABLE dt0 WITH NO DATA; REFRESH DYNAMIC TABLE Drop Dynamic Table Drop a Dynamic Table will drop its scheduler job automatically. DROP DYNAMIC TABLE dt0; DROP DYNAMIC TABLE Like Materialized Views, Dynamic Tables could be used to answer query too. This is limited by AQUMV. Authored-by: Zhang Mingli [email protected]

Doc for CREATE/DROP/REFRESH DYNAMIC TABLE. Authored-by: Zhang Mingli [email protected]

Use pg_dump to dump Dynamic Tables. Authored-by: Zhang Mingli [email protected]

Add tab-complete of CREATE/DROP/REFRESH DYNAMIC TABLE. Authored-by: Zhang Mingli [email protected]

Add a case of Dynamic Table speeding up query on external tables of lakehouse architecture. Instead of quering on external table, query on dynamic table and compute results automatically. The example is built on techniques of dynamic tables(materialized view with auto refreshing process), ability of materializd view could have external tables and AQUMV (Answer Query Using Materialized Views). CREATE READABLE EXTERNAL TABLE ext_r(id int) LOCATION('demoprot://dynamic_table_text_file.txt') FORMAT 'text'; EXPLAIN(COSTS OFF, VERBOSE) SELECT sum(id) FROM ext_r where id > 5; QUERY PLAN -------------------------------------------------------------- Finalize Aggregate Output: sum(id) -> Gather Motion 3:1 (slice1; segments: 3) Output: (PARTIAL sum(id)) -> Partial Aggregate Output: PARTIAL sum(id) -> Foreign Scan on dynamic_table_schema.ext_r Output: id Filter: (ext_r.id > 5) CREATE DYNAMIC TABLE dt_external AS SELECT * FROM ext_r where id > 5; ANALYZE dt_external; SET optimizer = OFF; SET LOCAL enable_answer_query_using_materialized_views = ON; SET LOCAL aqumv_allow_foreign_table = ON; EXPLAIN(COSTS OFF, VERBOSE) SELECT sum(id) FROM ext_r where id > 5; QUERY PLAN --------------------------------------------------------------- Finalize Aggregate Output: sum(id) -> Gather Motion 3:1 (slice1; segments: 3) Output: (PARTIAL sum(id)) -> Partial Aggregate Output: PARTIAL sum(id) -> Seq Scan on dynamic_table_schema.dt_external Output: id Settings: enable_answer_query_using_materialized_views = 'on', optimizer = 'off' Optimizer: Postgres query optimizer (10 rows) Authored-by: Zhang Mingli [email protected]

Add function to get the SCHEDULE info of job in pg_task go hand in hand with a Dynamic Table. Authored-by: Zhang Mingli [email protected]

Dynamic Table's SCHEDULE clause is stored in pg_task jobs. Add it when a Dynamic Table is dumped. Since the SCHEDULE clause is optional, there would be no error if we forget it when dump a Dynamic Table info. And a default SCHEDULE is added with the value of Macro: DYNAMIC_TABLE_DEFAULT_REFRESH_INTERVAL Authored-by: Zhang Mingli [email protected]

avamingli · 2024-12-06T12:46:37Z

Update: two commits added to resolve the missed SCHEDULE clause when pg_dump DYNAMIC TABLE.

b215893 Add it when a Dynamic Table is dumped.

Dynamic Table's SCHEDULE clause is stored in pg_task jobs.
Since the SCHEDULE clause is optional, there would be no error if we forget it when dump a Dynamic Table info.
And a default SCHEDULE is added with the value of Macro: DYNAMIC_TABLE_DEFAULT_REFRESH_INTERVAL

17c9fed provides a function pg_get_dynamic_table_schedule() to get SCHEDULE info for pg_dump.
And, users also could use it to see SCHEDULE info of Dynamic Table.

src/test/regress/expected/dynamic_table.out

avamingli requested a review from my-ship-it November 21, 2024 08:00

avamingli force-pushed the dynamic_table branch from a2c9b3c to 63d3383 Compare November 21, 2024 08:01

tuhaihe requested a review from reshke November 21, 2024 08:27

reshke reviewed Nov 21, 2024

View reviewed changes

src/bin/psql/describe.c Outdated Show resolved Hide resolved

avamingli added the type: catalog_change label Nov 25, 2024

avamingli force-pushed the dynamic_table branch from 63d3383 to d289246 Compare November 25, 2024 08:25

avamingli force-pushed the dynamic_table branch from d289246 to 25faf4a Compare November 26, 2024 08:32

avamingli force-pushed the dynamic_table branch from 25faf4a to d9cd5e0 Compare November 26, 2024 09:54

my-ship-it reviewed Nov 26, 2024

View reviewed changes

src/backend/commands/matview.c Outdated Show resolved Hide resolved

my-ship-it previously approved these changes Nov 27, 2024

View reviewed changes

avamingli dismissed my-ship-it’s stale review via ef1af11 November 27, 2024 04:01

avamingli force-pushed the dynamic_table branch from d9cd5e0 to ef1af11 Compare November 27, 2024 04:01

yjhjstz reviewed Nov 28, 2024

View reviewed changes

src/backend/commands/createas.c Show resolved Hide resolved

avamingli force-pushed the dynamic_table branch from ef1af11 to 22de9dc Compare November 28, 2024 15:13

yjhnupt reviewed Dec 3, 2024

View reviewed changes

src/backend/parser/gram.y Show resolved Hide resolved

yjhnupt reviewed Dec 3, 2024

View reviewed changes

src/bin/psql/describe.c Show resolved Hide resolved

avamingli force-pushed the dynamic_table branch 2 times, most recently from 5a2dab1 to 80bfc73 Compare December 4, 2024 15:51

avamingli force-pushed the dynamic_table branch from f1e78e4 to 7a13989 Compare December 4, 2024 16:35

yjhjstz reviewed Dec 5, 2024

View reviewed changes

src/backend/commands/taskcmds.c Show resolved Hide resolved

yjhjstz reviewed Dec 5, 2024

View reviewed changes

src/backend/commands/taskcmds.c Show resolved Hide resolved

avamingli mentioned this pull request Dec 5, 2024

Make gp_matview_aux and gp_matview_tables unshared catalog. #756

Merged

12 tasks

avamingli force-pushed the dynamic_table branch from 7a13989 to 314c09b Compare December 6, 2024 05:14

avamingli added 6 commits December 6, 2024 20:40

Add document about DYNAMIC TABLE.

597bfbf

Doc for CREATE/DROP/REFRESH DYNAMIC TABLE. Authored-by: Zhang Mingli [email protected]

Add DYNAMIC TABLE support to pg_dump.

c72e333

Use pg_dump to dump Dynamic Tables. Authored-by: Zhang Mingli [email protected]

Add DYNAMIC TABLE support to psql.

238a094

Add tab-complete of CREATE/DROP/REFRESH DYNAMIC TABLE. Authored-by: Zhang Mingli [email protected]

Add pg_get_dynamic_table_schedule() for dynamic tables.

17c9fed

Add function to get the SCHEDULE info of job in pg_task go hand in hand with a Dynamic Table. Authored-by: Zhang Mingli [email protected]

avamingli force-pushed the dynamic_table branch 2 times, most recently from 7516c41 to 75fbfb4 Compare December 6, 2024 12:43

avamingli force-pushed the dynamic_table branch from 75fbfb4 to b215893 Compare December 6, 2024 12:43

yjhjstz reviewed Dec 8, 2024

View reviewed changes

src/test/regress/expected/dynamic_table.out Show resolved Hide resolved

yjhjstz approved these changes Dec 9, 2024

View reviewed changes

my-ship-it approved these changes Dec 9, 2024

View reviewed changes

my-ship-it merged commit 56632f5 into apache:main Dec 9, 2024
10 checks passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Feature] Dynamic Table. #725

[Feature] Dynamic Table. #725

avamingli commented Nov 21, 2024 •

edited

Loading

reshke commented Nov 21, 2024

avamingli commented Nov 21, 2024

avamingli commented Nov 21, 2024

avamingli commented Nov 21, 2024

avamingli commented Nov 21, 2024 •

edited

Loading

reshke commented Nov 21, 2024 •

edited

Loading

my-ship-it commented Nov 26, 2024

avamingli commented Nov 26, 2024

avamingli commented Nov 26, 2024

edespino commented Nov 26, 2024

avamingli commented Nov 26, 2024

my-ship-it commented Nov 26, 2024

my-ship-it commented Nov 26, 2024

my-ship-it left a comment

avamingli commented Nov 27, 2024

avamingli commented Dec 4, 2024

avamingli commented Dec 4, 2024

avamingli commented Dec 4, 2024

avamingli commented Dec 6, 2024

avamingli commented Dec 6, 2024

[Feature] Dynamic Table. #725

[Feature] Dynamic Table. #725

Conversation

avamingli commented Nov 21, 2024 • edited Loading

Create Dynamic Table:

SCHEDULE:

WITH NO DATA:

DISTRIBUTED BY:

Refresh Dynamic Table

REFRESH WITH NO DATA;

Drop Dynamic Table:

Privileges

Use Dynamic Tables to answer query

What does this PR do?

Type of Change

Breaking Changes

Test Plan

Impact

Checklist

Additional Context

reshke commented Nov 21, 2024

avamingli commented Nov 21, 2024

avamingli commented Nov 21, 2024

avamingli commented Nov 21, 2024

avamingli commented Nov 21, 2024 • edited Loading

reshke commented Nov 21, 2024 • edited Loading

my-ship-it commented Nov 26, 2024

avamingli commented Nov 26, 2024

avamingli commented Nov 26, 2024

edespino commented Nov 26, 2024

avamingli commented Nov 26, 2024

my-ship-it commented Nov 26, 2024

my-ship-it commented Nov 26, 2024

my-ship-it left a comment

Choose a reason for hiding this comment

avamingli commented Nov 27, 2024

avamingli commented Dec 4, 2024

avamingli commented Dec 4, 2024

avamingli commented Dec 4, 2024

avamingli commented Dec 6, 2024

avamingli commented Dec 6, 2024

avamingli commented Nov 21, 2024 •

edited

Loading

avamingli commented Nov 21, 2024 •

edited

Loading

reshke commented Nov 21, 2024 •

edited

Loading