Skip to main content

Teiid 8.7 Final Released

Teiid 8.7 has been released and is now available for download and from the Maven repository.  This was both a rich feature and a fix release with over 100 issues addressed.

Main features in this release include:
  • TEIID-1070 Amazon SimpleDB support has been contributed by Radim Hopp. See the Admin and Reference Guides for more. See example here
  • TEIID-2761 Security Enhancements added support for a grant-all attribute on a role. Also added the ability to specify the security domain for a VDB. See the reference guide for more.
  • TEIID-2780 Apache Solr Translator has been added. See the Admin and Reference Guides for more. See example here
  • TEIID-2809 Pattern based system property substitution has been added to VDB.XML files. Only supported if the DVB is being deployed JBoss EAP.
  • TEIID-2844 Remove unauthorized columns from SELECT * can be enabled via the session property ignore_unauthorized_asterisk. See the Reference for more.
  • TEIID-2863/TEIID-2761 More robust GSS-API support. This issue also implements a feature where a user can now define a "security-domain" per VDB. User no longer has to depend upon the transport level authentication.
  • TEIID-2826 Revamped build structure for translators and connectors so that it is easier to package them and deploy them to a Teiid server.
  • TEIID-2859 TEXTTABLE FOR ORDINALITY a FOR ORDINALITY column can now be used with TEXTTABLE. See the Reference for more.
  • TEIID-965 Apache POI based Excel connectivity has been added. See the reference for more. See example here
  • TEIID-2888 Designer VDB support in Embedded is now available. With a few caveats, Designer .INDEX based vdbs can now be used with Teiid Embedded. See the Embedded Guide for more.
  • TEIID-2904 Translator Properties Translator import, override and extension-metadata properties are can retrieved through Admin API
  • TEIID-2627 Accumulo Translator has been added. See Admin and Reference guides for more information. See example here
We sincerely thank everyone who participated in the community.  All bugs/posts are helpful in refining Teiid.  We are looking forward to your input on 8.8.

If 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.

Steve and Ramesh


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…