Skip to main content

Teiid 8.13.2 Released

Teiid 8.13.2 is now available.  Note TEIID-4017 is an important security fix.  It is recommended that anyone running 8.12.x or 8.13.x upgrade to 8.13.2. 

In total 8.13.2 addresses 27 issues since 8.13.1:
  • [TEIID-3872] - Error with odata entity create with generated keys
  • [TEIID-3975] - 8.13+ Teiid Client should work on JRE 1.6
  • [TEIID-3978] - Remove AddressWrapper
  • [TEIID-3979] - Teiid generates queries containing VARCHAR without a size, causing an HSQL syntax error
  • [TEIID-3980] - NPE with Salesforce retrieve query and no matching entity
  • [TEIID-3981] - Salesforce-34 connector dependency on "com.force.api" is wrong
  • [TEIID-3983] - External Materialization MATVIEW_ONERROR_ACTION WAIT problem
  • [TEIID-3989] - PartialResultsWarning not being returned
  • [TEIID-3990] - Issues with nested correlated references
  • [TEIID-3993] - Teiid: indexOutOfBoundsException on union + count distinct query
  • [TEIID-3994] - AliasSymbol wrapping AliasSymbol error
  • [TEIID-3995] - SAP HANA materialization:function loadMatView with argument invalidate set to true problem
  • [TEIID-4003] - Vertica and DB2 translators use incorrect push down of WEEK function
  • [TEIID-4006] - Texttable column header option toString incorrect
  • [TEIID-4007] - Unparseable model name if user changes odata4 context root
  • [TEIID-4008] - Sending teiid varbinary value (x'') to Microsoft SQL Server errors
  • [TEIID-4011] - automatic/autonomous refresh of materialized views does not work
  • [TEIID-4015] - Error or incorrect value when there is a conflict between local and correlated names
  • [TEIID-4017] - EXECUTE IMMEDIATE in anonymous procedure ignores permissions
  • [TEIID-4022] - Materialization issue dynamic SQL command can't be executed due ambiguous group name
  • [TEIID-4023] - Exception with unresolved Array expression hashcode
  • [TEIID-4031] - Missing dependency in module com.fasterxml.jackson.dataformat.yaml
  • [TEIID-4034] - Google spreadsheet translator issues
  • [TEIID-3599] - Excel translator and dynamic filenames
  • [TEIID-3986] - Materialization planning should be sensitive to property changes
  • [TEIID-3987] - SYSADMIN.setProperty should resolve property keys
  • [TEIID-4052] - Dynamic SQL exception should include evaluated sql
Thanks for all of the community efforts in identifying these issues.  There are still several web console issues that will addressed in 8.13.3, which should be available in 2-3 weeks.

Another 9.0 Alpha will be available in a couple of days that includes all of these fixes and more.  Ideally we'll be moving on to Beta releases by the end of March.




  1. Good job guys... and thanks, also for being so committed to the project and for listening and helping so much your community! :) You're awesome.

  2. btw atm I see that the files are there but the download page you linked still has 8.13.1 links...


Post a Comment

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 …