Hi all, I heard some users complain that table is difficult to test. Now with SQL client, users are more and more inclined to use it to test rather than program. The most common example is Kafka source. If users need to test their SQL output and checkpoint, they need to:
- 1.Launch a Kafka standalone, create a Kafka topic . - 2.Write a program, mock input records, and produce records to Kafka topic. - 3.Then test in Flink. The step 1 and 2 are annoying, although this test is E2E. Then I found StatefulSequenceSource, it is very good because it has deal with checkpoint things, so it is very good to checkpoint mechanism.Usually, users are turned on checkpoint in production. With computed columns, user are easy to create a sequence source DDL same to Kafka DDL. Then they can test inside Flink, don't need launch other things. Have you consider this? What do you think? CC: @Aljoscha Krettek <aljos...@apache.org> the author of StatefulSequenceSource. Best, Jingsong Lee
