Skip to main content

Teiid 8.12.3 Released

Teiid 8.12.3 has been released.  Issues addressed include:
  • [TEIID-3814] - Rest Web Service URL for VDB
  • [TEIID-3823] - Issues with fetchsize and local connections
  • [TEIID-3827] - multi-source view insert throwing TEIID30492 error
  • [TEIID-3840] - teiid-outh-util.bat - typo in name
  • [TEIID-3841] - sap-nw-gateway translator wrongly encodes when a parameter includes a space
  • [TEIID-3845] - select count(*) query not working on SimpleDB connector in Teiid
  • [TEIID-3846] - Wrong alias rewriting in subqueries
  • [TEIID-3847] - HiveTranslator should not use a Calendar for the Hive getDate
  • [TEIID-3848] - Issue with hive literal timestamps
  • [TEIID-3850] - Source caching with the cache directive can be at the wrong scope
  • [TEIID-3851] - foreign temp additional extension properties not accessible in QMI
  • [TEIID-3854] - Impala translator - ORDER BY clause using incorrect columns when not in SELECT list
  • [TEIID-3857] - ProjectIntoNode should report a transaction required even with iterator processing
  • [TEIID-3858] - Planning error with unrelated sort columns and view removal
  • [TEIID-3682] - Add logon properties to audit messages
  • [TEIID-3831] - For results set caching there should scope metadata for source tables/procedures
  • [TEIID-3829] - olingo module junit test failed
  • [TEIID-3839] - minimize implicit dependencies on sun classes
Depending upon the progression of 8.13 and the criticality of any issues discovered, this may be the last of the fix releases on 8.12.x.  Teiid 8.13 is introducing Wildfly 9 support, but no new feature work so that it provides a transitional release into Teiid 9.  Teiid 8.13 should provide Beta1 next week and the first 9.0 Alpha should be available by the end of January.



Popular posts from this blog

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 …

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…