Skip to main content

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 getBytes
  • [TEIID-3450] - bulk values are set directly from client
  • [TEIID-3400] - Oracle connection not consistently usable after cancel 
Thanks again for all the community support.

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 …