Skip to main content

Teiid 8.12.1 Released

Teiid 8.12.1 is now available.  It contains all of the 8.11.5 fixes plus a number of odata and hbase fixes.  All fixes since 8.12 include:
  • [TEIID-3757] - OData V2: $top doesn't work with virtual procedures
  • [TEIID-3760] - endswith defined with wrong return type
  • [TEIID-3761] - OData V2: The property based response and Function based responses are incorrect per specification
  • [TEIID-3762] - OData V2: $value on property is not supported
  • [TEIID-3764] - HBase - Phoenix driver does not support UNION
  • [TEIID-3765] - HBase - Phoenix does not support scalar subquery
  • [TEIID-3767] - HBase - Phoenix does not support LIKE ESCAPE
  • [TEIID-3770] - HBase - table's alias (... AS ...) is not "visible" in SELECT caluse in IN predicate
  • [TEIID-3771] - Teiid throws an NPE while executing query with nested subquery IN predicate
  • [TEIID-3776] - Teiid throws NPE if query contains AVG function on varchar type
  • [TEIID-3777] - ORDER BY DESC is ignored in STRING_AGG function when DISTINCT is also specified
  • [TEIID-3783] - Error when limit/sort is pushed above a window function
  • [TEIID-3785] - PostgreSQL - Large Objects may not be used in auto-commit mode.
  • [TEIID-3759] - Missing Apache Olingo dependency in Teiid 8.12.0.Final
  • [TEIID-3780] - Hive: Convert "UseDatabaseMetaData: to be an translator import property
  • [TEIID-3781] - Queries are not killed even if the client sends a cancel request
Additionally we are working targeted enhancements in 8.12.x.  For 8.12.1 this includes:
  • [TEIID-3039] - OData V2: Add support for odata expand
  • [TEIID-3361] - Initial addition of source query details to the command log
  • [TEIID-3436] - OData V2: Add array type support to the odata translator
  • [TEIID-3778] - Mark hbase/phoenix as supporting limit
  • [TEIID-3791] - Upgrade groovy-all to be version 2.4.
We'll look to put out an 8.12.2 in a couple of weeks as more issues are worked/found.

Work has started on the Wildfly 9 support in Teiid 8.13.  If all goes well, then an 8.13 Alpha1 will be available in the next two weeks.

Thanks,
The Teiid Team


Comments

Popular posts from this blog

Teiid 8.11 Beta1 and 8.10.1 Released

Teiid 8.11 Beta1 is now available from the  downloads  and maven.  Feature highlights since Alpha2 include: TEIID-3434 More caching control over ttls in the result set cache down to the schema/table level. TEIID-3412 MS Access support via the UCanAccess driver. The UCanAccess support is necessary for those running on Java 1.8 as the JDBC ODBC bridge has been removed from the JRE. The waiting continues on EAP 6.4 Alpha1 - it still should be available shortly and should be the platform target for Teiid 8.11 Beta2. Of course, let us know if you find any issues with these early releases.  There's still plenty of time to get fixes into the final release. Teiid 8.10.1 is also available.  It addresses 5 important issues discovered since 8.10 was released: [ TEIID-3409 ] - PostgreSQLExecutionFactory TranslatorProperty annotation in wrong place [ TEIID-3437 ] - Inconsistencies with row count handling [ TEIID-3438 ] - Null value returned from BlobImpl

Tech Tip: Teiid SQL Language MAKEDEP Hint Explained

In this article I will explain what a MAKEDEP hint is, how and when, why it should be used in Teiid. What: MAKEDEP is query hint.  When a query hint is defined in the SQL query it influences the Teiid query planner to optimize the query in a way that is driven by the user. MAKEDEP means "make this as a dependent join". What is a Dependent Join? For example if we have query like: SELECT * FROM X INNER JOIN Y ON X.PK = Y.FK Where the data for X, and Y are coming from two different sources like Oracle and WebService in Teiid, so in relational algebra you can represent above query as Here the result tuples from node X and node Y are being simultaneously fetched by Teiid query engine, then it joins the both the results inside Teiid engine based on the specified X.PK = Y.PK condition and returns the filtered resulted to the user. simple.. Now, what if, if X table has 5 rows and Y table has 100K rows? In order to do the JOIN naively Teiid need sto read all the 5

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