Skip to main content

Teiid 9.2.1 Released

Teiid 9.2.1 is now available.  This fix release covers 18 issues:
  • [TEIID-4765] - The notion of resolving order may need to be extended beyond a schema
  • [TEIID-4788] - DDL vdb is expensive to process
  • [TEIID-4809] - lob performance issues
  • [TEIID-4770] - The convert script generates empty GRANT statements for roles that don't have permission to access a certain schema.
  • [TEIID-4771] - The convert script generates GRANT TEMPORARY_TABLE ON DATABASE statements but these fail.
  • [TEIID-4774] - Convert VDB utility does not work when translator overrides are present
  • [TEIID-4776] - Issues with array type metadata
  • [TEIID-4783] - missing message keys for functions
  • [TEIID-4785] - Add options through alter table in DDL does not work.
  • [TEIID-4791] - Bypass lookup function's keycolumn reserved word
  • [TEIID-4797] - Oracle: empty catalog messed up VDB schemas name
  • [TEIID-4807] - DDL format of a vdb lacks import information
  • [TEIID-4652] - SybaseIQ translator: DAYOFYEAR function not pushed correctly
  • [TEIID-4653] - SybaseIQ translator: Input parameter not set in prepared statement in source command
  • [TEIID-4775] - External materialization, after transaction timeout, LoadState continues to be LOADING
  • [TEIID-4778] - External Materialization, When TTL is less than loading time, the scheduling is off
  • [TEIID-4780] - Clone TEIID-4734 (Backwards compatible solution)
  • [TEIID-4782] - Change framework to catch RutineException from translator/connector
Note that several of these are related to the new DDL vdb feature - thanks Bram Gadeyne for the initial feedback.  This feature will continue to evolve even in 9.2.x to maintain forward compatibility with 9.3.x.

Looking forward, Teiid 9.2.2 should be available in 3-4 weeks.

Thanks,
Steve


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