feat(batch): support basic postgres tvf #18811

kwannoel · 2024-10-08T09:39:58Z

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

This PR introduces postgres tvf, in the form of postgres_query(...). You can look at the release notes for more details.

We implement the full postgres tvf, in frontend and batch engine. The key parts are firstly in the binder, where we instantiate a pg connection, then prepare the pg query to get the output schema. Subsequently, we will rewrite it into its own plan node (PostgresQueryNode), and its own batch executor. Then in the batch executor, we again instantiate a client and run the actual query against postgres. Finally we deserialize the output from postgres and send it to downstream batch executors.

There's still things missing. We can support these in separate PRs:

Support for serde of more types (see postgres cdc connector).
Support for pagination so we don't hit OOM when reading a large table.
Support under projectset feat(batch): support basic postgres tvf #18811 (review)
Support SECRET in basic postgres tvf password field.

--

Although there's >740 LOC, most of these changes are boilerplate.

Checklist

I have written necessary rustdoc comments
I have added necessary unit tests and integration tests
I have added test labels as necessary. See details.
I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
All checks passed in ./risedev check (or alias, ./risedev c)
My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

This feature should be a TECHNICAL PREVIEW. See below.

This PR introduces the postgres_query tvf. Its syntax will very likely change down the road. So the interface and examples you see below will be obsolete in subsequent versions. That being said the core functionality will still exist.

postgres_query is defined as follows:

postgres_query(hostname varchar, port varchar, username varchar, password varchar, database_name varchar, query varchar)

An example of its usage:

Postgres:

CREATE TABLE test (id bigint primary key, x int);
INSERT INTO test select id, id::int from generate_series(1, 100) as t(id);

RisingWave:

