Skip to main content

Teiid 9.1 Alpha1 Released

Teiid 9.1 Alpha1 has been posted.  This is expected to be a typical 3 month feature release cycle with pre-releases about every two weeks.  So far in Alpha1 you'll find:
  • TEIID-4243 BatchUpdateException support in JDBC to indicate what part of batch succeeds when a failure occurs.
  • TEIID-4191 NO QUOTE option for TEXTAGG.
  • TEIID-4200 Moved to WildFly 10 as host environment
WildFly Upgrade

We chose to stick with the Teiid 9.x release series even with the platform update since we not introducing Teiid centric feature changes and this by itself will not be a breaking change for most.  However the WildFly 10 upgrade does mean that JRE 1.8+ is required for both the server and embedded.  Teiid 9.0 will be supported for an extended period to provide a JRE 1.7 compatible platform.  Other know issues:

TEIID-4306: xa datasource create cli not work
TEIID-3834: start/stop of a data source or resource adapter requires a restart (somewhat worse behavior than WildFly 9 from our perspective)

Teiid Designer

A Teiid Designer release should be available shortly that is compatible with WildFly 9 and Teiid 8.13.x with partial support for Teiid 9.0.x.  A Teiid Designer release compatible with WildFly 10 is TDB.  The tooling team has several irons including refinements to the OpenShift web UI and the Komodo project - so anyone with an interest in tooling work should contact their community.

Coming Soon to 9.1

TEIID-3617: Provide an option to Limit per user based connections
TEIID-3754: OData V2 service removal
TEIID-4000: Data Expand support
And much more...


9.0.1 is due out later this week, and as mentioned above we'll keep supporting 9.0.x for an extended period.


8.13.6 is due out next week.  At this point only critical/blocker fixes will make it into 8.13.x.

As always thanks for all the community support,


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 …