-
Notifications
You must be signed in to change notification settings - Fork 296
Add support for Trino #155
Conversation
@erezsh Fixed the Poetry dependencies which caused the CI job to fail. |
Hi @danthelion , thanks for making a contribution! The next step is be to add Trino to the A few points:
We're going to write a comprehensive guide for contributors real soon. But meanwhile, if you have any questions at all, I'll be happy to answer them. |
Looks like the port is already used. Perhaps by Presto? |
Just one note about the PR, please make trino optional, like the rest. i.e. trino = { version = "^0.314.0", optional = true } |
@erezsh Mapped the port to 8081 instead, Presto was indeed conflicting. Also added the Trino lib as optional and rebased to master. |
ca37e77
to
cb8c943
Compare
Hi @danthelion , I opened a new PR to fix a few minor things and to make sure the tests run in the CI. (#162 ) I'm getting this error from Trino:
(See here: https://github.com/datafold/data-diff/runs/7309529815?check_suite_focus=true) I don't have this issue when I run it locally. Any idea what's the problem and how to fix it? |
P.S. I'm using |
@erezsh thanks for looking into this! I added the fixes to this branch. Could you try running the CI with |
Keep in mind these tests are still running with |
Now I'm getting Does it mean it couldn't find the server? |
But it's happening here:
|
Weird, in the py3.8 test suite the Presto connection fails. Could you check the connection strings for both? |
Add support for Trino (Merge PR #155)
I gave up getting this into the CI. I tested it on my machine and that's good enough for now. If you want to help us get Trino tests into the CI, please open a new PR. I think that the problem is running both the Presto and Trino servers at the same time; they step on each others' toes. |
Mainly based on the Presto integration to serve as a starting point for future development.