Dbeaver and AWS S3 Tables limitations

[smafra]

While DBeaver Community Edition can connect to Amazon Athena, it currently has limitations when working with S3 Tables. There is an issue where it´s not possible to see catalogs other than AwsDataCatalog in the treeview.

However you can still query S3 Tables using SQL scripts directly. This is because S3 Tables use a separate catalog from the default AWS Glue Data Catalog, which is why you need to specify the full path including the s3tablescatalog in your queries.

To work with S3 Tables in DBeaver:

• Ensure you're using the latest Athena JDBC driver, which you've already done.
• Connect to Athena as you normally would in DBeaver.
• Instead of relying on the treeview, you'll need to write your queries manually, specifying the full path to your S3 Tables. For example:
• SELECT * FROM "s3tablescatalog/".""."" LIMIT 10;
• You can create SQL scripts in DBeaver with these queries to work with your S3 Tables.

Remember to use the correct catalog name (s3tablescatalog/), namespace, and table name in your queries.

While this method requires more manual input compared to using the treeview, it allows you to continue using DBeaver with S3 Tables. Keep in mind that as S3 Tables is a relatively new feature, tool support may improve in future updates to DBeaver or the Athena JDBC driver.

When can we get this limitation over?