You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@seatunnel.apache.org by "Hisoka-X (via GitHub)" <gi...@apache.org> on 2025/08/28 06:56:25 UTC
[I] [Feature][Connector-V2] Source/Sink support read/write TIMESTAMP_TZ [seatunnel]
Hisoka-X opened a new issue, #9785:
URL: https://github.com/apache/seatunnel/issues/9785
### Search before asking
- [x] I had searched in the [feature](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22Feature%22) and found no similar feature requirement.
### Description
After #8367 and #9784 . We support transform timestamp with time zone in sql transform and write into jdbc sink.
We should support read timestamp with time zone type from all source which support this type. And write into all sink which support this type.
This is a ticket that tracks all sources and sinks. However, you can have one PR address the functionality of one connector at a time.
### Usage Scenario
_No response_
### Related issues
_No response_
### Are you willing to submit a PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
--
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: commits-unsubscribe@seatunnel.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature][Connector-V2] Source/Sink support read/write TIMESTAMP_TZ [seatunnel]
Posted by "dybyte (via GitHub)" <gi...@apache.org>.
dybyte commented on issue #9785:
URL: https://github.com/apache/seatunnel/issues/9785#issuecomment-3400684503
Among the databases supported by seatunnel connectors,
it seems that only a few actually support the TIMESTAMP_TZ type natively.
Am I missing something? @Hisoka-X
--
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: commits-unsubscribe@seatunnel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature][Connector-V2] Source/Sink support read/write TIMESTAMP_TZ [seatunnel]
Posted by "yzeng1618 (via GitHub)" <gi...@apache.org>.
yzeng1618 commented on issue #9785:
URL: https://github.com/apache/seatunnel/issues/9785#issuecomment-3252886196
I can take some time to give it a try. However, since it involves a relatively large number of sources and sinks, this will be a long-term feature.
--
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: commits-unsubscribe@seatunnel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature][Connector-V2] Source/Sink support read/write TIMESTAMP_TZ [seatunnel]
Posted by "dybyte (via GitHub)" <gi...@apache.org>.
dybyte commented on issue #9785:
URL: https://github.com/apache/seatunnel/issues/9785#issuecomment-3420050495
> You mean seatunnel side or database side?
It means database side.
--
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: commits-unsubscribe@seatunnel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature][Connector-V2] Source/Sink support read/write TIMESTAMP_TZ [seatunnel]
Posted by "hohosznta (via GitHub)" <gi...@apache.org>.
hohosznta commented on issue #9785:
URL: https://github.com/apache/seatunnel/issues/9785#issuecomment-3397655993
Hello, I would like to contribute by working on the Kafka Source.
--
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: commits-unsubscribe@seatunnel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature][Connector-V2] Source/Sink support read/write TIMESTAMP_TZ [seatunnel]
Posted by "SEZ9 (via GitHub)" <gi...@apache.org>.
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: commits-unsubscribe@seatunnel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature][Connector-V2] Source/Sink support read/write TIMESTAMP_TZ [seatunnel]
Posted by "goutamadwant (via GitHub)" <gi...@apache.org>.
goutamadwant commented on issue #9785:
URL: https://github.com/apache/seatunnel/issues/9785#issuecomment-5648799643
Opened #12285 for ClickHouse scalar `TIMESTAMP_TZ` writes and key predicates, and #12286 for Iceberg offset-aware `custom_sql` delete predicates. Both are validated on Java 8 and 11.
Since this issue already tracks the broader feature, could we maintain a connector/capability checklist here with contributor, status and linked PRs, similar to #10753? These two PRs cover specific capabilities rather than complete connector support.
@davidzollo @zhangshenghang would you prefer separate linked issues for the remaining work, or checklist entries linked directly to PRs? I can help put together the coverage checklist and keep it updated.
--
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: commits-unsubscribe@seatunnel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature][Connector-V2] Source/Sink support read/write TIMESTAMP_TZ [seatunnel]
Posted by "Hisoka-X (via GitHub)" <gi...@apache.org>.
Hisoka-X commented on issue #9785:
URL: https://github.com/apache/seatunnel/issues/9785#issuecomment-3419377725
> it seems that only a few actually support the TIMESTAMP_TZ type natively.
You mean seatunnel side or database side?
--
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: commits-unsubscribe@seatunnel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature][Connector-V2] Source/Sink support read/write TIMESTAMP_TZ [seatunnel]
Posted by "SEZ9 (via GitHub)" <gi...@apache.org>.
SEZ9 commented on issue #9785:
URL: https://github.com/apache/seatunnel/issues/9785#issuecomment-5650470803
Thanks @goutamadwant for opening #12285 and #12286, and for offering to help maintain a coverage checklist.
A checklist in this issue with connector/capability, contributor, status, and linked PRs sounds helpful for avoiding duplicated work. Based on the thread so far, it should already reflect: JDBC support from #8367/#9784, the remaining JDBC `TIMESTAMP_TZ` types in #11485 (@DanielLeens), Kafka Source (@hohosznta), ClickHouse (#12285), and Iceberg (#12286).
@Hisoka-X @davidzollo, could you confirm whether you prefer checklist entries linked directly to PRs here, or separate linked issues for the remaining work? Once decided, contributors can comment here before starting on a connector so it can be marked as claimed, keeping to one connector per PR.
<!-- streview-comment:1008 -->
--
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: commits-unsubscribe@seatunnel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature][Connector-V2] Source/Sink support read/write TIMESTAMP_TZ [seatunnel]
Posted by "goutamadwant (via GitHub)" <gi...@apache.org>.
goutamadwant commented on issue #9785:
URL: https://github.com/apache/seatunnel/issues/9785#issuecomment-5648768608
Prepared #12285 for scalar `TIMESTAMP_TZ` writes and key predicates on existing tables. @DanielLeens @zhangshenghang can you please review when you get a chance?
--
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: commits-unsubscribe@seatunnel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature][Connector-V2] Source/Sink support read/write TIMESTAMP_TZ [seatunnel]
Posted by "davidzollo (via GitHub)" <gi...@apache.org>.
davidzollo commented on issue #9785:
URL: https://github.com/apache/seatunnel/issues/9785#issuecomment-5014373933
@DanielLeens is doing the left connectors
--
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: commits-unsubscribe@seatunnel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature][Connector-V2] Source/Sink support read/write TIMESTAMP_TZ [seatunnel]
Posted by "Hisoka-X (via GitHub)" <gi...@apache.org>.
Hisoka-X commented on issue #9785:
URL: https://github.com/apache/seatunnel/issues/9785#issuecomment-3253970685
> I can take some time to give it a try. However, since it involves a relatively large number of sources and sinks, this will be a long-term feature.
We can support one source/sink in per PR.
--
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: commits-unsubscribe@seatunnel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature][Connector-V2] Source/Sink support read/write TIMESTAMP_TZ [seatunnel]
Posted by "DanielLeens (via GitHub)" <gi...@apache.org>.
DanielLeens commented on issue #9785:
URL: https://github.com/apache/seatunnel/issues/9785#issuecomment-5017985129
Thanks for calling out the current status.
This issue is still useful as the umbrella tracker for broader `TIMESTAMP_TZ` source/sink support. At this point it is no longer just an open-ended request: some connector work has already landed, and the remaining JDBC-side coverage is currently being worked on in PR #11485.
That said, PR #11485 only covers the remaining JDBC `TIMESTAMP_TZ` types, so this issue should stay open until the wider connector coverage is complete.
For anyone who wants to help, the right way to move this forward is still one connector per PR, so additional source/sink follow-up contributions are very welcome.
--
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: commits-unsubscribe@seatunnel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org