corgy-w opened a new issue, #7291: URL: https://github.com/apache/seatunnel/issues/7291
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22bug%22) and found no similar issues. ### What happened I spotted top issue and wanted to try it, so I chose a simple mail sink, a simple operation, and threw an error `Action name is duplicated:`. ps: refer to other people's pr, I just modified interface implementation. `SupportMultiTableSink`,`SupportMultiTableSinkWriter` help me :< of course I'm still looking at this part code. ### SeaTunnel Version dev ### SeaTunnel Config ```conf env { parallelism = 1 job.mode = "BATCH" } source { FakeSource { tables_configs = [ { row.num = 3 schema = { table = "test.table1" columns = [ { name = id type = bigint } { name = name type = string } { name = age type = int } ] } }, { row.num = 3 schema = { table = "test.table2" columns = [ { name = id type = bigint } { name = name type = string } { name = age type = int } ] } } ] } } sink{ EmailSink { email_from_address = "[email protected]" email_to_address = "[email protected]" email_host="smtp.qq.com" email_transport_protocol="smtp" email_smtp_auth="true" email_authorization_code="tsssssssbigh" email_message_headline="test-title" email_message_content="test-content" } } ``` ### Running Command ```shell - ``` ### Error Exception ```log java.lang.IllegalArgumentException: Action name is duplicated: [pipeline-1 [Sink[0]-EmailSink]] two identical pipelines ？ ``` ### Zeta or Flink or Spark Version _No response_ ### Java or Scala Version _No response_ ### Screenshots _No response_ ### Are you willing to submit PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
