Teiid

9.1.4 is available for download or from the Maven repository.  It addresses 8 important issues: [ TEIID-4737 ] - Incorrect work of left join statement [ TEIID-4754 ] - Wrong result with bidirectional relationship [ TEIID-4776 ] - Issues with array type metadata [ TEIID-4791 ] - Bypass lookup function's keycolumn reserved word [ TEIID-4775 ] - External materialization, after transaction timeout, LoadState continues to be LOADING [ TEIID-4778 ] - External Materialization, When TTL is less than loading time, the scheduling is off [ TEIID-4780 ] - Clone TEIID-4734 (Backwards compatible solution) [ TEIID-4782 ] - Change framework to catch RutineException from translator/connector From here the release pace on 9.1.x will slow as primary support will be on the 9.2.x branch. There will also be a 9.3 Alpha1 release next week with significant work toward JDG, materialization, and allowing domain types. Thanks,

Teiid 9.0.6 is now available .  This release contains 12 important fixes: [ TEIID-4663 ] - Support a more secure block mode for client/server encryption [ TEIID-4546 ] - On setting jboss-teiid cluster : throwing java.lang.IllegalArgumentException. [ TEIID-4547 ] - getQueryPlan fails in adminapi [ TEIID-4553 ] - COUNT returns inconsistent results when column statistics are not gathered [ TEIID-4608 ] - Insert statement - multi-value insert into view - incorrect type resolution if first tuple contains NULL [ TEIID-4661 ] - Subsequent queries hang after materialized view TTL expires. [ TEIID-4668 ] - Google translator skips NULL value in INSERT [ TEIID-4710 ] - Request id conflict with CommandContext connection [ TEIID-4727 ] - Aggregation is performed incorrectly for JOIN queries [ TEIID-4732 ] - Teiid Server does not honor columns name in external materialization [ TEIID-4737 ] - Incorrec

Teiid community is very excited to announce that with 9.2 release we have extended the support to define VDB completely in DDL. Previous to this version, a Virtual Database (VDB) is defined either using combination of XML/DDL format or one could have designed using Teiid Designer, which is in custom binary format (.vdb) So, what the big deal? Well when you look at any traditional relational database, DDL is primary language to create any database and its Schema. Even though Teiid is a Data Virtualization engine, for consumers it always behaves like a relational database. Having separate concepts to define your schema really impedes the adoption and learning curve for a developer. We want to make working with Teiid, as simple as you working with any relational database. However, Teiid needs are different than a traditional databases, in that Teiid needs to interface with external systems, now how can that be represented? that is where SQL-MED specification comes to light. What is

It's been 4 months of hard work and we're ready to sign off on the 9.2 Final release .  Feature highlights include: TEIID-4284 Salesforce Bulk API for SELECT queries. TEIID-4556 TEIID-4545 TEIID-4515 Phoenix/Hbase Translator now supports joins, more system functions/pushdown functions, and offset TEIID-4532 Hashing Functions were added for md5, sha1, sha2-256, and sha2-512. TEIID-4627 Source Triggers to handle source change events. TEIID-4643 Encrypt/decrypt functions were added for 128bit AES. TEIID-4622 Data Quality Functions contributed by OSDQ. TEIID-4441 FTP/SFTP Connectivity via a new ftp resource adapter. TEIID-4629 DDL Replacement for vdb.xml to eliminate the need to mix XML and DDL. TEIID-4398 VDB Migration tool - Migration tool to convert .vdb & -vdb.xml files into DDL based VDB In addition to reading up on the individual JIRA issues, here's a summary of where several important efforts stand. DDL Support The DDL option (TEII

We are nearing the final release of 9.2.  CR1 can be downloaded or is available from Maven. A feature was added since Beta2: TEIID-4398 VDB Migration tool - Migration tool to convert .vdb & -vdb.xml files into DDL based VDB At over 160 issues addressed this is a pretty significant release.  We'll now work hard to close out the remaining issues and make sure the documentation is ready.  Thanks to all who have brought issues to our attention.  In particular Pedro Inácio highlighted several issues with external materialization management. Please try out all of issues on the CR to provide feedback before the final release.  If nothing significant is found we'll be ready for a final in about a week to 10 days. Thank you, Steve

9.1.3 is available for download or from the Maven repository.  It address 17 important issues: [ TEIID-4298 ] - Support in Odata4 for the Partner NavigationProperty attribute [ TEIID-4633 ] - Odata $expand over Oracle tables generates bad query [ TEIID-4644 ] - anonymous block dynamic issues [ TEIID-4679 ] - PrestoDB translator - locate function - source specific function has different order of arguments [ TEIID-4680 ] - PrestoDB translator - error executing locate(string, string, int) [ TEIID-4681 ] - PrestoDB tranlator - NPE while executing CHR function with illegal argument (char) [ TEIID-4685 ] - PrestoDB translator - IFNULL is translated as NULLIF [ TEIID-4692 ] - upsert delegating override not correct [ TEIID-4693 ] - mysql "booleans" translation issues [ TEIID-4698 ] - Adding an INFO validation to a model can invalidate the vdb [ TEIID-4700 ] - Google translator incon