Skip to main content

Teiid 9.3 CR1

Teiid 9.3 CR1 has been released.  A recap of all feature highlights:
  • TEIID-3624 CREATE DOMAIN support for user defined simple types.
  • TEIID-4724 DDL .vdb deployment.
  • TEIID-4557 TEIID-2465 Memory restrictions at the operation and session level.
  • TEIID-4578 SQLAlchemy and Superset support through our pg/odbc access.
  • TEIID-4646 LEAD/LAG/FIRST_VALUE/LAST_VALUE analytic/value function support.
  • TEIID-2820 Couchbase support via a new translator and resource adapter.
  • TEIID-4733 Infinispan Support via a new translator and resource adapter.
There have been 136 issues addressed so far - https://issues.jboss.org/projects/TEIID/versions/12332954 - please test your issues if possible before the final release in early June.

Other news:
  • A Teiid 9.1.5 will be released shortly after 9.3 Final.
  • Teiid 10.0 work has begun.
    • Please comment on TEIID-4895 with regards to WildFly utilization.  Comments on JRE support are welcome as well - can you describe what circumstances may be holding you to 1.6 or 1.7?
    • We will likely start including the Data Services Builder in the all-in-one download.  Data Services Builder and other efforts will be at the forefront of offering data virtualization on OpenShift.
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