DanielLeens commented on PR #11953: URL: https://github.com/apache/seatunnel/pull/11953#issuecomment-5451420715
@davidzollo +1 to that direction — I checked `docs/en/getting-started/recipes` on `dev` and it's already the established home for exactly this kind of end-to-end walkthrough (e.g. `jdbc-to-s3.md`, `mysql-cdc-to-doris.md`): a single self-contained Markdown page with prerequisites, an embedded job config, and expected output, rather than a standalone `.conf`/`.sql` pair under `seatunnel-examples/`. Moving this there should give it a lot more visibility than a resource file buried in `seatunnel-engine-examples`. @lce-mo on the technical side, the good news is there's nothing left to re-derive: I've already verified end-to-end (current head `73d213cc7`, CI green) that the JDBC source options, the `date(create_time)` + `FORMATDATETIME(create_date, 'yyyy-MM-dd')` transform, the `plugin_input`/`plugin_output` linkage, and the HdfsFile partitioned-Parquet sink config all check out against current source. If you rework this into a `recipes/mysql-to-hdfs.md`-style page (prerequisites section, embedded config block, embedded seed SQL, expected-output section — similar shape to `jdbc-to-s3.md`), the underlying config content can carry over as-is; it's just a presentation change. Happy to take another look once the recipe version is up. -- 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]
