Skip to main content

Teiid 9.3.1 Released

Teiid 9.3.1 has been released.  23 issues were addressed:
  • [TEIID-4636] - In the SWARM readme's, need to indicate the URL to connect
  • [TEIID-4793] - Change of class loading no longer requires module dependencies
  • [TEIID-4985] - Update Quickstart to use new columns in status table
  • [TEIID-4315] - HBase Quickstart issues
  • [TEIID-4896] - Two VDB's referencing same teiid_ispn:cache is not using the same cache
  • [TEIID-4942] - Statement batch does not enforce autoCommitTxn
  • [TEIID-4947] - Error with Salesforce translator if criteria on outer join on a custom table is from the right side table
  • [TEIID-4948] - java.lang.IllegalArgumentException: No marshaller registered for ispn.G1
  • [TEIID-4950] - PostgreSQL Linux ODBC driver v09.06.0100 and newer does not work with Teiid Server 9.1.1
  • [TEIID-4953] - JOIN of CTEs fails if one of them is dependent and has window functions with inner DISTINCT in underlying queries
  • [TEIID-4960] - Problems when using External Materialized Views
  • [TEIID-4961] - External Materialized View With State Loaded but 0 Cardinality
  • [TEIID-4962] - 9.3 teiid-standalone-mode-install.cli gives an error on startup
  • [TEIID-4967] - Couchbase - incorrect data returned from VIEW if one value is NULL
  • [TEIID-4968] - oids are not unique in pg_attribute
  • [TEIID-4969] - Couchbase - ORDER BY returns empty result
  • [TEIID-4970] - Couchbase - GROUP BY returns empty result
  • [TEIID-4972] - Couchbase - query with comparison criteria not properly translated
  • [TEIID-4973] - Couchbase - Teiid returns empty result if source query fails
  • [TEIID-4974] - Couchbase - TRANSLATE function is transalted as REPLACE
  • [TEIID-4975] - Couchbase - SUBSTRING function is not translated correctly
  • [TEIID-4986] - Couchbase import nested array handling
  • [TEIID-4952] - release notes is not having tokens replaced
The next preview release of 10.0 will be due out in about 2 weeks.



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 …