DanielLeens commented on PR #11953:
URL: https://github.com/apache/seatunnel/pull/11953#issuecomment-5522160184

   @nzw921rx Agreed — this lines up with what @davidzollo suggested a few days 
ago and what I confirmed in my follow-up comment above: 
`seatunnel-engine-examples` is meant as a fast local-startup debugging 
resource, not a user-facing tutorial location, so a walkthrough like this one 
(MySQL -> transform -> HDFS partitioned Parquet) is a better fit for 
`docs/en/getting-started/recipes` (with a `docs/zh` counterpart, per project 
convention — both directories already exist and hold the same set of recipe 
pages, e.g. `jdbc-to-s3.md` / `mysql-cdc-to-doris.md`).
   
   @lce-mo to be clear on where things stand so you don't have to re-derive 
anything: 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 in this PR are already technically correct and CI-green (verified 
end-to-end against the current head `73d213cc7`). This is purely a 
presentation/location change at this point — if you rework the content into a 
`recipes/mysql-to-hdfs.md`-style page under `docs/en/getting-started/recipes` 
(prerequisites section, embedded job config, embedded seed SQL, expected-output 
section, similar shape to `jdbc-to-s3.md`), plus the matching `docs/zh` page, 
the config content can carry over as-is. Happy to take another look once that's 
up — thanks for sticking with this!
   


-- 
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]

Reply via email to