Skip to main content

Teiid 9.3 Final Released

With about 3 1/2 months of work, 138 issues later, 9.3 Final release is ready.  Feature highlights include:
  • TEIID-3624 CREATE DOMAIN support for user-defined simple types.
  • TEIID-4724 DDL .vdb deployment.
  • TEIID-4557 TEIID-2465 Memory restrictions at the operation and session level.
  • TEIID-4578 SQLAlchemy and Superset support through our pg/odbc access.
  • TEIID-4646 LEAD/LAG/FIRST_VALUE/LAST_VALUE analytic/value function support.
  • TEIID-2820 Couchbase support via a new translator and resource adapter.
  • TEIID-4733 Infinispan Support via a new translator and resource adapter.
There were also several important planning issues that were resolved including: More join pruning and left outer join optimization.

DDL VDB support has been enhanced to be nearly equivalent to of its XML counterpart.  We will continue to improve the usability, feature set, and refine the syntax when necessary.


UI Work

If you haven't seen it, please also check out Data Service Builder - which is a streamlined web UI for JDV/Teiid. We will release a Designer version based on Teiid 9.3 in near future. However after that Designer will be mostly in maintenance mode.  We are going to focus more on Web-based UI for future.

10.x and Beyond

Although initially slated for 9.3 change data capture (CDC) event handling based on Debezium to keep the materialization tables in sync with source data sources like MySQL and PostgreSQL will be delayed until 10.0 or later.

With the emergence of Cloud-based processing and Microservices architectures, we have been taking a hard look at Teiid and how we could progress technology into future. We have laid out some initial plans about our thinking and some immediate actions. We are soliciting your input all these matters, so please get involved so that we can shape Teiid together.

Thanks again to everyone who contributed to this release.
Ramesh & Steve

Comments

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 …