Skip to content

Commit db33d3e

Browse files
Apply suggestions from code review
Co-authored-by: Iain Cox <[email protected]> Signed-off-by: Philip Krauss <[email protected]>
1 parent 725aa92 commit db33d3e

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

use-timescale/tigerlake.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -321,7 +321,7 @@ data lake:
321321

322322
**Specify a different namespace**
323323

324-
Tables are created, by default in the the `timescaledb` namespace, use the `tigerlake.iceberg_namespace` property to specify a different namespace when starting the sync through the following statement:
324+
By default, tables are created in the the `timescaledb` namespace. To specify a different namespace when you start the sync, use the `tigerlake.iceberg_namespace` property. For example:
325325

326326
```sql
327327
ALTER TABLE my_hypertable SET (
@@ -333,8 +333,8 @@ data lake:
333333
**Specify a different Iceberg table name**
334334

335335
The table name in Iceberg is the same as the source table in $CLOUD_LONG.
336-
Some services do not allow mixed case or have other constraints for table names.
337-
With the `tigerlake.iceberg_table` property a different table name for the Iceberg table can be defined on sync start.
336+
Some services do not allow mixed case, or have other constraints for table names.
337+
To define a different table name for the Iceberg table at sync start, use the `tigerlake.iceberg_table` property. For example:
338338

339339
```sql
340340
ALTER TABLE Mixed_CASE_TableNAME SET (

0 commit comments

Comments
 (0)