Skip to main content

Posts

Showing posts from June, 2009

Teiid 6.1.0 Released, adds Hibernate Dialect for Teiid

We are excited to announce the availability of Teiid 6.1.0 along with a coordinated release of Teiid Designer 6.1.0 . There are numerous fixes and improvements in this release. See the complete list here . Some of the highlights of the release include: Simplified embedded deployment and configuration. Deployment of embedded in JBoss AS 5.0, Eclipse DTP, Squirrel, etc. is straight-forward. See some examples on our wiki . Resolved class loading issues surrounding the usage of vendor specific drivers. A "Hibernate Dialect" for Teiid is available. Accessing the your "virtualized" data is now as easy as creating a VDB and writing a Hibernate application. Enhanced processing with the introduction of a partitioned merge join, sort optimizations, and a variety of new push down features. Stream based processing for XML connector. Enjoy the features, please be sure let us know what you think. We always welcome your comments and suggestions! Thank you. Teiid Team.

A Relational Data Integration Engine

Teiid has been an open source project for few months now and the response from community has been fairly positive. New users are taking it for test drive and we have busily been executing on our roadmap. Still I sometimes feel, we may have not explained what Teiid software really does? Since I am java six pack , I am going to dumb it down to level that I understand, and present it to you. If you look around Teiid site depending, you will find a multitude of terms and definitions, here are some examples It is a EII (Enterprise Information Integration) tool It is a Virtual Database It is Data Integration Engine Data Mash up Engine Data Virtualization Engine All the above are accurate. But, I want to describe Teiid's base processor more precisely. "Teiid is a Relational Data Integration Engine" Using Teiid and its supplied tools, you build a brand new logical data model for your data in multiple heterogeneous data sources using SQL as glue language. Now, the schema from t