Is there still interest in a Trino2Trino connector? (Ref #21791) #29097
kkd927
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Trino community and maintainers,
I've been very interested in the Trino2Trino connector discussed in issue #21791. However, it seems there hasn't been much recent activity on that thread. I wanted to carefully ask: is there still a need or interest within the Trino community for an upstream Trino-to-Trino connector?
Since I personally needed this for cross-cluster federated queries without data duplication, I went ahead and built a working prototype for my own use. It is largely based on the ideas and requirements discussed in the original issue.
My current implementation is available here: kkd927/trino2trino
To give a brief overview of the current prototype:
count,count distinct,min,max,sum,avg), and some same-remote join shapes.system.querypassthrough table function for row-returning read queries, so remote Trino SQL can be executed directly when connector-level pushdown is not expressive enough.SHOW STATS FOR <table>to provide table statistics to the local planner when available.I am currently using this in my own environment, and it has been useful for my use cases so far.
If this still seems aligned with the project direction, I would be happy to open a Draft PR with the current implementation.
Even at this early stage, I would greatly appreciate any advice, feedback, or guidance on the architectural direction. I want to make sure it aligns with the project's standards before pushing further.
Thank you for your time and for all the great work on Trino.
Beta Was this translation helpful? Give feedback.
All reactions