gustavodemorais commented on code in PR #27886:
URL: https://github.com/apache/flink/pull/27886#discussion_r3117842001
##########
docs/content/docs/sql/reference/queries/changelog.md:
##########
@@ -154,18 +154,18 @@ This is useful when you need to materialize changelog
events into a downstream s
```sql
SELECT * FROM TO_CHANGELOG(
- input => TABLE source_table,
+ input => TABLE source_table [PARTITION BY key_col],
[op => DESCRIPTOR(op_column_name),]
[op_mapping => MAP['INSERT', 'I', 'DELETE', 'D', ...]]
)
```
### Parameters
-| Parameter | Required | Description |
-|:-------------|:---------|:------------|
-| `input` | Yes | The input table. Accepts insert-only, retract, and
upsert tables. |
-| `op` | No | A `DESCRIPTOR` with a single column name for the
operation code column. Defaults to `op`. |
+| Parameter | Required | Description
|
+|:-------------|:---------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `input` | Yes | The input table. With `PARTITION BY`, rows with
the same key are co-located and run in the same operator instance. Without
`PARTITION BY`, each row is processed independently. Accepts insert-only,
retract, and upsert tables. For upsert tables, providing `PARTITION BY` is
recommended for better performance. |
Review Comment:
The key doesn't have to match exactly, it can be a subset. Updating with
"For upsert tables, the provided `PARTITION BY` key should match or be a subset
of the upsert key of the subquery"
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
