Support for Trino/Presto in DatabaseConnector/Achilles and Atlas

Developers
1

We have deployed the Trino query engine (https://trino.io/) on our servers in a cluster and have been impressed with both the speed as well as the ability to query various data sources (HDFS, Postgres, Snowflake) all thru one engine and connection.

We are looking to see what it would take to add Trino support to the DBConnector package, thru either direct JDBC connection or thru a DBI based connection. RPresto is a developed package that is compliant with DBI (https://github.com/prestodb/RPresto)

Looking at the source code it seems like it would be a relatively straightforward task to add the backend support. I was hoping to get some guidance on what it would be like for adding a new database support or other contributor guidelines.

While this is specifically for the first step of getting an Atlas compliant CDM queryable thru Trino, would the changes to Atlas be as robust or would simply adding the jars and dependencies akin to Snowflake be enough?

Thanks in advance.

Best,
Alex

2

Hi @alex_chop !

The OHDSI tools use advanced database analytics (ie. more than just SELECT * FROM table WHERE …), and adding support for a new database platform is therefore non-trivial. It requires both a major investment from the party seeking to have a new platform and from the OHDSI developers. I therefore strongly recommend not trying to get a new platform supported.

The good news is that the OHDSI tools already support a whopping 11 database platforms! This includes all flavors of platforms, from small-scale open-source to massive parallel computing environments. I highly recommend picking one of those, and moving the data there.

Should you still be interested in pursuing support for a new database platform, your uphill battle starts with the HADES Database Platform Support Policy.