Thursday, November 12, 2015

Teiid 8.12.2 Available

Teiid 8.12.2 is now available.  Issues addressed since 8.12.1 include:
  • [TEIID-3795] - Order of VARIADIC parameters is not preserved
  • [TEIID-3799] - Insert default expressions not rewritten
  • [TEIID-3802] - HANA translator modifies boolean to tinyint in type conversion
  • [TEIID-3803] - Kerberos with ODBC with MutualAuth fails
  • [TEIID-3806] - Improve null resolving in array literals
  • [TEIID-3807] - quantified comparison results dependent on null ordering
  • [TEIID-3812] - HANA MIN and MAX functions not applicable on boolean
  • [TEIID-3813] - Informix translator - convert function in definition of view is not pushed down
  • [TEIID-3815] - Oracle translator - OFFSET function does not work
  • [TEIID-3817] - HANA FLOOR and CELING functions not applicable to boolean
  • [TEIID-3818] - Issues with ODBC metadata foreign key queries
  • [TEIID-3819] - SimpleDB NullPointerException when inserting null value
  • [TEIID-3581] - Add a system function to return Teiid Server Name
  • [TEIID-3582] - Add the query requestID to all lines for that query in the logs
  • [TEIID-3793] - Push Teiid function LOCATE() to SQL Server
  • [TEIID-3821] - Expand xml output types
  • [TEIID-3717] - Enable SNI (Server Name Indication) support
  • [TEIID-3787] - ignored properties in dynamic vdb should be flagged with a WARN log entry
  • [TEIID-3811] - Teiid Embedded with remote JDBC susceptible to exploit with common-collections in classpath
  • [TEIID-3820] - SimpleDB column import order may not be consistent

If you are using Teiid Embedded with socket based JDBC access enabled and have spring, common-collections, or groovy in the classpath, then you should upgrade to 8.12.2 due to TEIID-3811 to prevent deserialization attacks.

There have been a few delays in the 8.13 pre-releases as there has been more changes in the AS/Wildfly integration apis and it has been a larger effort than expected to normalize our dependencies.  Ideally we're still on track for an alpha release in the next week or two.

Thanks again for all the community support,
Steve

No comments:

Post a Comment