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.

Thanks,

Steve

Comments

  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.

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

    ReplyDelete

Post a Comment

Popular posts from this blog

Teiid 8.11 Beta1 and 8.10.1 Released

Teiid 8.11 Beta1 is now available from the  downloads  and maven.  Feature highlights since Alpha2 include: TEIID-3434 More caching control over ttls in the result set cache down to the schema/table level. TEIID-3412 MS Access support via the UCanAccess driver. The UCanAccess support is necessary for those running on Java 1.8 as the JDBC ODBC bridge has been removed from the JRE. The waiting continues on EAP 6.4 Alpha1 - it still should be available shortly and should be the platform target for Teiid 8.11 Beta2. Of course, let us know if you find any issues with these early releases.  There's still plenty of time to get fixes into the final release. Teiid 8.10.1 is also available.  It addresses 5 important issues discovered since 8.10 was released: [ TEIID-3409 ] - PostgreSQLExecutionFactory TranslatorProperty annotation in wrong place [ TEIID-3437 ] - Inconsistencies with row count handling [ TEIID-3438 ] - Null value returned from BlobImpl

Tech Tip: Teiid SQL Language MAKEDEP Hint Explained

In this article I will explain what a MAKEDEP hint is, how and when, why it should be used in Teiid. What: MAKEDEP is query hint.  When a query hint is defined in the SQL query it influences the Teiid query planner to optimize the query in a way that is driven by the user. MAKEDEP means "make this as a dependent join". What is a Dependent Join? For example if we have query like: SELECT * FROM X INNER JOIN Y ON X.PK = Y.FK Where the data for X, and Y are coming from two different sources like Oracle and WebService in Teiid, so in relational algebra you can represent above query as Here the result tuples from node X and node Y are being simultaneously fetched by Teiid query engine, then it joins the both the results inside Teiid engine based on the specified X.PK = Y.PK condition and returns the filtered resulted to the user. simple.. Now, what if, if X table has 5 rows and Y table has 100K rows? In order to do the JOIN naively Teiid need sto read all the 5

Teiid Spring Boot 1.7.0 Released

Teiid Spring Boot version 1.7.0 to support Teiid 16.0 has been released. This release is mainly to support the Teiid's latest version.  In this release, the support for OpenAPI code generation based on VDB has been removed as there is no community interest and moreover it was at OpenAPI 2.0, and the industry has moved to 3.0 and beyond. There are no plans to further pursue this feature. VDB maven plugin was also removed, which was intended to be a replacement for the VDB importing feature was to be used when working on OpenShift, however, since it requires the Maven repository and does not completely represent the feature as defined on the WildFly based deployments this is also removed. You can still use the VDB import feature with Teiid Spring Boot, simply define the VDB with your "IMPORT DATABASE" statements and provide the additional files along with the main VDB file. During the start of the application, Teiid Spring Boot will load all the necessary DDL files for the