Skip to main content

Teiid 8.12.1 Released

Teiid 8.12.1 is now available.  It contains all of the 8.11.5 fixes plus a number of odata and hbase fixes.  All fixes since 8.12 include:
  • [TEIID-3757] - OData V2: $top doesn't work with virtual procedures
  • [TEIID-3760] - endswith defined with wrong return type
  • [TEIID-3761] - OData V2: The property based response and Function based responses are incorrect per specification
  • [TEIID-3762] - OData V2: $value on property is not supported
  • [TEIID-3764] - HBase - Phoenix driver does not support UNION
  • [TEIID-3765] - HBase - Phoenix does not support scalar subquery
  • [TEIID-3767] - HBase - Phoenix does not support LIKE ESCAPE
  • [TEIID-3770] - HBase - table's alias (... AS ...) is not "visible" in SELECT caluse in IN predicate
  • [TEIID-3771] - Teiid throws an NPE while executing query with nested subquery IN predicate
  • [TEIID-3776] - Teiid throws NPE if query contains AVG function on varchar type
  • [TEIID-3777] - ORDER BY DESC is ignored in STRING_AGG function when DISTINCT is also specified
  • [TEIID-3783] - Error when limit/sort is pushed above a window function
  • [TEIID-3785] - PostgreSQL - Large Objects may not be used in auto-commit mode.
  • [TEIID-3759] - Missing Apache Olingo dependency in Teiid 8.12.0.Final
  • [TEIID-3780] - Hive: Convert "UseDatabaseMetaData: to be an translator import property
  • [TEIID-3781] - Queries are not killed even if the client sends a cancel request
Additionally we are working targeted enhancements in 8.12.x.  For 8.12.1 this includes:
  • [TEIID-3039] - OData V2: Add support for odata expand
  • [TEIID-3361] - Initial addition of source query details to the command log
  • [TEIID-3436] - OData V2: Add array type support to the odata translator
  • [TEIID-3778] - Mark hbase/phoenix as supporting limit
  • [TEIID-3791] - Upgrade groovy-all to be version 2.4.
We'll look to put out an 8.12.2 in a couple of weeks as more issues are worked/found.

Work has started on the Wildfly 9 support in Teiid 8.13.  If all goes well, then an 8.13 Alpha1 will be available in the next two weeks.

The Teiid Team


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 …