yyanyy commented on a change in pull request #2147:
URL: https://github.com/apache/iceberg/pull/2147#discussion_r564784008
##########
File path: site/docs/flink.md
##########
@@ -224,24 +225,49 @@ DROP TABLE hive_catalog.default.sample;
## Querying with SQL
-Iceberg does not support streaming read in flink now, it's still working
in-progress. But it support batch read to scan the existing records in iceberg
table.
+Iceberg support both streaming and batch read in flink now. we could execute
the following sql command to switch the execute type from 'streaming' mode to
'batch' mode, and vice versa:
+
+```sql
+-- Execute the flink job in streaming mode for current session context
+SET execution.type = streaming
+
+-- Execute the flink job in batch mode for current session context
+SET execution.type = batch
+```
+
+### Flink batch read
+
+If want to check all the rows in iceberg table by submitting a flink __batch__
job, you could execute the following sentences:
```sql
-- Execute the flink job in batch mode for current session context
SET execution.type = batch ;
SELECT * FROM sample ;
```
-Notice: we could execute the following sql command to switch the execute type
from 'streaming' mode to 'batch' mode, and vice versa:
+### Flink streaming read
+
+Iceberg supports processing incremental data in flink streaming jobs which
starts from a historical snapshot-id:
```sql
--- Execute the flink job in streaming mode for current session context
-SET execution.type = streaming
+-- Submit the flink job in streaming mode for current session.
+SET execution.type = streaming ;
--- Execute the flink job in batch mode for current session context
-SET execution.type = batch
+-- Enable this switch because streaming read SQL will provide few job options
in flink SQL hint options.
+SET table.dynamic-table-options.enabled=true;
Review comment:
Is this to ensure `OPTIONS(...)` in the commands below will not be
disregard by flink? If so "requires" might be better than "will provide". Also
after `'streaming'='true'` is no longer needed in options, what if we don't
specify options at all (or we don't specify 'monitor-interval'='1s' now)? Does
it default to some value, or it will just not work?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
