Skip to main content

Teiid 10.0.5 Released

Teiid 10.0.5 has been released. It resolves 8 issues:
  • [TEIID-5293] - Add implicit partitioning of joins to non-multisource partitioning as well
  • [TEIID-5288] - OData4 skiptoken is not pulling from the cached results
  • [TEIID-5290] - NOW() function returns the same value for each call in BEGIN...END block
  • [TEIID-5294] - Bug with the name correction logic (TEIID30151 eror)
  • [TEIID-5296] - With MongoDB, timestamp operations throw exceptions when called on null or missing values
  • [TEIID-5297] - With MongoDB, null is returned from timestamp functions if the same function is part of WHERE clause
  • [TEIID-5300] - ClassCastException during query Optimization
  • [TEIID-5301] - With MongoDB, a query with subquery in HAVING clause doesn't return any results
This is the final community release on the 10.0.x line. Please upgrade to 10.1 or 10.2 when possible. 

Planning and work has begun on Teiid 11 and Teiid 10.3 respectively. Teiid 11 will align with WildFly 12, while Teiid 10.3 will likely be the last minor release on 10.x.



  1. Thanks Steven, which major changes are expected with Teiid 11?

  2. In addition to aligning to WildFly 12 and the corresponding Swarm release, we should make progress on Debezium and general OpenShift integration (some of which has gone into 10.x as well). We should be getting an Exasol translator in 10.3 or 11. I would expect 1 other new source to make it in by then.


Post a Comment

Popular posts from this blog

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 …

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…