Skip to main content

Teiid 9.0 CR1 Released

Teiid 9.0 CR1 is now available.  This is a very large release compared to most with 238 issues addressed so far.  A recap of the major features:
  • TEIID-3601 Large row counts internal tables and source queries are no longer limited to max integer rows. However update counts, count aggregate values, user result sets, etc. are still limited to max integer.
  • TEIID-3792 Array Quantified Comparisons can be used to search array values - for example expression = SOME (array_expression)
  • TEIID-3462 Semantic VDB Versioning can be used in the VDB name and connection string, rather than the simple integer version. See the Reference for more.
  • TEIID-3849 Cassandra Update Improvements for bulk/batch updates and asynch processing.
  • TEIID-3869 Additional geospatial support for Geoserver integration with Teiid.
  • TEIID-2476 Data role metadata filtering to omit non-accessible objects from system tables.
  • TEIID-4076 Improved autoCommitTxn detect to prevent unnecessary transactions.
  • TEIID-4084 Allowing for with clause inlining to improve performance.
  • TEIID-3725 JDG Cache/DSL Translator added cache swapping feature to support external materialization.
  • TEIID-3810 JDG Cache/DSL Translator upgraded support for JDG 6.6
  • TEIID-3520 Swagger Translator for calling REST services defined by Swagger.
  • TEIID-4202 Lateral join and procedure pushdown support for targeted sources.
This puts us on pace for a release in the next 2-3 weeks.

Even if you are already on 8.13.x, which uses the same Wildfly platform, you should checkout the migration guide.  The quickstarts have been updated - including several new scenarios.  There is still a lot more places that we want to correct/update that reference things like JBoss AS rather than Wildfly - so let us know if anything seems amiss.

Thanks,
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 …