Skip to main content

Domain Mode Aware Teiid

Teiid 8.0.0.Beta2 is released today with  "domain mode" support provided by JBoss AS 7. This release is based on JBoss AS 7.1.1

So, what does "domain mode" provide to Teiid?

When you have more than one JBoss AS instance in your server farm and if they are started in domain mode, all the configuration options of this server farm can be centrally managed. For example, you can deploy a VDB or create a data source across all the instances, with one single CLI based call.  Teiid extends this configuration concept to deploy the VDBs, Translators across the whole server farm.

Also, when domain mode is combined with "HA (high availability)" profile, one can cluster the JBoss AS server instances that are deployed. Teiid chooses the HA profile as default profile in its "domain-teiid.xml" file. When the Server is started using the "domain-teiid.xml" the distributed caching that is used for ResultSet caching and Internal Materialized caching is automatically configured. The usage of Admin API is same in both standalone mode and domain mode. See the following document to start in Domain Mode with cluster capabilities.

When multiple Teiid instances are available in a cluster, you can make use load balancing and fail-over features. Check out Teiid documents.

Other Stuff

We are fast approaching CR1 release in next couple weeks, then soon followed by  8.0.0-Final, so check your use cases and let us know if you see any issues before it is too late to get them into 8.0.0-Final.

We are also planning the 8.1 work currently, so if you have any feature(s) you think that Teiid should implement speak up and open a dialogue in Teiid forums.

We are looking for GWT experts to help us with Teiid Console application in 8.1, so if you got some time to spare and want to contribute back to Teiid, please contact us.

Download and try it out and let us know if you see any issues or question in Teiid forums.

Thank you.

Ramesh.. 

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