Skip to main content

Teiid 10.3.1 Released

We are pleased to announce the release of Teiid 10.3.1 (A regression with TEIID-5314 caused an immediate patch release).  See all 48 issues addressed.  The feature highlight are:
  • TEIID-5293 Added implicit partition wise joining in non-multisource scenarios as well.
  • TEIID-5308 Added ENV_VAR and SYS_PROP functions and clarified the usage of the ENV function.
  • TEIID-4745 Added a polling query to trigger the reload of materialized views.
  • TEIID-5317 Added ODBC 3.0 functions current_time, current_date, current_timestamp.
  • TEIID-5314 Environment variables can now be used instead of or to override system properties.
  • TEIID-5307 Added more information_schema tables for pg compatibility.
  • TEIID-4864 Added update support to the Excel translator.
Special thanks to the many community members who contributed to this release - in particular Andreas Krück, Divyesh Vallabh, Mathieu Rampant, Mike Higgins, Pedro Inácio, Yuming Zhu, Michael Echevarria, and Bram Gadeyne.

We should also extend a warm welcome to Rafal Korytkowski to the Teiid Team. Rafal has begun by finishing off the work on the Exosal translator and will help with efforts related to cloud and OpenShift support.

Other Important Stuff:
  • The new website is (mostly) live! See teiid.io. There are no under construction animated GIFs, but you can expect a few issues as we get the new Hugo/Netlify/Travis build worked out. Notice that we're effectively combining tooling and backend under a single site.  The content is being updated to be more relevant for cloud and OpenShift deployments. A lot of work is happening in creating a self-service data virtualization OpenShift based solution. If you have any interest in becoming involved, or would like to see more around the image build/configuration please let us know.
  • Teiid 10.2.2 and 10.1.4 will be available in the next couple of days. That will effectively end support for the 10.1.x release stream.
Thank you,
The Teiid Team


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…