Skip to main content

Teiid 7.1 Final Released

By
Teiid 7.1 continues the 7.x series with numerous features and performance improvements. Here are some highlights:
  • ODBC Support - Support for ODBC access is now available through PostgreSQL ODBC driver clients. See the Client Developer's Guide for more on how to use Teiid's ODBC access.
  • Native Materialized Tables - views marked as materialized without a target table will be materialized internally by Teiid. Materialized view tables will be indexed by the primary key of the view if present and can be controlled through the expanded cache hint. There are also new system procedures refreshMatView and refreshMatViewRow to refresh materialized view table contents.
  • Expanded Cache Hint - The cache hint can now specify pref_mem to indicate that data should prefer to be held in memory, ttl to indicate the time-to-live, and updatable to indicate that a materialized view with a primary key can be updated by row with the refreshMatViewRow system procedure.
  • SQL Support
    • Added NULLS FIST/LAST handling - including pushdown support.
    • Added enhanced numeric stat aggregate functions STDDEV_POP, STDDEV_SAMP, VAR_POP, VAR_SAMP, with pushdown and aggregate decomposition.
    • Added support for the boolean aggregate functions ANY, SOME, EVERY.
    • Added support for using boolean value expression as both criteria and expressions, e.g. "... where boolean_value" or "select x = 1 as boolean_value ...".
    • Changed named procedure syntax to accept param=>value, rather than param=value.
    • Added PRIMARY KEY and the associated index support to temp tables.

  • Parallel Source Queries - reestablished parallel execution of source queries within a query plan along with a prioritized work system to help prevent resource contention.
  • Improved Insert Support - Cross source inserts using a query expression can defer to the source to perform the entire insert atomically with source controlled batching. See maxPreparedInsertBatchSize on any JDBC translator supporting the new InsertWithIterator capability.
  • SHOW Statement - added client handling for the SHOW statement to retrieve query plan information and see parameter values.
  • User Identity - Teiid DataSources in JBossAS connecting to a local Teiid instance can preserve the thread's user identity, rather than requiring a new authentication. See TeiidDataSource.setPassthroughAuthentication.
  • VDB Versioning - The VDB version may be determined by the deployed file name. The expected pattern is .Version.vdb. See the Admin Guide for more on how to use VDB versioning.
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
Labels:

Comments

Post a Comment

Popular posts from this blog

Teiid 8.13.3 Released

By
Teiid 8.13.3 is now  available .  In total 8.13.3 addresses 10 issues since 8.13.2: [ TEIID-4028 ] - adding salesforce-34 resource adapter does not work through the cli [ TEIID-4066 ] - Odata translator ClassNotFoundException: com.sun.ws.rs.ext.RuntimeDelegateImpl [ TEIID-4070 ] - Issues with resource adapters with api modules in wildfly [ TEIID-4089 ] - Teiid JDBC driver does not reset the update count when calling getMoreResults(int) [ TEIID-4093 ] - OData authentication fails with NPE when gss-pattern related properties are included in VDB [ TEIID-4096 ] - AssertionError with independent side of a dependent join that has an ordered limit [ TEIID-3050 ] - allow for more incremental insert with iterator [ TEIID-4075 ] - Netezza translator to support common table expressions [ TEIID-4098 ] - Always preserve columns order in google spreadsheets models [ TEIID-4046 ] - OData - $skip is beeing ignor
10 comments
Read more

Tech Tip: Teiid SQL Language MAKEDEP Hint Explained

By
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
Post a Comment
Read more

Teiid Spring Boot 1.7.0 Released

By
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
Post a Comment
Read more