DanielLeens commented on issue #11007: URL: https://github.com/apache/seatunnel/issues/11007#issuecomment-6168243222
Classification: I / Declarative OptionRule migration tracking. I rechecked current `dev` and the open PR set before handling the new CDC and HTTP claims. * @1328837476-hug: the HTTP Sink factory requires `url` for presence but does not apply a nonblank condition. This narrow factory-only slice is available. Add `Conditions.notBlank(URL)`, focused valid/missing/empty/whitespace/padded-value tests, and matching documentation only if the existing option contract needs clarification. Do not change URL parsing, placeholder behavior, HTTP execution, retry behavior, or runtime connectivity checks. * @ZYZ666-RGB: the exact SQL Server CDC URL slice is now tracked by #12764. Please keep that as the single implementation and CI surface; do not open a second PR for the same rule. * @Nikk8091: DB2 and Postgres CDC each require a URL for presence without a nonblank condition, and no exact validation PR is open for either. The two source-only slices are available, but they must stay as separate PRs. For each, preserve table selection, startup/stop semantics, parsing, credentials, connection/retry behavior, and runtime checks; cover valid, missing, empty, whitespace-only, and padded nonblank URLs, then align the EN/ZH documentation with the final rule. * @ryanmeowy: #12746 already covers the Vitess structural-validation scope and its Build is in progress, so please continue only there for Vitess. The Oracle validation follow-up must wait for #12736: that PR currently changes `OracleIncrementalSourceFactory`, its tests, and the Oracle CDC documentation. After it merges, recheck the current source before proposing a narrow, non-overlapping Oracle rule-only PR. The assignments below record the currently claimed tracker ownership. Please link each focused PR back to this issue and leave unrelated runtime or external-system validation in its existing runtime path. -- 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]
