DanielLeens commented on issue #11007:
URL: https://github.com/apache/seatunnel/issues/11007#issuecomment-5602978737

   I rechecked current `dev`, factory rules, and the complete open PR set 
before deciding the new requests. No labels or formal assignees were changed.
   
   - @xinnyuli: Amazon SQS is not available. Both the source and sink already 
require nonblank `url` and `region` in current `dev`, so this would duplicate 
existing behavior.
   - @ZYZ666-RGB: Lance is now tracked by PR #12222. Please keep review 
discussion on that PR; do not open another claim.
   - @Nikk8091: SensorsData is available with one correction. `server_url` has 
no default and is consumed by the SDK config, so register it as required and 
nonblank. `consumer` has the existing `batch` default, so register it as 
optional and preserve console and batch semantics. Do not add format, SDK, or 
remote checks.
   - @Nikk8091: SelectDB Cloud is available. Add declarative nonblank 
validation only for the five already-required string options: `jdbc-url`, 
`load-url`, `cluster-name`, `username`, and `table.identifier`. Keep `password` 
optional and do not change writer, retry, 2PC, or network behavior.
   - @Nikk8091: SLS source and sink are available. The open SLS PR #12234 
concerns catalog-table return behavior, not factory validation; keep this claim 
in a separate connector-scoped PR and rebase before review. Validate only the 
five existing required strings on both factories, with no credential or remote 
checks.
   - @smoggy666: Druid is available. Register the existing optional `batchSize` 
option and reject zero or negative values at factory validation. Preserve the 
default and all writer, coordinator, and ingestion behavior; add focused 
default, positive, zero, and negative cases.
   
   Each accepted slice needs focused valid, missing, empty, and whitespace-only 
coverage where applicable, EN/ZH documentation that matches the option 
contract, and one linked PR per connector.
   


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