[ https://issues.apache.org/jira/browse/FLINK-17892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17115653#comment-17115653 ]
hailong wang commented on FLINK-17892: -------------------------------------- Yes, it is right to define two kakfa source and use different group id. But I think, by this, users need to understand the meaning, which is not very flexible. > Dynamic option may not be a part of the table digest > ---------------------------------------------------- > > Key: FLINK-17892 > URL: https://issues.apache.org/jira/browse/FLINK-17892 > Project: Flink > Issue Type: Improvement > Components: Table SQL / Planner > Affects Versions: 1.11.0 > Reporter: hailong wang > Priority: Major > Attachments: image-2020-05-25-10-47-18-829.png, > image-2020-05-25-10-50-53-033.png > > > For now, Table properties not be a part of table digest, but dynamic option > will be included. > This will lead to an error when plan reused. > if I defines a kafka table: > {code:java} > CREATE TABLE KAFKA ( > …… > ) with ( > topic = 'xx', > groupid = 'xxx' > …… > ) > Insert into sinktable select * from KAFKA; > Insert into sinktable1 select * from KAFKA;{code} > KAFKA source will be reused according to the SQL above. > But if i add different table hint to dml, like: > {code:java} > Insert into sinktable select * from KAFKA /*+ OPTIONS('k1' = 'v1')*/; > Insert into sinktable1 select * from KAFKA /*+ OPTIONS('k2' = 'v2')*/; > {code} > There will be two kafka tableSources use the same groupid to consumer the > same topic. > So I think dynamic option may not be a part of the table digest. -- This message was sent by Atlassian Jira (v8.3.4#803005)