[flink-table-store] branch master updated: [hotfix] Add note for testing immediate data with sql-client

[lz...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

lzljs3620320 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/flink-table-store.git


The following commit(s) were added to refs/heads/master by this push:
     new 1a69ba80 [hotfix] Add note for testing immediate data with sql-client
1a69ba80 is described below

commit 1a69ba80d34d5578655aaff7b1c88c46f46d17f6
Author: JingsongLi <lz...@aliyun.com>
AuthorDate: Tue Aug 2 10:33:24 2022 +0800

    [hotfix] Add note for testing immediate data with sql-client
---
 docs/content/docs/development/streaming-query.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/docs/content/docs/development/streaming-query.md b/docs/content/docs/development/streaming-query.md
index 532e8b13..2b47a27e 100644
--- a/docs/content/docs/development/streaming-query.md
+++ b/docs/content/docs/development/streaming-query.md
@@ -130,6 +130,11 @@ that the streaming reading has transactional consistency.
 Immediate data visibility is configured via
 `log.consistency` = `eventual`.
 
+{{< hint info >}}
+__Note:__ Use `SELECT` in the sql-client does not get immediate data, the collect sink generated by select relies
+on the checkpoint mechanism. The more recommended way to test is to use a print sink.
+{{< /hint >}}
+
 Due to the tradeoff between data freshness and completeness, immediate data visibility is barely
 accomplished under exactly-once semantics. Nevertheless, users can relax the constraint to use
 at-least-once mode to achieve it. Note that records may be sent to downstream jobs ahead of the committing