Add Support for Trino Query Engine as CDM database store.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 151
- Forks
- 183
- Avg merge
- 14m
- Merged PRs (30d)
- 2
Description
We have deployed Trino trino.io as our query engine for our CDM data it has been incredible performant for us. Query times for complex queries have been improved as much as 50x. We are hoping to add support to Atlas in order to run it with that as the backing system in order to speed up Atlas performance.
There is a jdbc driver that can be used to send queries to the system.
I am wondering what steps would be need in order to add this as a possible CDM store? I have started to modify some of the other OHDSI packages, SqlRender, DatabaseConnector and Achilles to run against Trino as a first step and have been successful.
Any help or guidance would be greatly appreciated before I start diving into the code base.
Let me know if there is anything I can provide that can be helpful in terms of trino context.
Best,
Alex
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no WebAPI files, tests, or entry points. Start by mapping how the Java WebAPI selects and connects to a CDM store, using the Trino JDBC driver and the author's SqlRender, DatabaseConnector, and Achilles work as context. Done means a concrete implementation plan for Trino-backed CDM support and agreement on its required query coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, sql
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100