Skip to main content

Teiid 8.2 Final Released

Continuing our time boxed release schedule Teiid team is excited to announce availability of Teiid 8.2.Final.

In total there were 120 issues resolved - including 15 new features and over 50 bug fixes. See all the issues on Teiid's JIRA.

This release coincides with the first release of the Teiid Console for Teiid 8.x.  The Teiid Console is a web based administrative tool for configuration and monitoring and is also available from the downloads area. A big thanks to Heiko Braun for his support in developing this.

The Teiid Designer team is making great progress towards the Teiid Designer 8.0 which works with Teiid 8.2.Final. For early releases please see the Designer Downloads.

Teiid 8.2 is still based on JBoss AS 7.1.1  The JBoss AS 7.2 release is still TDB sometime after the rename process. You can help by voting for new name  

Here are the feature highlights:
  • TEIID-1923 Teiid Console - A web based administrative console for Teiid.
  • TEIID-2150 Positional procedure defaults - a procedure now may be called positionally with just the leading input parameters as long as all trailing parameters are out or defaultable.
  • TEIID-2148 Streaming Improvements - the ws translator invoke/invokeHttp procedures now accept a "stream"" parameter to indicate that the result should be streamed directly without an intermediate copy being created. Also intermediate document/blob copies are made concurrently with reading to reduce latency.
  • TEIID-2158 Rest Services - when required extension metadata defined on the virtual procedure, a REST based service on that procedure is automatically generated and deployed upon VDB deployment.
  • TEIID-2163 Binary XMLSERIALIZE - XMLSERIALIZE now supports blob/varbinary and the encoding/version and XMLDECLARATION options.
  • TEIID-2141 OBJECTTABLE - was added to extract values from objects using arbitrary scripts. See the Reference for usage.
  • TEIID-2111 Vararg Procedures - variable argument procedures and functions can be created through DDL using the VARIADIC parameter type. See the Reference for usage.
  • TEIID-2195 Function Based Indexes - DDL can be used to specify function based indexes. When used on an internal mat view it will create the corresponding function based index automatically. In any other circumstance, the metadata is not currently used.
  • TEIID-2181 System query performance - system queries are now indexed on case-insensitive schema/table name columns.
  • TEIID-2086 Transactional results caching - the result set cache is now transactional by default.
  • TEIID-2210 Object Translator - the translator-object can support Infinispan Cache and other Map type caches. See OBJECTTABLE for executing queries against this translator.
  • TEIID-1386 Procedure exception handling - the Teiid procedure language now supports exception handling and emitting SQLWarnings. See the Reference for syntax and usage.
  • TEIID-2176,TEIID-2177 Native Query Support - JDBC, LDAP, SalesForce, JPA, OLAP translators now support execution of native queries directly against the source either through "native-query" extension metadata property or native procedure defined by their translator.
  • TEIID-2227 Procedure RETURN statement - the Teiid procedure language now supports a RETURN statement. See the Reference for syntax and usage.
  • TEIID-2269 Vault Support - The transport's keystore and truststore passwords are now supported through vault based passwords.
  • TEIID-1064 Google Spreadsheet Support - there is now support for querying Google Spreadsheets via Teiid. See the Reference and Admin Guides for more.
  • TEIID-2274, TEIID-2275, TEIID-2288, TEIID-2299 Converting examples to Quick Starts - The examples in the Teiid JBoss dist zip have been converted to Quick Starts and will now be found in the Quick Start kit.
This work was due in large part to the great participation from Teiid community users, a BIG thanks to all who participated especially Mark Addleman, Jack Ma, I Leitch, Vineela Gumpa, Samier Nadji, Graeme Gillies, Ivan Chan, David Eichmann, Hisanobu Okuda, Jaspal Singh, Mónica L.A., Rajasekhar Kota, Filip Nguyen in providing valuable input through their JIRAs and community suggestions.

How To Get Involved:

If you have useful features in mind for Teiid, please open a forum discussion and lets get them captured in JIRA for inclusion in the Teiid roadmap.  8.3 is just starting and can still be influenced based upon community need. 

If you are a developer, did you know Teiid source is now hosted on GitHub? Your contribution is just a fork away! 

If you are using Teiid, please blog about it and tell us how it is helping you solve your Data Virtulization needs. If you have/can create tutorials or videos about Teiid, please share with the community.

Thank you.

Ramesh & Steve


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…