Skip to main content

Teiid 9.0 Alpha2 Released

We are making progress with 9.0 with the release of Alpha2.  The main features in Alpha2 since Alpha1:
  • TEIID-2476 Data role metadata filtering to omit non-accessible objects from system tables.
  • TEIID-4076 Improved autoCommitTxn detect to prevent unnecessary transactions.
The web console should be in better shape than with the Alpha1 release.  Once again there was also a substantial amount of fixes already picked up from 8.12.x and 8.13.x including a lot of refinements to the OData4 production logic.  So far 125 issues have been addressed - https://issues.jboss.org/projects/TEIID/versions/12315992


Expect 8.13.3 within the next week, which will pickup the web console changes and other fixes since 8.13.2.  Please let us know as soon as possible if you find any issues with 8.13 so that we get the fixes into 8.13.3.

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

Steve

Comments

Popular posts from this blog

Teiid Platform Sizing Guidelines and Limitations

Users/customers always ask us about the sizing of their Data Virtaulization infrastructure based on Teiid or the JDV product from Redhat. Typically this is very involved question and not a very easy one answer in plain terms. This is due to fact that it involves taking into consideration questions like:
What kind of sources that user is working with? Relational, file, CRM, NoSQL etc.How many sources they are trying to integrate? 10, 20, 100?What are the volumes of data they are working with? 10K, 100K, 1M+?What are the query latency times from the sources? How you are using Teiid to implement the data integration/virtualization solution. What kind of queries that user is executing? Even small federated results may take a lot of server side processing - especially if the plan needs tweaking.Is materializing being used?Is query written in optimal way?and so on..Each and every one of the question affects the performance profoundly, and if you got mixture of those then it become that much…

Teiid Runtimes Explained

If you have been following Teiid lately we have been going through a whole lot of renovations. Yes, renovations or reorganization or refactoring or whatever you want to call it. Basically, we are making Teiid more modular with fewer dependencies that can be used by however your use case dictates rather than use it as one monolith application deployed into WildFly JEE Application Server. There is nothing wrong in using Teiid as server model, but with the proliferation of container-based workloads and cloud-based architectures, the previous server-based model does not work or simply won't scale. So, we needed to think of alternatives, thus Teiid team introduced a couple different versions modular Teiid what we are calling as "Teiid Runtimes".

Note that in these modular Teiid runtimes, not all the features you were used to using in Teiid Server model may not be there but you will have extensions to add in those that are most appropriate for your domain. If you are looking …