[ 
https://issues.apache.org/jira/browse/FLINK-20121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17235996#comment-17235996
 ] 

Shengkai Fang edited comment on FLINK-20121 at 11/20/20, 8:39 AM:
------------------------------------------------------------------

E2E Test
Env: 
 
||name||mode||version||
| mysql | docker | 5.7 |
| kafka | docker | 2.12 |
| flink| local stand alone | 1.12 

Scenario:
 Scenario 1 - sync database using upsert-kafka
 # read from mysql binlog and insert into upsert-kafka

Scenario 2 - join multiple streams for enrichment
 # kafka TEMPORAL JOIN upsert-kafka and use upsert-kafka as sink
 # kafka LEFT JOIN upsert-kafka and upsert-kafka and use upsert-kafka as sink
 # upsert-kafka LEFT JOIN upsert-kafka and use upsert-kafka as sink

Scenario 3 - aggregate on upsert-kafka
 # aggregate over the WINDOW on the upsert-kafka and write into upsert-kafka
 # aggregate on the upsert-kafka and write into upsert-kafka
 # special agg: topN, rank 

I almost cover the  Scenario 1 and  Scenario 2 by sql-client. 



was (Author: fsk119):
E2E Test
Env: 
 
||name||mode||version||
| mysql | docker | 5.7 |
| kafka | docker | 2.12 |
| flink| local stand alone | 1.12 

Scenario:
 Scenario 1 - sync database using upsert-kafka
 # read from mysql binlog and insert into kafka

Scenario 2 - join multiple streams for enrichment
 # kafka TEMPORAL JOIN upsert-kafka and use upsert-kafka as sink
 # kafka LEFT JOIN upsert-kafka and upsert-kafka and use upsert-kafka as sink
 # upsert-kafka LEFT JOIN upsert-kafka and use upsert-kafka as sink

Scenario 3 - aggregate on upsert-kafka
 # aggregate over the WINDOW on the upsert-kafka and write into upsert-kafka
 # aggregate on the upsert-kafka and write into upsert-kafka
 # special agg: topN, rank 

I almost cover the  Scenario 1 and  Scenario 2 by sql-client. 


> Test the upsert-kafka Connector
> -------------------------------
>
>                 Key: FLINK-20121
>                 URL: https://issues.apache.org/jira/browse/FLINK-20121
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table SQL / Ecosystem
>    Affects Versions: 1.12.0
>            Reporter: Robert Metzger
>            Assignee: Shengkai Fang
>            Priority: Critical
>             Fix For: 1.12.0
>
>
> ----
> [General Information about the Flink 1.12 release 
> testing|https://cwiki.apache.org/confluence/display/FLINK/1.12+Release+-+Community+Testing]
> When testing a feature, consider the following aspects:
> - Is the documentation easy to understand
> - Are the error messages, log messages, APIs etc. easy to understand
> - Is the feature working as expected under normal conditions
> - Is the feature working / failing as expected with invalid input, induced 
> errors etc.
> If you find a problem during testing, please file a ticket 
> (Priority=Critical; Fix Version = 1.12.0), and link it in this testing ticket.
> During the testing keep us updated on tests conducted, or please write a 
> short summary of all things you have tested in the end.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to