Skip to main content

Teiid 9.1 Alpha2 Available

After a small delay Teiid 9.1 Alpha2 has been posted.  Notable features since Alpha1:
  • TEIID-4332 Improved NDV calculations for costing.
  • TEIID-2715 OData Metadata support for providing the metadata extension properties for OData.
Also the OData 2 service layer has been removed.  Please contact the community if you still need that functionality and want to maintain it as an independent project.

WildFly Upgrade

While most of the issues with the WildFly upgrade should be resolved.  It is unclear when progress will be made on TEIID-3834: start/stop of a data source or resource adapter requires a restart (somewhat worse behavior than WildFly 9 from our perspective)

Teiid Whipper

Whipper is a new project that will incorporate the changes made to our BQT testing framework by our Red Hat QE team and will aim to provide new features / ease of use for validation testing of all things Teiid.

Teiid Designer

Teiid Designer should have a release compatible with WildFly 9 / Teiid 8.13.x and Teiid 9.0.x in the next two weeks.  There is still no timeline yet for a Teiid Designer release compatible with WildFly 10.

The OpenShift web UI continues to progress, please contact their community is you have any interest in following or contributing to the work.

9.0.x

9.0.3 is due out in approximately 2-3 weeks.

8.13.x

If needed 8.13.7, the last fix release on 8.13, will be available by the general release of 9.1.

As always thanks 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 …