Skip to main content

Teiid 8.8 Final Released

We are pleased to announce the timely release of Teiid 8.8.  It is now available for download and from the Maven repository.  While we didn't quite make it to 100 issues, this release still has a good set of features and quite a few fixes.  Main features include:
  • TEIID-2647 Translator for Cloudera's Impala data warehouse has been added. See the reference for more.
  • TEIID-2902 More incremental joins where the whole dataset does not need fully sorted or even read.
  • TEIID-2263 More control over MAKE (NOT) DEP hints via syntax that allows for traversing views. See the reference for more.
  • TEIID-2263 Common Table (WITH) planning improvements such that the usage of a WITH clause in a view or inline view no longer inhibits planning as part of the larger query.
  • TEIID-2980 XMLTable Array Support - XMLTABLE may now return arrays for sequence values.
  • TEIID-1675 Updatable LDAP multi-valued attributes - using an array type mapping, LDAP multi-valued attributes can be inserted/updated.
  • TEIID-3018 System tables for view/procedure definitions - the SYSADMIN Views and StoredProcedures tables can be used to access the definitions of the views/procedures.
Thanks to everyone who helped in this release from the community - all bugs/posts are helpful in refining Teiid.  There was a lot of important OData feedback from Luca Gioppo, John Muller, Greg MacKinnon, and others.  Hopefully 8.9 will be the start of the OData v4 work - which will require all sorts of new testing.  

And now for the obligatory product plug - if you have been using Teiid and would like fully supported version, Red Hat has released Data Virtualization V6 (DV6).  The DV platform has comprehensive support from Red Hat including services/training.

Thanks,
Steve and Ramesh

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 …