select * from postgres_query('localhost', '5432', 'postgres', 'postgres', mydb', 'select * from test where id > 90;');
----
91 91
92 92
93 93
94 94
95 95
96 96
97 97
98 98
99 99
100 100

gitguardian · 2024-10-08T09:58:38Z

⚠️ GitGuardian has uncovered 16 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
9425213	Triggered	Generic Password	`b1a286d`	e2e_test/source/tvf/postgres_query.slt	View secret
9425213	Triggered	Generic Password	`e2e20f0`	e2e_test/source/tvf/postgres_query.slt	View secret
9425213	Triggered	Generic Password	`e2e20f0`	e2e_test/source/tvf/postgres_query.slt	View secret
9425213	Triggered	Generic Password	`e2e20f0`	e2e_test/source/tvf/postgres_query.slt	View secret
9425213	Triggered	Generic Password	`e2e20f0`	e2e_test/source/tvf/postgres_query.slt	View secret
9425213	Triggered	Generic Password	`b1a286d`	e2e_test/source/tvf/postgres_query.slt	View secret
9425213	Triggered	Generic Password	`111a7a5`	e2e_test/source/tvf/postgres_query.slt	View secret
9425213	Triggered	Generic Password	`b5e76a5`	e2e_test/source/tvf/postgres_query.slt	View secret
9425213	Triggered	Generic Password	`b5e76a5`	e2e_test/source/tvf/postgres_query.slt	View secret
9425213	Triggered	Generic Password	`b5e76a5`	e2e_test/source/tvf/postgres_query.slt	View secret
9425213	Triggered	Generic Password	`b5e76a5`	e2e_test/source/tvf/postgres_query.slt	View secret
9425213	Triggered	Generic Password	`5b66d01`	e2e_test/source/tvf/postgres_query.slt	View secret
9425213	Triggered	Generic Password	`c254e71`	e2e_test/source/tvf/postgres_query.slt	View secret
9425213	Triggered	Generic Password	`66464d9`	e2e_test/source/tvf/postgres_query.slt	View secret
9425213	Triggered	Generic Password	`fe10528`	e2e_test/source/tvf/postgres_query.slt	View secret
9425213	Triggered	Generic Password	`8ea47ed`	e2e_test/source/tvf/postgres_query.slt	View secret

🛠 Guidelines to remediate hardcoded secrets

Understand the implications of revoking this secret by investigating where it is used in your code.
Replace and store your secrets safely. Learn here the best practices.
Revoke and rotate these secrets.
If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

following these best practices for managing and storing secrets including API keys and other credentials
install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

src/frontend/src/expr/table_function.rs

kwannoel · 2024-10-09T06:36:18Z

src/frontend/src/optimizer/plan_node/batch_postgres_query.rs

+    }
+
+    pub fn clone_with_dist(&self) -> Self {
+        let base = self.base.clone_with_new_distribution(Distribution::Single);


I noticed file_scan uses Distribution::SomeShard instead here. But that's a problem because when using that, 4 instances of the PostgresQueryExecutor were spawned. It should only spawn a single one.

I changed it to Distribution::Single for batch_postgres_query.rs and it fixed it for me.

Just flagging it, in case a similar bug can occur for file_scan source. cc @chenzl25

xiangjinwu

Btw table function can also be part of ProjectSet, although practically we can leave it as unsupported:

dev=> select postgres_query('localhost', '5432', 'postgres', 'postgres', 'test', 'select * from t');
ERROR:  Failed to run the query

Caused by these errors (recent errors listed first):
  1: failed to build executor
  2: Expr error
  3: Unsupported function: postgres_query(character varying, character varying, character varying, character varying, character varying, character varying) -> struct<s character varying>

e2e_test/source/tvf/postgres_query.slt

src/frontend/src/binder/expr/function/mod.rs

src/batch/src/executor/postgres_query.rs

xiangjinwu · 2024-10-10T08:34:22Z

Also wants to mentioned #14763. Without it:

postgres_query(..., 'select * from t where k = ''foo'' '); -- single quotes inside the query shall be doubled (NOT double quote)

With it:

postgres_query(..., $$select * from t where k = 'foo' $$); -- just copy paste unless it contains $$ inside

Co-authored-by: xiangjinwu <17769960+xiangjinwu@users.noreply.github.com>

xxchan

This feature should be a TECHNICAL PREVIEW.

sounds good

xxchan · 2024-10-11T01:58:58Z

ci/scripts/e2e-source-test.sh

+echo "--- postgres_query tvf test"
+risedev slt './e2e_test/source/tvf/postgres_query.slt'


It would be better to put in e2e_test/source_inline, and no need to modify CI script

Currently inline source test does not have a postgres service managed by risedev. We can refactor it after #18099.

xxchan · 2024-10-11T02:00:18Z

e2e_test/source/tvf/postgres_query.slt

@@ -0,0 +1,40 @@
+system ok
+PGHOST=db PGPORT=5432 PGUSER=postgres PGPASSWORD=postgres PGDATABASE=cdc_test psql -c "


It would be better to use $RISEDEV_ envvars, instead of hard-coded ones. Then you can run it easier locally

Current e2e-source-test does not have a postgres service managed by risedev. We can refactor it after #18099.

I think we already have risedev managed pg #16662

Yes, it can be configured as a service in the risedev config. But switching the risedev configuration may cause diff conflicts with #18099. There could be conflicts with the ci-managed postgres instance as well.

Migrating everything together in #18858 after #18099 will be more straightforward.

Hmmm, we already have a dedicated risedev profile, so I don't think it will affect other stuff..

risingwave/ci/scripts/e2e-source-test.sh

Lines 38 to 41 in c80cbf3

echo "--- e2e, inline test"

RUST_LOG="debug,risingwave_stream=info,risingwave_batch=info,risingwave_storage=info" \

risedev ci-start ci-inline-source-test

risedev slt './e2e_test/source_inline/**/*.slt'

risingwave/risedev.yml

Lines 952 to 979 in c80cbf3

ci-inline-source-test:

config-path: src/config/ci-recovery.toml

steps:

- use: minio

- use: etcd

unsafe-no-fsync: true

- use: meta-node

meta-backend: etcd

- use: compute-node

enable-tiered-cache: true

- use: frontend

- use: compactor

- use: pubsub

persist-data: true

- use: kafka

user-managed: true

address: message_queue

port: 29092

- use: schema-registry

user-managed: true

address: schemaregistry

port: 8082

- use: mysql

port: 3306

address: mysql

user: root

password: 123456

user-managed: true

I just mean to write the new tests introduced in the new style, without changing existing tests. If you mean migrating all tests to the style later after that PR, it also sounds good

BugenZhao · 2024-10-11T05:00:55Z

src/batch/src/error.rs

@@ -127,6 +128,13 @@ pub enum BatchError {
        ParquetError,
    ),

+    #[error(transparent)]


I'm not sure if the error messages from Postgres can be clearly distinguished from ours, given that we're using transparent and not including any prompt here.

As we introduce more external system queries and directly interact with them in the batch crate, I'm concerned that BatchError might become another maintainability hell just like ConnectorError.

Just FYI, in #15086, we made ConnectorError a wrapper of anyhow::Error because it has too many variants (may check the documentation on def_anyhow_wrapper for the underlying ideas). For example, shall we introduce a ExtSystemError with this approach (or even reuse ConnectorError) and make it the only variant for all external system queries in BatchError?

Just FYI, in #15086, we made ConnectorError a wrapper of anyhow::Error because it has too many variants (may check the documentation on def_anyhow_wrapper for the underlying ideas). For example, shall we introduce a ExtSystemError with this approach (or even reuse ConnectorError) and make it the only variant for all external system queries in BatchError?

I think this a fair point. There's quite a few tvf to be supported. And we should preemptively introduce an ExtSystemError to deal with it.

I realize there's more external system errors like iceberg, parquet from before this PR, and not just postgres error, which was introduced in this PR.
I will handle it in a separate PR since this is a larger refactor: #18860

#[error(transparent)] Iceberg( #[from] #[backtrace] iceberg::Error, ), #[error(transparent)] Parquet( #[from] #[backtrace] ParquetError, ), #[error(transparent)] Postgres( #[from] #[backtrace] tokio_postgres::Error, ),

BugenZhao · 2024-10-11T05:12:13Z

src/frontend/src/expr/table_function.rs

+            let schema = tokio::task::block_in_place(|| {
+                RUNTIME.block_on(async {


May note that this still blocks the current thread, meaning that the concurrency of binding Postgres TVF cannot exceed the TOKIO_WORKER_THREADS. As we're introducing more in the future, we may have to consider refactoring this part. Like

make binder async (can be abused)

resolve necessary info ahead of time

resolve necessary info ahead of time

I was considering the latter approach. Something like splitting the binder into 2 phases, first is async phase which can resolve bindings like this by traversing the ast. Second is the current binder, just a pure function.

So it will be something like:

async fn bind(&self, ast) { let pure_ast = self.bind_async(ast); let ast = self.bind_sync(pure_ast); } async fn bind_async() {...} fn bind_sync() {...}

This also means we need 2 IRs in binder. Something like:

PartialBoundQuery --- artifact from bind_async BoundQuery -- artifact from bind_sync

But this approach seems quite heavy, we now need to maintain 2 IRs rather than jsut 1 in binder.

Just mentioning a third option. I do not prefer it but it may inspire an improved fourth option:

Let the user specify return schema and defer the async validation (instead of ahead of time)

The following syntax exists in PostgreSQL but we have not supported it yet:

select * from json_to_recordset('[{"a":1,"b":"foo"}, {"a":"2","c":"bar"}]') as x(a int, b text) -- Similarly: select * from postgres_query(...) as x(a int, b text)

make binder async (can be abused)

Historical context on binder not being async, although most of the discussion happened in slack private channel:
#173 (comment)

So far the simplest way, while preserving good ux, seems to be just making the binder async.

The other approaches in this thread will either make maintainence more cumbersome (extra IR in binder), or lead to complexity in ux.

To clarify making binder async may not be easy. We can discuss the topic separately, not blocking this PR but necessary before going further with such batch TVFs.

BugenZhao · 2024-10-11T05:13:05Z

src/frontend/src/optimizer/plan_node/logical_postgres_query.rs

+        schema: Schema,
+        hostname: String,
+        port: String,
+        username: String,
+        password: String,
+        database: String,
+        query: String,


Shall we extract these fields into a struct to make it clearer?

We will be removing some/all of these fields and using Connection instead down the road. So no need to refactor now.

kwannoel · 2024-10-11T06:28:10Z

Thanks for the many reviews, but still need one for Cargo.lock. I think they have all been addressed. It blocks this PR from merging 😆

stdrc · 2024-10-11T06:50:27Z

postgres_query is defined as follows:

postgres_query(hostname varchar, port varchar, username varchar, password varchar, database_name varchar, query varchar)

Just to confirm, can we use SECRET in the place of password?

kwannoel · 2024-10-11T06:58:03Z

postgres_query is defined as follows:
postgres_query(hostname varchar, port varchar, username varchar, password varchar, database_name varchar, query varchar)
Just to confirm, can we use SECRET in the place of password?

I'll add a test for it subsequently. Added to the PR description of followup tasks.

kwannoel · 2024-10-18T07:19:16Z

postgres_query is defined as follows:
postgres_query(hostname varchar, port varchar, username varchar, password varchar, database_name varchar, query varchar)
Just to confirm, can we use SECRET in the place of password?

Wait for connection to be supported. SECRET can be used there, the original interface will be deprecated as mentioned in PR sdescription.

github-actions bot added the type/feature label Oct 8, 2024

kwannoel added the ci/run-e2e-source-tests label Oct 8, 2024

kwannoel added the ci/pr/run-selected label Oct 8, 2024

kwannoel force-pushed the kwannoel/pg-tvf-fe branch 2 times, most recently from e27da02 to ad7db51 Compare October 8, 2024 14:14

kwannoel commented Oct 8, 2024

View reviewed changes

src/frontend/src/expr/table_function.rs Outdated Show resolved Hide resolved

kwannoel removed the ci/pr/run-selected label Oct 9, 2024

kwannoel marked this pull request as ready for review October 9, 2024 06:32

kwannoel requested a review from a team as a code owner October 9, 2024 06:32

kwannoel requested a review from stdrc October 9, 2024 06:32

graphite-app bot requested a review from a team October 9, 2024 06:32

kwannoel commented Oct 9, 2024

View reviewed changes

kwannoel requested review from chenzl25 and xiangjinwu October 9, 2024 07:14

graphite-app bot requested a review from a team October 9, 2024 08:04

kwannoel added 14 commits October 9, 2024 17:54

interim: add tvf to binder

df14470

bind postgres_query table_function

b56f281

add boilerplate for optimizer plan nodes

ccc90fb

update plan node fields

22ec6b3

fmt

514e031

update proto + add batch executor skeleton

b8f8aea

fmt

7e19074

interim commit: add pg tvf functionality

26a7a11

support serde in postgres_query executor

4abe65c

add tests

b1a286d

fix table function error in madsim + fix postgres_query tvf test

e2e20f0

consume all remaining chunks

2b5946e

add logs

6d09259

fix connection not polled

c2b444b

match quotes

c254e71

xiangjinwu reviewed Oct 10, 2024

View reviewed changes

e2e_test/source/tvf/postgres_query.slt Outdated Show resolved Hide resolved

src/frontend/src/binder/expr/function/mod.rs Outdated Show resolved Hide resolved

src/batch/src/executor/postgres_query.rs Outdated Show resolved Hide resolved

kwannoel and others added 4 commits October 10, 2024 17:16

fix test

650ecd9

Update src/batch/src/executor/postgres_query.rs

1413bd4

Co-authored-by: xiangjinwu <17769960+xiangjinwu@users.noreply.github.com>

add timezone

66464d9

Update src/frontend/src/binder/expr/function/mod.rs

4674982

Co-authored-by: xiangjinwu <17769960+xiangjinwu@users.noreply.github.com>

kwannoel requested a review from xiangjinwu October 10, 2024 09:20

kwannoel added 4 commits October 10, 2024 17:28

fix

fe10528

fix

ad46398

fix

4a58d05

fix slt

8ea47ed

kwannoel requested a review from a team October 10, 2024 10:45

xxchan reviewed Oct 11, 2024

View reviewed changes

BugenZhao reviewed Oct 11, 2024

View reviewed changes

kwannoel mentioned this pull request Oct 11, 2024

Create a ExternalSystemError in BatchError to force explicit handling of external system errors #18860

Closed

xiangjinwu approved these changes Oct 11, 2024

View reviewed changes

kwannoel added this pull request to the merge queue Oct 11, 2024

kwannoel removed this pull request from the merge queue due to a manual request Oct 11, 2024

kwannoel added this pull request to the merge queue Oct 11, 2024

Merged via the queue into main with commit da977e9 Oct 11, 2024
33 of 34 checks passed

kwannoel deleted the kwannoel/pg-tvf-fe branch October 11, 2024 07:30

kwannoel added the user-facing-changes Contains changes that are visible to users label Oct 23, 2024

WanYixian mentioned this pull request Dec 3, 2024

Document ingest data from PostgreSQL table risingwavelabs/risingwave-docs#108

Merged

BugenZhao mentioned this pull request Dec 11, 2024

risingwave 2.1.0 risingwavelabs/homebrew-risingwave#46

Closed

1 task

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat(batch): support basic postgres tvf #18811

feat(batch): support basic postgres tvf #18811

kwannoel commented Oct 8, 2024 •

edited

Loading

gitguardian bot commented Oct 8, 2024 •

edited

Loading

kwannoel Oct 9, 2024

xiangjinwu left a comment •

edited

Loading

xiangjinwu commented Oct 10, 2024 •

edited

Loading

xxchan left a comment

xxchan Oct 11, 2024

kwannoel Oct 11, 2024

kwannoel Oct 11, 2024

xxchan Oct 11, 2024

kwannoel Oct 11, 2024

kwannoel Oct 11, 2024

xxchan Oct 11, 2024

kwannoel Oct 11, 2024

xxchan Oct 11, 2024

xxchan Oct 11, 2024

BugenZhao Oct 11, 2024

BugenZhao Oct 11, 2024

kwannoel Oct 11, 2024

kwannoel Oct 11, 2024

BugenZhao Oct 11, 2024

kwannoel Oct 11, 2024 •

edited

Loading

xiangjinwu Oct 11, 2024

xiangjinwu Oct 11, 2024

kwannoel Oct 11, 2024

xiangjinwu Oct 11, 2024 •

edited

Loading

BugenZhao Oct 11, 2024

kwannoel Oct 11, 2024

kwannoel commented Oct 11, 2024

stdrc commented Oct 11, 2024

kwannoel commented Oct 11, 2024

kwannoel commented Oct 18, 2024

		echo "--- postgres_query tvf test"
		risedev slt './e2e_test/source/tvf/postgres_query.slt'

		@@ -0,0 +1,40 @@
		system ok
		PGHOST=db PGPORT=5432 PGUSER=postgres PGPASSWORD=postgres PGDATABASE=cdc_test psql -c "

	echo "--- e2e, inline test"
	RUST_LOG="debug,risingwave_stream=info,risingwave_batch=info,risingwave_storage=info" \
	risedev ci-start ci-inline-source-test
	risedev slt './e2e_test/source_inline/*/.slt'

	ci-inline-source-test:
	config-path: src/config/ci-recovery.toml
	steps:
	- use: minio
	- use: etcd
	unsafe-no-fsync: true
	- use: meta-node
	meta-backend: etcd
	- use: compute-node
	enable-tiered-cache: true
	- use: frontend
	- use: compactor
	- use: pubsub
	persist-data: true
	- use: kafka
	user-managed: true
	address: message_queue
	port: 29092
	- use: schema-registry
	user-managed: true
	address: schemaregistry
	port: 8082
	- use: mysql
	port: 3306
	address: mysql
	user: root
	password: 123456
	user-managed: true

		let schema = tokio::task::block_in_place(\|\| {
		RUNTIME.block_on(async {

feat(batch): support basic postgres tvf #18811

feat(batch): support basic postgres tvf #18811

Conversation

kwannoel commented Oct 8, 2024 • edited Loading

What's changed and what's your intention?

Checklist

Documentation

Release note

gitguardian bot commented Oct 8, 2024 • edited Loading

⚠️ GitGuardian has uncovered 16 secrets following the scan of your pull request.

Choose a reason for hiding this comment

xiangjinwu left a comment • edited Loading

Choose a reason for hiding this comment

xiangjinwu commented Oct 10, 2024 • edited Loading

xxchan left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

kwannoel Oct 11, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

xiangjinwu Oct 11, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

kwannoel commented Oct 11, 2024

stdrc commented Oct 11, 2024

kwannoel commented Oct 11, 2024

kwannoel commented Oct 18, 2024

kwannoel commented Oct 8, 2024 •

edited

Loading

gitguardian bot commented Oct 8, 2024 •

edited

Loading

xiangjinwu left a comment •

edited

Loading

xiangjinwu commented Oct 10, 2024 •

edited

Loading

kwannoel Oct 11, 2024 •

edited

Loading

xiangjinwu Oct 11, 2024 •

edited

Loading