Skip to main content

Teiid 9.3.3 Released

Teiid 9.3.3 has been released.  It resolves 22 issues:
  • [TEIID-5021] - Latest openjdk does not include anon cipher suites
  • [TEIID-5028] - SystemFunctions should be loaded once
  • [TEIID-5017] - More aggressively use enhanced join sorted index to prevent buffering
  • [TEIID-5013] - Google Spreadsheet Data Sources with custom client_id and client_secret
  • [TEIID-4974] - Couchbase - TRANSLATE function is transalted as REPLACE
  • [TEIID-4983] - Couchbase tests rely on unpredictable order
  • [TEIID-5014] - Unable to use parameterized query with node pg module and Teiid/JBoss VDB
  • [TEIID-5019] - Makedep hint using @ syntax sometimes ignored
  • [TEIID-5020] - Join query results in NullPointerException
  • [TEIID-5029] - Regression with outer join optimization
  • [TEIID-5030] - Couchbase error in date/timestamp/time datatype pushdown
  • [TEIID-5031] - Couchbase issues in functions where result is different datatype than the argument
  • [TEIID-5033] - Couchbase substring function is 0-based
  • [TEIID-5035] - Couchbase INTERSECT doesn't return any values
  • [TEIID-5036] - Couchbase EXCEPT returns more values than expected
  • [TEIID-5037] - Couchbase UNION doesn't work correctly
  • [TEIID-5039] - Couchbase document type definition for a table
  • [TEIID-5042] - Couchbase supported data types restriction issues
  • [TEIID-5044] - Using "SHOW PLAN" statement only shows initial plan
  • [TEIID-5045] - Rewriter allows "true" criteria to be modified
  • [TEIID-5054] - autoFailover with a multi-batch result timing issue
  • [TEIID-5059] - CacheEntry memory leak due to issues with touch method
Note that TEIID-5059 is a particularly important issue as it leads to a memory leak of heap cache entries in certain situations.

Expect a 9.2.6 in the next day or two.



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 …