Skip to main content

Teiid 7.0-Final Released

After a long journey (9 months after 6.2 release), we are very excited to announce the release of Teiid 7.0. We revamped the Teiid architecture and removed quite a bit of legacy MetaMatrix to poise our project for future development. At the same time we now integrate seemlessly with other JBoss technologies such JBoss AS, Microcontainer, JOPR, JBossTM, PicketLink, Netty, etc. Teiid is ready to meet your data integration challenges.

While simplification was a consistent goal of this release, Teiid still supports most of the features available in Teiid 6.2 and earlier. Some notable new features are:
  • The runtime environment. Now Teiid runs inside the JBoss AS. Check out all the benefits in "JCA Container Integration, why Teiid needs it?" series.
  • Simplified Connector development with a split into the Teiid Translator API (largely defined by a single class) and JCA.
  • Enhanced JAAS based security. Many out of the box implementations available.
  • Support for JCA based connectors.
  • JOPR web-based administrative & monitoring tool.
  • Groovy based scripting environment for administrative tasks.
  • Text and web service integration has been redesigned from the ground up to simplify usage.
  • Nearly all of SQL/XML 2003 support has been added, as well as XMLTABLE and XMLQUERY from SQL/XML 2006.
  • The documentation set has been updated and expanded.
  • Many, many and many more features.
See the release notes for more.

In our testing, Teiid 7.0 is significantly fastest with improvements to buffering, threading, and caching. So, why wait? download today, and give it a try.

Teiid 7.0 is just the beginning -- check out Teiid 7.1 roadmap for more exciting features in the pipeline.

Thank you.

Teiid Team

Comments

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