SEZ9 commented on issue #9785:
URL: https://github.com/apache/seatunnel/issues/9785#issuecomment-5658386910

   @goutamadwant thanks for opening the two PRs for ClickHouse `TIMESTAMP_TZ` 
writes and Iceberg `custom_sql` delete predicates. Capability-scoped PRs are 
fine as long as each stays within a single connector, in line with the one 
source/sink per PR approach @Hisoka-X suggested earlier.
   
   On tracking: I would prefer a connector/capability checklist maintained 
directly in this issue over separate linked issues. One row per 
connector/capability with contributor, status and linked PR keeps the umbrella 
readable. If a connector needs a longer design discussion, we can spin it out 
into its own issue and link it back here.
   
   As @dybyte noted, only some of the underlying databases natively support a 
timestamp-with-time-zone type, so the checklist should also mark connectors 
that are out of scope on the database side so nobody picks them up by mistake.
   
   Concrete asks:
   - @goutamadwant, could you post the checklist as a comment here (connector, 
read/write capability, contributor, status, PR)? Once it looks right I will 
move it into the issue description and keep it updated as PRs land.
   - @hohosznta, please add yourself to the Kafka Source row once the checklist 
is up.
   - @yzeng1618, if you are still interested, pick a connector from the list 
and claim it the same way.
   - Everyone opening a PR for this: please link it back to this issue so the 
checklist stays in sync.
   
   This issue stays open until the wider source/sink coverage is complete.
   
   <!-- streview-comment:1033 -->


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