Supported Dialects

May 28, 2026 ยท View on GitHub

Dialect nameSourceTypeRepositoryLatest release
AthenaAWSJDBCAthena Virtual SchemaLatest release
AuroraAWSJDBCSee MySQL or PostgreSQL VS (interface-compatible)
Azure Blob Storage document filesMicrosoftdocumentAzure Blob Storage document files Virtual SchemaLatest release
Azure Data Lake Storage Gen2 document filesMicrosoftdocumentAzure Data Lake Storage Gen2 document files Virtual SchemaLatest release
BucketFS document filesExasoldocumentBucketFS document files Virtual SchemaLatest release
DatabricksDatabricksJDBCDatabricks virtual SchemaLatest release
DB2IBMJDBCDB2 Virtual SchemaLatest release
Dynamo DBAWSdocumentDynamo DB Virtual SchemaLatest release
ElasticSearchJDBCElasticSearchLatest release
ExasolExasolJDBC *)Exasol Virtual SchemaLatest release
Google Big QueryGoogleJDBCBig Query Virtual SchemaLatest release
Google Cloud Storage document filesGoogledocumentGoogle Cloud Storage document files Virtual SchemaLatest release
HANASAPJDBCHana Virtual SchemasLatest release
HiveApacheJDBCHive Virtual SchemasLatest release
ImpalaApacheJDBCImpala Virtual SchemaLatest release
MySQLJDBCMySQL Virtual SchemaLatest release
OracleOracleJDBCOracle Virtual SchemaLatest release
PostgreSQLJDBCPostgreSQL Virtual SchemaLatest release
RedshiftAWSJDBCRedshift Virtual SchemaLatest release
S3 document filesAWSdocumentS3 document files Virtual SchemaLatest release
SnowflakeSnowflakeJDBCSnowflake Virtual SchemaLatest release
SQL ServerMicrosoftJDBCSQL Server Virtual SchemaLatest release
Sybase ASESybaseJDBCSybase Virtual SchemaLatest release

*) The Virtual Schema for Exasol databases supports three connection variants in total:

  • Import from JDBC
  • Using EXA Import
  • Using IS_LOCAL

If your database is not part of that list but provides a JDBC driver, you can develop a custom dialect.