Skip to main content

Teiid 9.1.2 Released

Happy New Years to everyone. The next fix release on the 9.1.x line is now available. It addresses 21 issues:
  • [TEIID-4551] - Improve exception handling in Admin methods
  • [TEIID-4663] - Support a more secure block mode for client/server encryption
  • [TEIID-4553] - COUNT returns inconsistent results when column statistics are not gathered
  • [TEIID-4566] - Ordered limit against preserved view fails
  • [TEIID-4573] - Modeshape query
  • [TEIID-4580] - ST_PointOnSurface returns point on the boundary of the polygon
  • [TEIID-4584] - SimpleDB doesn' work
  • [TEIID-4589] - Teiid throws NPE if multi-value insert is issued on global temporary table
  • [TEIID-4595] - Wrong pushdown of several spatial functions to Oracle
  • [TEIID-4598] - NPE when analytic Source function for Greenplum doesn't get pushdown
  • [TEIID-4605] - SqlServer translator - insert/update statements - timestamp is cast to datetime
  • [TEIID-4608] - Insert statement - multi-value insert into view - incorrect type resolution if first tuple contains NULL
  • [TEIID-4631] - IN clause causes an error when used within a function in SELECT clause
  • [TEIID-4637] - join of aliased views with partitioned unions not handled correctly.
  • [TEIID-4648] - MySQL unsigned type detection is incorrect
  • [TEIID-4649] - SybaseIQ translator: different order of arguments in CONVERT function
  • [TEIID-4650] - SybaseIQ translator: week function can't be pushed directly
  • [TEIID-4651] - SybaseIQ translator: different order of arguments in LOCATE function
  • [TEIID-4661] - Subsequent queries hang after materialized view TTL expires.
  • [TEIID-4668] - Google translator skips NULL value in INSERT
  • [TEIID-4673] - Translator import of google spreadsheet not updatable

If needed a 9.0.6 will be made available prior to the release of 9.2 Final.  9.2 Beta1 will be available tomorrow.



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…