Releases: exasol/virtual-schemas
Join pushdown for Oracle dialect
Summary
The JDBC Adapter can now handle join pushdowns for the Oracle dialect, Keep in mind that the Exasol database generates join pushdowns from version 6.2 on. Furthermore Exasol version 6.1.2 / 6.0.15 or later is required for this version of the JDBC adapter, If you use an older version of Exasol, you have to add the JOIN capabilities to the EXCLUDED_CAPABILITIES:
excluded_capabilities='JOIN,JOIN_TYPE_INNER,JOIN_TYPE_LEFT_OUTER,JOIN_TYPE_RIGHT_OUTER,JOIN_TYPE_FULL_OUTER,JOIN_CONDITION_EQUI'
Changes
- #150 Enable Join pushdown for Oracle dialect
Join pushdown for PostgreSQL dialect
Summary
The JDBC Adapter can now handle join pushdowns for the PostgreSQL dialect, Keep in mind that the Exasol database generates join pushdowns from version 6.2 on. Furthermore Exasol version 6.1.2 / 6.0.15 or later is required for this version of the JDBC adapter, If you use an older version of Exasol, you have to add the JOIN capabilities to the EXCLUDED_CAPABILITIES:
excluded_capabilities='JOIN,JOIN_TYPE_INNER,JOIN_TYPE_LEFT_OUTER,JOIN_TYPE_RIGHT_OUTER,JOIN_TYPE_FULL_OUTER,JOIN_CONDITION_EQUI'
Changes
- #151: Enable Join pushdown for PostgreSQL
Bugfix: Table filter in refresh requests
Summary
This release fixes a bug where instead for selected tables the metadata of all tables was refreshed in case of an ALTER VIRTUAL SCHEMA statement.
Changes
- #171: Bugfix: Table filter in refresh request
AWS Athena support
Summary
With this release Exasol's Virtual Schemas support Amazon's AWS Athena, a managed service derived from the Open Source distributes SQL query engine Presto.
This allows users to query file-based data stores (e.g. CSV and Parquet) stored on S3.
Changes
- #156: AWS Athena support
Join pushdown for Exasol dialect
Summary:
The JDBC Adapter can now handle join pushdowns for the Exasol dialect, Keep in mind that the Exasol database generates join pushdowns from version 6.2 on. Furthermore Exasol version 6.1.2 / 6.0.15 or later is required for this version of the JDBC adapter, If you use an older version of Exasol, you have to add JOIN to the EXCLUDED_CAPABILITIES.
Changes:
- #149: Enable Join pushdown for Exasol
Redshift Spectrum support
Summary
With this release Exasol's Virtual Schemas support reading data not only from regular Amazon's AWS Redshift tables, but also from so-called "external tables" mapped via Redshift Spectrum.
Changes
- #124: Redshift Spectrum support
Refactoring: Remote metadata reading
Summary
This is a refactoring release, request dispatching and SQL dialect handling and remote metadata handling were modularized. A large number of Sonar findings was resolved.
Changes
- #45: Rewrote parts of the JDBC adapter to use the new
commoncode - #121: Used new request dispatching from
common - #123: Improved how schemas identify support for structural elements
- #131: Refactored metadata reading
- #147: Enabled Hive integration test
- #154: Rewrote documentation after refactoring
- #155: moved property validation logic to dialects
- #162: Automatically register SQL dialects
- #167: Fixed broken JavaDoc
Exasol Virtual Schema JDBC Adapter 1.8.1
Exasol Virtual Schema JDBC Adapter 1.6.0
- #93 documentation for PostgreSQL identifier handling
- #93 added POSTGRESQL_IDENTIFIER_MAPPING property
For details see: https://github.com/exasol/virtual-schemas/blob/master/jdbc-adapter/doc/sql_dialects/postgresql.md