SEZ9 commented on issue #11007: URL: https://github.com/apache/seatunnel/issues/11007#issuecomment-5964522903
@Nikk8091 @yigitcan-ozturk thanks for the update on #12603 and for confirming the scope stays limited to the IoTDB Source-only `sql` nonblank validation (optional root-level `sql`, exclusivity with `tables_configs` preserved, plus the factory tests and EN/ZH doc alignment). That matches the agreed slice, so please keep it exactly there. On the Build: since the workflow for #12603 runs on the Nikk8091 fork, @Nikk8091 is the one who can re-trigger it. Pushing a rebase onto current `dev` (or an empty commit) will start a fresh run; alternatively re-run the failed job from the Actions tab of the fork. If the Docusaurus step times out again on the retry, please note that in the PR so it can be distinguished from a problem in the connector change itself. Remaining asks before we move to implementation review: 1. @Nikk8091: re-run the Build on #12603 and post back once it is no longer `TIMED_OUT`. 2. Keep the PR limited to the validation/test/documentation boundary described above — no MaxCompute, Paimon, or other connector changes folded in. 3. In the PR description, briefly list the covered cases (valid root SQL with schema, empty/whitespace-only root SQL rejected, padded nonblank accepted unchanged, valid `tables_configs` with root SQL absent) so the reviewer can map them to the tests. <!-- streview-comment:1480 --> -- 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]
