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 http://jboss.org/vote.  

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

Comments

Popular posts from this blog

Teiid 8.11 Beta1 and 8.10.1 Released

Teiid 8.11 Beta1 is now available from the  downloads  and maven.  Feature highlights since Alpha2 include: TEIID-3434 More caching control over ttls in the result set cache down to the schema/table level. TEIID-3412 MS Access support via the UCanAccess driver. The UCanAccess support is necessary for those running on Java 1.8 as the JDBC ODBC bridge has been removed from the JRE. The waiting continues on EAP 6.4 Alpha1 - it still should be available shortly and should be the platform target for Teiid 8.11 Beta2. Of course, let us know if you find any issues with these early releases.  There's still plenty of time to get fixes into the final release. Teiid 8.10.1 is also available.  It addresses 5 important issues discovered since 8.10 was released: [ TEIID-3409 ] - PostgreSQLExecutionFactory TranslatorProperty annotation in wrong place [ TEIID-3437 ] - Inconsistencies with row count handling [ TEIID-3438 ] - Null value returned from BlobImpl

Tech Tip: Teiid SQL Language MAKEDEP Hint Explained

In this article I will explain what a MAKEDEP hint is, how and when, why it should be used in Teiid. What: MAKEDEP is query hint.  When a query hint is defined in the SQL query it influences the Teiid query planner to optimize the query in a way that is driven by the user. MAKEDEP means "make this as a dependent join". What is a Dependent Join? For example if we have query like: SELECT * FROM X INNER JOIN Y ON X.PK = Y.FK Where the data for X, and Y are coming from two different sources like Oracle and WebService in Teiid, so in relational algebra you can represent above query as Here the result tuples from node X and node Y are being simultaneously fetched by Teiid query engine, then it joins the both the results inside Teiid engine based on the specified X.PK = Y.PK condition and returns the filtered resulted to the user. simple.. Now, what if, if X table has 5 rows and Y table has 100K rows? In order to do the JOIN naively Teiid need sto read all the 5

Teiid Spring Boot 1.7.0 Released

Teiid Spring Boot version 1.7.0 to support Teiid 16.0 has been released. This release is mainly to support the Teiid's latest version.  In this release, the support for OpenAPI code generation based on VDB has been removed as there is no community interest and moreover it was at OpenAPI 2.0, and the industry has moved to 3.0 and beyond. There are no plans to further pursue this feature. VDB maven plugin was also removed, which was intended to be a replacement for the VDB importing feature was to be used when working on OpenShift, however, since it requires the Maven repository and does not completely represent the feature as defined on the WildFly based deployments this is also removed. You can still use the VDB import feature with Teiid Spring Boot, simply define the VDB with your "IMPORT DATABASE" statements and provide the additional files along with the main VDB file. During the start of the application, Teiid Spring Boot will load all the necessary DDL files for the