Skip to main content

Teiid 9.0 Beta1 Released

We are ready to move into the Beta phase of 9.0 with the release of Beta1.  Any of the remaining larger features will likely be pushed to Teiid 9.1.  The main feature in Beta1 since Alpha2:
  • TEIID-4084 Allowing for with clause inlining to improve performance.

This should put us on track for a 9.0 release by the end of May.  Also a 8.13.4 release will probably be available by end of month depending upon what issues are found.

A reminder - the new GitBook documentation home for 9.0 and later is at: https://teiid.gitbooks.io/documents/content/

Steve

Comments

  1. title typo? it's beta 1, not beta 2 right?

    ReplyDelete
  2. Yes, it's now corrected to Beta1. There was initially a hiccup with the Beta1 would due to https://issues.jboss.org/browse/TEIID-4094 that I was initially going to move the build name for, but then went back and re-built Beta1. Sorry for the confusion.

    ReplyDelete
  3. When will Teiid move to Wildfly 10? I am interested in moving to CXF 3.1 (from 3.0).

    ReplyDelete
  4. That will be Teiid 9.1 at the earliest. A good guess would be we'll have something for 10 (or 11 if it's early) in about 6 months.

    ReplyDelete

Post a Comment

Popular posts from this blog

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 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

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