Skip to main content

Teiid 8.9 Final Released

The Teiid community is excited to announce yet another (nearly) time boxed release of its Data Virtualization software - version 8.9. This release took an extra 4 weeks on top of regular 12 weeks to accommodate a NEW version of the host environment - JBoss EAP 6.3.0 Alpha.

You can find the Teiid downloads at

A little over 100 issues were resolved and this is looking to be solid release. The major features include:
  • TEIID-3009 WITH project minimization - common table expressions will have their project columns minimized.
  • TEIID-3038 geoSpatial support for MongoDB translator
  • TEIID-3050 Increased Insert Performance with sources that support batching or insert with iterator.
  • TEIID-3044 Function Metadata is available through system tables and DatabaseMetaData.
  • TEIID-1910 TeiidPlatform for EclipseLink integration is now provided via the teiid-eclipselink-platform jar in maven.
  • TEIID-3119 Performance improvements in grouping and duplicate removal as well as general improvements to memory management.
  • TEIID-3156 Collation aware prevention of order by pushdown via the collationLocale translator property and the org.teiid.requireTeiidCollation system property.
  • TEIID-3042 Usage Information on views and procedures in the system table SYSADMIN.Usage.
  • OData4 Support - There is partial support for OData4 using the Apache Olingo project. The OData2 is still intact. We consider this still as experimental feature.
Thank you for continued support in the community, especially to the individuals who found issues, entered JIRAs, and provided other valuable contributions. Huge thanks to Alex K.,  Bram GadeyneCristiano NicolaiDevesh MishraGary GregoryHaifen BiHarrison GentryIvan ChanJoao ViragineJoseph CHIDIACMark AckertMark AddlemanMichael FarwellPranav KSalvatore RSanjeev GourSunil VarmaTom Arnold for all your contributions.

The development of Teiid 8.10 is already well underway, but there is plenty of time to add more features. The target release date will be February 15th, 2015. If you have been thinking about a feature for Teiid, this is a great time to engage the leads and submit your request/proposal. We really need experts out there to help with our big data story.  If you have experience with NoSQL stores, please write a translator in Teiid or improve what we already have in the build.  Check out the Open To Community issue bucket to see some existing issues that could be good to start with.  We are also looking for web smiths, as we really want update the main Teiid website - any volunteers are welcome.

If you are thinking about production support, look into Redhat Data Virtualization.  You can also download a free developer version of upcoming DV 6.1.0 version there.

Thank you. 

Steve and Ramesh.


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 …