Description of problem: Here is the list of PrestoDB translator bugs which should be included in JDV 6.4.0. TEIID-4676 PrestoDB translator - convert/cast is not properly translated/pushed TEIID-4677 PrestoDB translator - date/time/timestamp values are pushed in Teiid's format ({d/t/ts '...'}) TEIID-4678 PrestoDB translator - log function not translated correctly TEIID-4682 PrestoDB translator - cannot use temp tables - PrestoDB could not commit transaction TEIID-4683 PrestoDB translator - dayof* functions not translated correctly TEIID-4684 PrestoDB translator - format* functions - invalid conversion to 'timestamp with timezone' TEIID-4686 PrestoDB translator - ordering of joined tables fails TEIID-4687 PrestoDB translator - unsupported corelated subquery TEIID-4694 PrestoDB translator - NULL values not supported in SemiJoin TEIID-4706 PrestoDBMetadataProcessor load metadata failed due to Duplicate Table
Adding TEIID-4685
Adding TEIID-4679
Adding TEIID-4680 and TEIID-4681
If it's for 6.4 and not as part of an update release... I'm not concerned.
Van, I do not think this should be targeted for DR1. Moreover, none of the fixes has been in any 6.4.0 build, as I have reported this based on testing with 6.4.0 builds. Failing QA as this is not yet fixed.
Following JIRA issues were resolved by change of project documentation, we need to incorporate them in product docs as well. Assigning to David. TEIID-4686 TEIID-4694 TEIID-4706 See the Tips and Notes in [1] https://teiid.gitbooks.io/documents/content/reference/PrestoDB_Translator.html
I have added all of these into the PrestoDB section.
There are issues in wording of the new content: 1. >The translator property supports OrderBy supports OrderBy -> supportsOrderBy 2. > To check whether support your version supports null as valid values in a subquery see if you can produce a related error. Remove the sentence, it is unwieldy and adds no information value. 3. > PrestoDB does not support transaction. To work around this, define a no-tx-datasource. Reword similar to: PrestoDB does not support transactions. To overcome issues caused by this limitation, define the datasource as non-transactional.
1. Corrected and formatted. 2. Removed. 3. Replaced.
1. > The translator property supportsOrderBy which can be used to disable Order by in some specific situations. remove which
Wording amended.