Skip to main content

Teiid 8.9 CR2

We are happy and trepidatious about the availability of 8.9 CR2 in the downloads and maven.  This moves us closer to the final, but introduces two important and late changes:

  • The target platform is now EAP 6.3 Alpha.  This platform change better aligns us with more recent product releases and removed the need for applying the RESTEasy patch. We also have a high degree of confidence in the changes as we have already been through this effort for productizing DV 6.1. You may however need to be signed into a jboss.org account for the EAP 6.3 Alpha download - we are working with the EAP team to get that restriction removed.   
  • The semantics of the pg transport security configuration have changed. By default the socket configuration has SSL disabled.  If login security is used, then clients will be required to use a secure login - which is currently only GSS.  If SSL is fully enabled, then clients will be required to use SSL. This more closely matches the behavior of the JDBC transport.  There is a backwards compatibility option if needed - see System Properties.
Given these changes we'll expect another CR release before the final.  We apologize for the delay as we typically do want to stick as close as possible to a quarterly release.  

Thanks again for all of the community effort in logging issues.  We are up to 110 addressed for this release, so we are expecting a high quality result.  Work will begin shortly on 8.10, which means that now is the time to vote for or log issues to be included in that release.

Steve

Comments

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…