Skip to content

Releases: exasol/virtual-schemas

AWS Aurora support

29 Jul 10:20
1003573
Compare
Choose a tag to compare

Summary

In this release we added documentation on how to connect to the AWS service Amazon Aurora using the PostgreSQL dialect. We also unified the documentation for all dialects.

Changes

  • #235: Added documentation about connecting to Aurora
  • #235: Unified SQL dialect documentation

SAP HANA SQL dialect

27 Jun 12:21
17c7152
Compare
Choose a tag to compare

Summary

In this release we introduced a new SAP HANA SQL dialect. Please read the documentation for additional information about current data types' restrictions and how to use the dialect.

Changes

  • #205: Implemented and documented SAP HANA dialect
  • #220: Removed redis demo adapter.
  • #217: Excluded configuration-heavy dialect files from duplication checks
  • #213: Removed unsupported data types from BaseColumnMetadataReader

Improve robustness against misconfigured debug address

24 Jun 08:49
c71a928
Compare
Choose a tag to compare

Summary

Before this release, the validation of user-defined adapter properties threw an exception if the debug address was invalid. While this was nice in case of a CREATE VIRTUAL TABLE command, it blocked other commands from executing when the debug address was misconfigured — most notably DROP VIRTUAL TABLE.

Dropping should work under all circumstances though. We changed the behavior. If the debug address is misconfigured we now fall back to local logging, issue a warning in that local log and continue. This way you can always drop a Virtual Schema.

Changes

  • #115: DROP VIRTUAL SCHEMA now works even if debug output is misconfigured

Implemented new interface methods in JdbcAdapterFactory

19 Jun 08:40
dae3149
Compare
Choose a tag to compare

Summary

We extended AdapterFactory interface of virtual-schema-common with new methods which let you see the adapter's name and version as a logger's message. In this release those methods were implemented in JDBC adapter.

Changes

  • #207: implemented getAdapterVersion()
  • #207: implemented getAdapterName()

Kerberos & BigQuery fixes

12 Jun 11:30
f823908
Compare
Choose a tag to compare

Summary

This is a bugfix release that brings fixes for the BigQuery SQL dialect and reenables Kerberos authentication.

Changes

  • #196: Reenabled Kerberos authentication
  • #200: Removed duplicated documentation
  • #201: (BigQuery) Implemented BigQuery-specific ORDER BY without NULL sorting hint
  • #203: (BigQuery) Handle NULL values

Added Google Big Query SQL dialect

03 Jun 07:55
5cbe385
Compare
Choose a tag to compare

Summary

Virtual Schemas now support Google Big Query SQL dialect.

Changes

#189: implemented BigQuery SQL dialect

Improved query rewriting and property handling

29 May 05:41
abbe1b8
Compare
Choose a tag to compare

Summary

This is a refactoring release. We eliminated the class JdbcAdapterProperties and achieved that all dialects now take care of their own properties.

We modularized query rewriting and the construction of connection details for IMPORT commands that are created by query rewriting.

Changes

#180 Removed JdbcAdapterProperties, improved property handling and improved query rewriting

Fixed missing metadata refresh after SET PROPERTY

10 May 07:58
Compare
Choose a tag to compare

Summary

SET PROPERTY triggers a refresh of the metadata for some properties (e.g. schema_name). This was broken from version 1.10.0 on.

Changes

  • #175 SET PROPERTY does not refresh metadata from v1.10.0 on

Fixed documentation links

09 May 08:23
82d9a40
Compare
Choose a tag to compare

Summary

This is a bug-fix release that fixes stale links in the Virtual Schema documentation.

Changes

#177: Fixed broken documentation links

Join pushdown for Hive dialect

08 May 10:57
Compare
Choose a tag to compare

Summary

The JDBC Adapter can now handle join pushdowns for the Hive 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

#152 Enable Join pushdown for Hive