Skip to main content

Teiid 8.13.4 Released

Teiid 8.13.4 is now available. 8.13.4 addresses 13 issues since 8.13.3:
  • [TEIID-4107] - HSQL Syntax error when Teiid sends it a join query with no parenthesis
  • [TEIID-4109] - spatial_ref_sys reference needs qualified
  • [TEIID-4115] - XMLTABLE single element in sequence invalid conversion
  • [TEIID-4118] - Temp capabilities for null ordering not correct if default is changed
  • [TEIID-4120] - Teiid on Oracle Spatial generates incorrect SQL
  • [TEIID-4123] - Issues with odbc metadata
  • [TEIID-4130] - Prevent blocked exceptions from being thrown in AccessNode open
  • [TEIID-4136] - Sybase/SQL Server translator varchar length incorrect
  • [TEIID-4144] - Mismanagement of output columns in ruleimplementjoinstrategy
  • [TEIID-4151] - AssertionError: Delete failed
  • [TEIID-4160] - Impala - result set is not sorted if ORDER BY is defined in query
  • [TEIID-4168] - Odd resolving error with implicit temp groups
  • [TEIID-4169] - Deployment/start sequence issue
Be sure to also follow the 9.0 development as we are starting to narrow in on the release.

Thanks,
Steve

Comments

  1. Thank you for this new release! Not having any particular requirement, atm, for 8.x, would you suggest to use 9betas instead? I will try it, anyway as soon as possible :) Teiid fast and continue improvements are awesome, imho.

    ReplyDelete
  2. 9.0 has few new features, if you need those, would suggest moving on to it. Once we release 9.0 Final we probably stop any updates on 8.13 and only provide update on 9.0.

    ReplyDelete

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 …