Skip to main content

Teiid 8.12.4 Released

Teiid 8.12.4 has been released.  A somewhat large change is that there is now a new Redshift translator available to account for differences between Redshift and Postgres.  All issues addressed:

  • [TEIID-3874] - Invalid source query for subquery referencing a common table
  • [TEIID-3879] - Error during state transfer prevents a node from loading later
  • [TEIID-3880] - Missing dependency in "org.apache.olingo" module
  • [TEIID-3882] - Unable to convert Geometry Collection to GeoJSON
  • [TEIID-3884] - Queries with NextToken failing with NPE
  • [TEIID-3885] - Redshift - conversion to time does not work
  • [TEIID-3886] - Redshift - query ends with error message "Query cancelled on user's request"
  • [TEIID-3887] - Redshift - RS does not support ASCII function
  • [TEIID-3888] - Redshift - there is not function SUBSTR (RS uses SUBSTRING)
  • [TEIID-3889] - asynch start transaction / rollback throws exception
  • [TEIID-3891] - MetadataFactory create function from method does not account for primitive return types
  • [TEIID-3892] - There is no pg type for geometry
  • [TEIID-3895] - OData - metadata returns primary key with attribute "Nullable=true"
  • [TEIID-3897] - dimensional check for ewkb is incorrect
  • [TEIID-3900] - OData - malformed URL causes NPE
  • [TEIID-3876] - Add an option to import RowId as binary
  • [TEIID-3899] - Allow Web Services translator to retrieve metadata without source connection
  • [TEIID-3270] - Allow UDFs to call Teiid functions
  • [TEIID-3419] - Add ability to set a default role across all VDBs
  • [TEIID-3870] - Add ability to properly qualify package objects
  • [TEIID-3890] - Add a redshift translator
  • [TEIID-3865] - too much logging of source cancel
  • [TEIID-3866] - with clause used by subquery repeated in the subquery
  • [TEIID-3875] - Many info messages upon startup that start with: TEIID31173 Inherent
  • [TEIID-3893] - Handling of binary odbc parameters needs improved
  • [TEIID-3896] - When error occurs in the materialization process, an ERROR should be logged instead of DEBUG
  • [TEIID-3901] - MetadataFactory should account for user defined aggregate functions
This should be the last release on the 8.12.x line.  Expect another Teiid 8.13 CR shortly - with a final release by the end of next week.  From there fixes will be available on the 8.13 line.  Teiid 8.13 has support for Wildfly 9.0.2 support, but no new feature work so that it provides a transitional release into Teiid 9.  Teiid 9.0 Alpha is still expected by the end of January.

Steve

Comments

Popular posts from this blog

Teiid Platform Sizing Guidelines and Limitations

Users/customers always ask us about the sizing of their Data Virtaulization infrastructure based on Teiid or the JDV product from Redhat. Typically this is very involved question and not a very easy one answer in plain terms. This is due to fact that it involves taking into consideration questions like:
What kind of sources that user is working with? Relational, file, CRM, NoSQL etc.How many sources they are trying to integrate? 10, 20, 100?What are the volumes of data they are working with? 10K, 100K, 1M+?What are the query latency times from the sources? How you are using Teiid to implement the data integration/virtualization solution. What kind of queries that user is executing? Even small federated results may take a lot of server side processing - especially if the plan needs tweaking.Is materializing being used?Is query written in optimal way?and so on..Each and every one of the question affects the performance profoundly, and if you got mixture of those then it become that much…

Teiid Runtimes Explained

If you have been following Teiid lately we have been going through a whole lot of renovations. Yes, renovations or reorganization or refactoring or whatever you want to call it. Basically, we are making Teiid more modular with fewer dependencies that can be used by however your use case dictates rather than use it as one monolith application deployed into WildFly JEE Application Server. There is nothing wrong in using Teiid as server model, but with the proliferation of container-based workloads and cloud-based architectures, the previous server-based model does not work or simply won't scale. So, we needed to think of alternatives, thus Teiid team introduced a couple different versions modular Teiid what we are calling as "Teiid Runtimes".

Note that in these modular Teiid runtimes, not all the features you were used to using in Teiid Server model may not be there but you will have extensions to add in those that are most appropriate for your domain. If you are looking …