You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/user/data/syntax_options/create_table/create_table_options_source_populated_kafka.yml
-1Lines changed: 0 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,6 @@ rows:
48
48
| `JSON` | Decode the data as JSON. |
49
49
| `TEXT` | Decode the data as TEXT. |
50
50
| `BYTES` | Decode the data as BYTES. |
51
-
| `CSV WITH HEADER ( <col_name>[, ...]) [DELIMITED BY <char>]` | Parse the data as CSV with a header row. Materialize uses this header to infer both the number of columns and their names. The header is **not** ingested as data. The optional `DELIMITED BY <char>` clause specifies the delimiter character. <br><br>The data is decoded as [`text`](/sql/types/text). You can convert the data to other to other types using explicit [casts](/sql/functions/cast/) when creating views.|
52
51
| `CSV WITH <num> COLUMNS DELIMITED BY <char>` | Parse the data as CSV with a specified number of columns and a specified delimiter. The columns are named `column1`, `column2`...`columnN`. <br><br> The data is decoded as [`text`](/sql/types/text). You can convert the data to other to other types using explicit [casts](/sql/functions/cast/) when creating views.|
The mesage body format. The following `<format>`s are supported:
16
+
17
+
| Format | Type | Description |
18
+
|-------------|--------|-------------|
19
+
| `BYTES` | `bytea` | Does **no parsing** of the request, and stores the body of a request as it was received. |
20
+
| `JSON` | `jsonb` | Parses the body of a request as JSON. Also accepts events batched as newline-delimited JSON (`NDJSON`). If the body is not valid JSON, a response of `400 Bad Request` will be returned. |
21
+
| `JSON ARRAY`| `jsonb` | Parses the body of a request as a list of JSON objects, automatically expanding the list of objects to individual rows. Also accepts a single JSON object. If the body is not valid JSON, a response of `400 Bad Request` will be returned. |
22
+
| `TEXT` | `text` | Parses the body of a request as `UTF-8` text. If the body is not valid `UTF-8`, a response of `400 Bad Request` will be returned. |
23
+
24
+
- "Parameter": |
25
+
**INCLUDE <header_option\>**
26
+
"Description": |
27
+
28
+
Optional. If specified, include the header information in the table.
29
+
30
+
| header_option | Description |
31
+
|---------------|-------------|
32
+
| `INCLUDE HEADER <header_name> AS <col_name> [BYTES] [,...]` | Include the specified header in a column named `<col_name>`. |
33
+
| `INCLUDE HEADERS [([NOT] <header_name> [, [NOT] <header_name> ... ])]`| Include a column named `headers` of type `map[text => text]`: <ul><li>`INCLUDE HEADERS` to include all headers of the request.</li><li>`INCLUDE HEADERS (<header_name>, ...)` to only include the specified headers.</li><li>`INCLUDE HEADERS (NOT <header_name>, ...)` to include all headers except those specified with the `NOT` options.</li></ul>|
34
+
35
+
- "Parameter": |
36
+
**CHECK( [ WITH (...)] <check_expression>)**
37
+
"Description": |
38
+
39
+
Optional. If specified, validate each request received using the boolean
40
+
`<check_expression>`. To reference the body, headers, or secret in the
41
+
check expression, use the `WITH` clause.
42
+
43
+
| WITH options | Description
44
+
| ------------------|-----------------
45
+
| `BODY [AS <alias>] [BYTES]` | Makes available the `body` column -- typed as `text` -- to the check expression. The column can be renamed with the optional **AS** _alias_ statement. The data type can be changed to `bytea` with the optional **BYTES** keyword.
46
+
| `HEADERS [AS <alias>] [BYTES]` | Makes available the `headers` column -- typed as `map[text => text]` -- to the check expression. The column can be renamed with the optional **AS** _alias_ statement. The data type can be changed to `map[text => bytea]` with the optional **BYTES** keyword.
47
+
| `SECRET <secret_name> [AS <alias>] [BYTES]` | Securely makes available a [`SECRET`](/sql/create-secret) -- typed as `text` -- to the check expression. The column can be renamed with the optional **AS** _alias_ statement. The data type can be changed to `map[text => bytea]` with the optional **BYTES** keyword. When used with the [`constant_time_eq` function](/sql/functions/#constant_time_eq), if the secret is in a different namespace to the source, rename the column with the **AS** _alias_ statement since the function **does not support** fully qualified secret names.
0 commit comments