Skip to main content

Teiid 10.2.0 Released

We are pleased to announce the release of Teiid 10.2.0.  This was the new normal of an 8 week cycle. See all 54 issues addressed.  The feature highlight are:
  • TEIID-5236 Updated support for GeoServer and 9.4+ PostgreSQL JDBC drivers.
  • TEIID-5246 Simplified configuration when using an external load balancer.
  • TEIID-5248 v4 Api Support for Google Spreadsheets.
  • TEIID-5220 Additional Npgsql support via limited information_schema support.
Other Important Stuff:
  • Several important OData translator issues were addressed - if you use the OData translator, you should upgrade or use next fix release 10.0.5/10.1.3
  • Teiid 10.1.3 and 10.0.5 will be available in about 3 weeks.
Special thanks to the many community members who contributed to this release - in particular dalex dalex, Bram Gadeyne, Divyesh Vallabh, and Yuming Zhu.

Thank you,
The Teiid Team


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 …