Skip to main content

Teiid 8.12 Final Released, Swagger support added

Keeping up the tradition of time boxed releases, the Teiid team is proud to announce 8.12.0 Final. We have resolved 147 issues (features, enhancements, bugs) in this release. You can downloads at

JBoss EAP & Teiid:
8.12/8.11 are based on the JBoss EAP 6.4.Alpha platform. The downloads page contains a consolidated single download file that contains  EAP 6.4 Alpha + Teiid 8.12.0 + Teiid Web-Console.  You also have choice of using Docker image if you choose to at Docker Hub.

Please note this is the LAST VERSION of Teiid that will be based on JBoss EAP.  8.13 and 9.0, we will be moving to WildFly. Any micro releases on 8.12 line like 8.12.1, 8.12.2 etc still be using JBoss EAP.

Highlights of 8.12
  • TEIID-3411 LDAP modeling can now better account for associations defined by multivalued attributes.
  • TEIID-3323 Vertica translator added.
  • TEIID-3515 TEIID-3530 Dependent join enhancements in hints and pushdown planning.
  • TEIID-2883 Actian Vector in Hadoop Translator added
  • TEIID-3595 TEIID-3594 Logging Enhancements for command and audit logging
  • TEIID-3546 IS DISTINCT FROM syntax support added for use in procedures.
  • TEIID-3521 Swagger Support for auto-generated REST web services
  • TEIID-3652 Additional OUTER JOIN planning to allow more flexibility in join ordering
  • TEIID-3668/TEIID-3618 OAuth Support with JWT Bearer Access Token and Salesforce SSO using OAuth2 (RefreshToken, JWT)
  • TEIID-3712 Date/Time Keyword Literal support was added in the parser.
  • TEIID-3722 Option to not widen comparisons to string was added via the system property org.teiid.widenComparisonToString
  • TEIID-3327 OSIsoft PI translator added for use with the PI JDBC driver.
  • TEIID-3727 Salesforce Translator added a translator and resource-adapter based on Salesforce Partner API 34
  • TEIID-3370 OData4 Translator added new translator to read/write from any compliant OData V4 source
Community Folks:
Once again we had great interactions with community in developing this release. We sincerely extend our appreciation to Albert Wong, Avinash Misra, Bram Gadeyne, Burak Serdar, Dalex, Don Krapohl, Gary Gregory, Guru Prasad, Jorge Herrera, John Muller, Mark Addleman, Mark Tawk, Michael Davies, Michal Sanitrak, Mike Higgins, Pranav K, Prashanthi Kairuppala, Salvatore R, Sathish Kumaran Vairavelu, Scott Wallace, and Tom Arnold.

What's Coming Next:

Lot's of Stuff :)

We are working on 8.13 version that is just going to be similar to 8.12 version in terms of features, but we will replace JBoss EAP 6.4 Alpha with WildFly 9 or 10. If community feels WildFly 10 is better please speak up.  We'll probably move to WildFly 10 during the Teiid 9.0 development regardless.

Also expect an 8.11.5 shortly as the last of the 8.11.x series.

We are always looking for volunteers, so if you got idea or just want contribute to Teiid, please come talk to us in the forums.

Thank you for your continued support.

Ramesh & Steve.


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 …