Skip to main content

Teiid 7.2 Final Released

We are pleased to announce Teiid 7.2 with numerous features, improvements, and bug fixes. Here are some highlights:
  • SQL Support
    • Non-Recursive Common Table Expressions - The WITH clause (and associated pushdown) for non-recursive queries is now supported.
    • Explicit Table Syntax - TABLE x can now be used as a shortcut for SELECT * FROM x
  • JSON Support - JSON, which could be obtained through the ws-translator using http calls or other methods, can be converted to XML using the system function jsonToXml. XMLTABLE and other integration logic can then be used on the JSON results.
  • Transaction Statements - JDBC/ODBC now accepts START TRANSACTION, COMMIT, and ROLLBACK statements to control local transactions.
  • Procedure Result Caching - virtual procedure definitions may use a cache hint to cache results in the result set cache.
  • Improved Plan Caching - plans used by internal materialization and stored procedure plans will be automatically cached in the prepared plan cache. Improvements were also made to reduce the memory footprint of the plans.
  • Refined Load Balancing and Fail Over - clients can use use the statement "SET NEWINSTANCE TRUE" to allow their connection to select a new server instance. See the Client Developer's Guide for more information.
  • Simplified Role Usage - a role can now be assigned to any authenticated user via the any-authenticated attribute on the data-role element.
  • Materialized View Performance - materialized view tables will now automatically create and use non-unique secondary indexes for unique constraints and indexes defined on the view.
  • Binary Web Service Calls - the ws translator now provides an invokeHttp procedure to return the blob contents and string content type of an http/https call.
  • Improved clustering support - see the Admin Guide chapter on clustering.
  • IPv6 support - Teiid can started using IPv6 bind address and can be used with JDBC connection.
  • SESSION_ID - A new system function "SESSION_ID" is added to the system function library.
  • Assignment Syntax Improvements - Teiid's procedure syntax for assignments was clarified so that the assignment value must be a proper expression. INSERT/UPDATE/DELETE update counts must be obtained from VARIABLES.ROWCOUNT, scalar values must be obtained via a scalar subquery. The parser will continue to accept the old syntax and convert the query into the proper form.
  • TEXTAGG - SQL support for Text aggregation. Using this function expression values can be aggregated into a CSV BLOB with configurable delimiter, header, and encoding. The result can be optionally saved to a text file.
See the release notes for more details. Download today, give it try, and let us know what you think and what features you would want in upcoming releases.

The Teiid Team

Comments

  1. hi! congratulation for the new release!
    btw, i was still looking for the 7.1 release, but can't find it on sourceforge...? why, and where is it gone? is the "teiid designer 7.1" compatible with "teiid 7.2"?

    Thanks marco

    ReplyDelete
  2. Marco,

    The 7.1 release was posted to the jboss.org download site: http://downloads.jboss.org/teiid/7.1.0.Final/teiid-7.1.0.Final-jboss-dist.zip

    At the time we were looking at making a switch over, but decided to stay at sourceforge. We'll add 7.1 to sourceforce to prevent confusion.

    Yes, designer 7.1 should be compatible with teiid 7.2. There should be a 7.2 designer shortly.

    Steve

    ReplyDelete
  3. really kind, perfect! :)

    do you suggest a newbie to try
    a) teiid 7.1 with designer 7.1
    b) teiid 7.2 with designer 7.1
    c) teiid 7.2 with designer 7.2, as soon as it will be released?

    Marco

    ReplyDelete
  4. Starting with Teiid 7.2 and Designer 7.1 should be good.

    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