[X] I had searched in the issues and found no similar issues.
What happened
When the project began loading the plugin, we encountered multiple jars during the search due to custom development(eg ⬇️:plugin-mapping.properties). I propose using a similarity algorithm to match the most appropriate jar. Please review the details, and I will submit the corresponding pr.
SeaTunnel Version
2.3.3 When I raised this issue, I found that 2.3.5 had already avoided this by throwing IllegalArgumentException
Search before asking
What happened
When the project began loading the plugin, we encountered multiple jars during the search due to custom development(eg ⬇️:plugin-mapping.properties). I propose using a similarity algorithm to match the most appropriate jar. Please review the details, and I will submit the corresponding pr.
SeaTunnel Version
2.3.3 When I raised this issue, I found that 2.3.5 had already avoided this by throwing IllegalArgumentException
SeaTunnel Config
Running Command
Error Exception
Zeta or Flink or Spark Version
No response
Java or Scala Version
No response
Screenshots
Are you willing to submit PR?
Code of Conduct