Skip to main content

Teiid 9.2 Final Released

It's been 4 months of hard work and we're ready to sign off on the 9.2 Final release.  Feature highlights include:

  • TEIID-4284 Salesforce Bulk API for SELECT queries.
  • TEIID-4556 TEIID-4545 TEIID-4515 Phoenix/Hbase Translator now supports joins, more system functions/pushdown functions, and offset
  • TEIID-4532 Hashing Functions were added for md5, sha1, sha2-256, and sha2-512.
  • TEIID-4627 Source Triggers to handle source change events.
  • TEIID-4643 Encrypt/decrypt functions were added for 128bit AES.
  • TEIID-4622 Data Quality Functions contributed by OSDQ.
  • TEIID-4441 FTP/SFTP Connectivity via a new ftp resource adapter.
  • TEIID-4629 DDL Replacement for vdb.xml to eliminate the need to mix XML and DDL.
  • TEIID-4398 VDB Migration tool - Migration tool to convert .vdb & -vdb.xml files into DDL based VDB
In addition to reading up on the individual JIRA issues, here's a summary of where several important efforts stand.

DDL Support

The DDL option (TEIID-4629/TEIID-4398) for defining VDBs is an exciting feature set. You will no longer need to mix XML and DDL to define a VDB, it can all be done in DDL. These features are evolving though, so please bear with us if you discover issues such as syntax that needs tweaked or inconsistencies with XML metadata. Just log an issue and we'll get things addressed - a special thanks to Bram Gadeyne who has already helping catch issues.

Data Quality

Vivek Singh contributed more OSDQ Data Quality Functions. Please see the OSDQ tooling for data quality / preparation functionality that is now compatible with Teiid. Some hashing and encryption functions (TEIID-4532/TEIID-4643) were also added as regular Teiid system functions. Expect more functions to become available in subsequent releases. We'll continue to work across both communities on data quality and related efforts.

UI Work

If you haven't seen it, please also check out Data Service Builder - which is a streamlined web GUI for JDV/Teiid on OpenShift.

There will also be a Teiid Designer compatible with 9.2 out shortly - unless full UI support for some of the language features, such as source triggers, is initially targeted.


TEIID-4627 added DDL support for source table AFTER triggers - that is just part of a major thrust. Additional issues in 9.3 will allow Debezium integration to help keep materialized views synchronized with live data via change events.

We will also be adding domain support as a first step toward making the type system more flexible.

We expect that we'll hit the 3 month target for the release, so if there is anything that seems of high value to identify for the release please let us know early.

Thanks again to everyone who contributed in some way to this release,


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…