Skip to main content

Dynamic VDBs Are Back With A Punch!!!

You did not think we removed this feature from Teiid forever did you? In earlier releases of Teiid 8.0 cycles, Dynamic VDBs were not supported due to lack of non-archive file based deployment support from the JBoss AS 7. Now that  JBoss AS 7.1.0-Final has been released they added much needed feature to enable the Dynamic VDBs. With that we are announcing the first release of Teiid that is based on JBoss AS 7.1.0-Final.

Teiid 8.0.Beta1 is released today. Teiid 8.0.Final will also be based upon same version of JBoss AS. This release brings back Dynamic VDB feature, but that is not the big news. Now you can define virtual tables, procedures and functions as you did in Teiid Designer based VDB are now can be defined in the Dynamic VDBs using DDL with out Teiid Designer. Yes, using DDL! This can lead design of Virtual Databases that are more dynamic in nature that can be changed programatically. Without any more non-sense here is quick example.

The below example is extension of the example from Quick Start Guide, so if you are new to Teiid start with that example. Also a full project with all files is also available in the Teiid download archive in the examples section (see docs/teiid/examples/dynamicvdb-portfolio)

dynamic-portfolio-vdb.xml
 <vdb name="DynamicPortfolio" version= "1">  
   <model name="MarketData">  
     <source name="text-connector" translator-name="file" connection-jndi-name="java:/marketdata-file"/>  
   </model>  
   <model visible = "true" type = "VIRTUAL" name = "portfolio">  
      <metadata import-type = "DDL"><![CDATA[  
        CREATE VIEW stock (  
         symbol varchar,  
         price decimal  
         ) AS   
          select stock.* from (call MarketData.getTextFiles('*.txt')) f,   
          TEXTTABLE(f.file COLUMNS symbol string, price bigdecimal HEADER) stock;  
      ]]>  
      </metadata>  
   </model>  
 </vdb>  

Note in the "portfolio" model, we created a VIEW (stock) that is based on the procedure "getTextFiles", which is exposed by a "file" translator. What we effectively have done here is turned some data from CSV file into a table using "TEXTTABLE", and exposed those results as a table. In prior Teiid 7.x releases you could have defined the "TEXTTABLE" construct as shown in view query above after "AS" keyword, however there was no facility to define an abstraction (or logical) view to expose the results of TEXTTABLE. So, when you deploy the above VDB, you can issue queries like

 SELECT * FROM stock WHERE price > 50.00  

using your JDBC connection to the Teiid's Virtual Database. This effectively created an abstraction for your end users, to hide the real details behind your data integration. That is one of basic tenants of data virtualization.

Read related documentation on this feature at https://docs.jboss.org/author/display/TEIID/View+Definitions+in+VDB

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