Skip to main content

Teiid 8.13.6 Released

The 8.13.6 fix release is now available.  This addresses 11 important issues:
  • [TEIID-3685] - org.teiid.padSpace does not affect to the "IN" operator
  • [TEIID-3815] - Oracle translator - OFFSET function does not work
  • [TEIID-4244] - Assertion failed error when joining duplicate rows to a table from other source
  • [TEIID-4248] - Build change for 8.13 caused the release notes to miss the version replacement
  • [TEIID-4260] - Accumulo: Resource adapter fails to load
  • [TEIID-4262] - Wrong result (empty or NULL) with an view and a single disjunction for join criteria
  • [TEIID-4280] - NPE in RuleMergeVirtual when running a query with nested CTEs
  • [TEIID-4287] - An exception is thrown by PostgreSQL when nested CTEs are pushed down
  • [TEIID-4290] - Rollback to savepoint should be a no op
  • [TEIID-4320] - Costing calculation issues
  • [TEIID-4324] - TEIID30019 Unexpected exception for request ... java.lang.AssertionError: Batch not found in storage
This is likely the second to last fix release for 8.13.  Expect an 8.13.7 in about a month and for fix releases to continue on 9.0.x after that.

Steve

Comments

Popular posts from this blog

Teiid Spring Boot 1.7.0 Released

Teiid Spring Boot version 1.7.0 to support Teiid 16.0 has been released. This release is mainly to support the Teiid's latest version.  In this release, the support for OpenAPI code generation based on VDB has been removed as there is no community interest and moreover it was at OpenAPI 2.0, and the industry has moved to 3.0 and beyond. There are no plans to further pursue this feature. VDB maven plugin was also removed, which was intended to be a replacement for the VDB importing feature was to be used when working on OpenShift, however, since it requires the Maven repository and does not completely represent the feature as defined on the WildFly based deployments this is also removed. You can still use the VDB import feature with Teiid Spring Boot, simply define the VDB with your "IMPORT DATABASE" statements and provide the additional files along with the main VDB file. During the start of the application, Teiid Spring Boot will load all the necessary DDL files for the

Teiid 8.13.3 Released

Teiid 8.13.3 is now  available .  In total 8.13.3 addresses 10 issues since 8.13.2: [ TEIID-4028 ] - adding salesforce-34 resource adapter does not work through the cli [ TEIID-4066 ] - Odata translator ClassNotFoundException: com.sun.ws.rs.ext.RuntimeDelegateImpl [ TEIID-4070 ] - Issues with resource adapters with api modules in wildfly [ TEIID-4089 ] - Teiid JDBC driver does not reset the update count when calling getMoreResults(int) [ TEIID-4093 ] - OData authentication fails with NPE when gss-pattern related properties are included in VDB [ TEIID-4096 ] - AssertionError with independent side of a dependent join that has an ordered limit [ TEIID-3050 ] - allow for more incremental insert with iterator [ TEIID-4075 ] - Netezza translator to support common table expressions [ TEIID-4098 ] - Always preserve columns order in google spreadsheets models [ TEIID-4046 ] - OData - $skip is beeing ignor

Expose Excel Data as OData feed using Teiid

For that matter you can expose any data source that is supported by Teiid through its translators as OData service. You can convert Relational databases XML, JSON, CSV files Web Services  Sales Force Excel documents sources, or write your on top of your specific source. Teiid added support for exposing its virtual database (VDB) as OData service without any additional work. Create a virtual database with your required sources and create any additional views and deploy in the the JBoss EAP 6.1 server, that has Teiid 8.3 or greater installed.  See https://docs.jboss.org/author/display/teiid84final/OData+Support  for more information. So, lets build a simple example of exposing the Excel Sheet. Teiid accesses Excel sheets via JDBC-ODBC bridge, and Windows OS provides a ODBC driver for Excel documents.  Edit the standalone-teiid.xml, and create Connection Factory jdbc:odbc:Driver={Microsoft Excel Driver (*.xls)};Dbq=c:\ODBC\ExcelData.xls odbc