Alberne commented on issue #9500: URL: https://github.com/apache/seatunnel/issues/9500#issuecomment-3200580544
> Why not use SPI? The algorithm logic will not change much, so there is no need to rewrite it in every config file. Using SPI to load custom algorithms may be more universal. hi @Hisoka-X Thank you for your suggestions. I chose the **dynamicCompileCode** approach primarily based on two key considerations: 1. **Practical Scenario**: We integrate with over a dozen third-party OpenAPIs, 80% of which require distinct signature algorithms. The **dynamicCompile** solution enables "code-as-configuration", allowing users to implement custom signatures without modifying the Seatunnel project code. This eliminates the need to download the project, build JARs, or redeploy. 2. **User Experience**: For other Seatunnel users, the "code-as-configuration" approach is far more user-friendly, as it simplifies customization while maintaining flexibility. -- 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]
