JDBC Driver for Athena to include S3 file paths

Question

Hi All,

I came across a support article How to register a JDBC Driver for Athena to include S3 file paths – Support Portal (collibra.com) that describes a possibility to configure the Jobserver’s JDBC driver for Athena to ingest S3 file path into the Collibra Data Catalog. Have you tried if this process would work for Edge too?
I have tried to add the ShowS3Filepathparameter into the Athena Edge connection and it registered an asset named _S3Path for every table but the s3 file path is not present in the catalog so I’m wondering if there is some configuration that I’m missing?

Thomas Deschepper · Answer

We are having the same problem with the AWS Glue Data Catalog connector (which uses the Athena JDBC Driver). _S3Path just turns up empty. Asides from the obvious problem that we do not get an S3 path for our tables, we struggle to understand: Why we need to have “Store sample data” checked prior to an ingestion/refresh. S3 paths have nothing to do with sampling in our view (cfr https://support.collibra.com/hc/en-us/articles/4410279899415-How-to-register-a-JDBC-Driver-for-Athena-to-include-S3-file-paths ) Why the _S3Path is modeled as a Column in Collibra. For every table, the column count is now confusing as the actual amount of columns is always minus the fake _S3Path. Any idea why the S3 path is not simply added as an Attribute to the Table asset?

1	Grant Rollerson SUNCORP CORPORATE SERVICES PTY LTD
2	Tom Friesen Algonquin College
3	SB S Benson Plus3 IT
4	S stefan_busch
5	Brian Lloyd USA TODAY Co.
6	D daverichard