February 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5896) enable EXTRACT EPOCH/QUARTER from timestamp

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5896?focusedWorklogId=12450044&pag... ] Steven Hawkins logged work on TEIID-5896: ----------------------------------------- Author: Steven Hawkins Created on: 05/Feb/20 9:03 AM Start Date: 05/Feb/20 9:03 AM Worklog Time Spent: 5 hours Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 5 hours) Time Spent: 5 hours Worklog Id: (was: 12450044) > enable EXTRACT EPOCH/QUARTER from timestamp > ------------------------------------------- > > Key: TEIID-5896 > URL: https://issues.redhat.com/browse/TEIID-5896 > Project: Teiid > Issue Type: Enhancement > Components: Grammar > Affects Versions: 12.3.1 > Reporter: Ken Geis > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.1 > > Original Estimate: 5 hours > Time Spent: 5 hours > Remaining Estimate: 0 minutes > > I am connecting to Teiid from Tableau using the JDBC driver and PostgreSQL dialect. I try to drill into a timestamp field, and I get some complaints parsing the SQL. In particular, it has trouble with: > {code:java} > EXTRACT(QUARTER FROM the_time) > EXTRACT(EPOCH FROM the_time) > {code} > The docs suggest these datetime components are not supported by Teiid. They are not standard, but supporting them would get me a step closer to running Tableau against Teiid (a killer app!) > I was able to work around the QUARTER by dismissing the error, drilling down to month, dismissing the error again, then dragging the quarter out of my drill-down. > I worked around the EPOCH by moving a date difference from being calculated in Tableau to calculating it in Teiid with TIMESTAMPDIFF. > An alternate I tried was using Tableau's SQL92 dialect, but it issues a "SELECT TOP" clause that is not SQL92 standard and also not supported by Teiid. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5896) enable EXTRACT EPOCH/QUARTER from timestamp

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5896?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-5896. ----------------------------------- Resolution: Done Added the extract targets for quarter and epoch. We already supported a quarter function, so that didn't require any additional changes. An epoch function was added to support microsecond precision (the same as pg and double won't support all the way to nanoseconds). > enable EXTRACT EPOCH/QUARTER from timestamp > ------------------------------------------- > > Key: TEIID-5896 > URL: https://issues.redhat.com/browse/TEIID-5896 > Project: Teiid > Issue Type: Enhancement > Components: Grammar > Affects Versions: 12.3.1 > Reporter: Ken Geis > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.1 > > > I am connecting to Teiid from Tableau using the JDBC driver and PostgreSQL dialect. I try to drill into a timestamp field, and I get some complaints parsing the SQL. In particular, it has trouble with: > {code:java} > EXTRACT(QUARTER FROM the_time) > EXTRACT(EPOCH FROM the_time) > {code} > The docs suggest these datetime components are not supported by Teiid. They are not standard, but supporting them would get me a step closer to running Tableau against Teiid (a killer app!) > I was able to work around the QUARTER by dismissing the error, drilling down to month, dismissing the error again, then dragging the quarter out of my drill-down. > I worked around the EPOCH by moving a date difference from being calculated in Tableau to calculating it in Teiid with TIMESTAMPDIFF. > An alternate I tried was using Tableau's SQL92 dialect, but it issues a "SELECT TOP" clause that is not SQL92 standard and also not supported by Teiid. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5896) enable EXTRACT EPOCH/QUARTER from timestamp

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5896?page=com.atlassian.jira.plugi... ] Work on TEIID-5896 started by Steven Hawkins. --------------------------------------------- > enable EXTRACT EPOCH/QUARTER from timestamp > ------------------------------------------- > > Key: TEIID-5896 > URL: https://issues.redhat.com/browse/TEIID-5896 > Project: Teiid > Issue Type: Enhancement > Components: Grammar > Affects Versions: 12.3.1 > Reporter: Ken Geis > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.1 > > > I am connecting to Teiid from Tableau using the JDBC driver and PostgreSQL dialect. I try to drill into a timestamp field, and I get some complaints parsing the SQL. In particular, it has trouble with: > {code:java} > EXTRACT(QUARTER FROM the_time) > EXTRACT(EPOCH FROM the_time) > {code} > The docs suggest these datetime components are not supported by Teiid. They are not standard, but supporting them would get me a step closer to running Tableau against Teiid (a killer app!) > I was able to work around the QUARTER by dismissing the error, drilling down to month, dismissing the error again, then dragging the quarter out of my drill-down. > I worked around the EPOCH by moving a date difference from being calculated in Tableau to calculating it in Teiid with TIMESTAMPDIFF. > An alternate I tried was using Tableau's SQL92 dialect, but it issues a "SELECT TOP" clause that is not SQL92 standard and also not supported by Teiid. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5896) enable EXTRACT EPOCH/QUARTER from timestamp

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5896?page=com.atlassian.jira.plugi... ] Steven Hawkins reassigned TEIID-5896: ------------------------------------- Assignee: Steven Hawkins (was: Barry LaFond) > enable EXTRACT EPOCH/QUARTER from timestamp > ------------------------------------------- > > Key: TEIID-5896 > URL: https://issues.redhat.com/browse/TEIID-5896 > Project: Teiid > Issue Type: Enhancement > Components: Grammar > Affects Versions: 12.3.1 > Reporter: Ken Geis > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.1 > > > I am connecting to Teiid from Tableau using the JDBC driver and PostgreSQL dialect. I try to drill into a timestamp field, and I get some complaints parsing the SQL. In particular, it has trouble with: > {code:java} > EXTRACT(QUARTER FROM the_time) > EXTRACT(EPOCH FROM the_time) > {code} > The docs suggest these datetime components are not supported by Teiid. They are not standard, but supporting them would get me a step closer to running Tableau against Teiid (a killer app!) > I was able to work around the QUARTER by dismissing the error, drilling down to month, dismissing the error again, then dragging the quarter out of my drill-down. > I worked around the EPOCH by moving a date difference from being calculated in Tableau to calculating it in Teiid with TIMESTAMPDIFF. > An alternate I tried was using Tableau's SQL92 dialect, but it issues a "SELECT TOP" clause that is not SQL92 standard and also not supported by Teiid. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5896) enable EXTRACT EPOCH/QUARTER from timestamp

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5896?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5896: ---------------------------------- Fix Version/s: 13.1 Sprint: DV Sprint 59 > enable EXTRACT EPOCH/QUARTER from timestamp > ------------------------------------------- > > Key: TEIID-5896 > URL: https://issues.redhat.com/browse/TEIID-5896 > Project: Teiid > Issue Type: Enhancement > Components: Grammar > Affects Versions: 12.3.1 > Reporter: Ken Geis > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.1 > > > I am connecting to Teiid from Tableau using the JDBC driver and PostgreSQL dialect. I try to drill into a timestamp field, and I get some complaints parsing the SQL. In particular, it has trouble with: > {code:java} > EXTRACT(QUARTER FROM the_time) > EXTRACT(EPOCH FROM the_time) > {code} > The docs suggest these datetime components are not supported by Teiid. They are not standard, but supporting them would get me a step closer to running Tableau against Teiid (a killer app!) > I was able to work around the QUARTER by dismissing the error, drilling down to month, dismissing the error again, then dragging the quarter out of my drill-down. > I worked around the EPOCH by moving a date difference from being calculated in Tableau to calculating it in Teiid with TIMESTAMPDIFF. > An alternate I tried was using Tableau's SQL92 dialect, but it issues a "SELECT TOP" clause that is not SQL92 standard and also not supported by Teiid. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5846) Support "order by" by default in the salesforce translator

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5846?page=com.atlassian.jira.plugi... ] Work on TEIID-5846 started by Steven Hawkins. --------------------------------------------- > Support "order by" by default in the salesforce translator > ---------------------------------------------------------- > > Key: TEIID-5846 > URL: https://issues.redhat.com/browse/TEIID-5846 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Environment: teiid-spring-boot+spring-odata teiid+spring-data-salesforce > Reporter: Renat Eskenin > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.1 > > > When we call simple request as > salesforce-odata-facade/odata/salesforce/Product_License__c?$top=1&$select=Id > request processing time is 1min. But this request processing by simple SOAP SOQL request is ~150ms. > I think this do because teiid select all objects by ignoring top in request. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4992) Add OSDQ set functions

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-4992?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-4992. ----------------------------------- Fix Version/s: (was: 13.x) Resolution: Won't Do > Add OSDQ set functions > ---------------------- > > Key: TEIID-4992 > URL: https://issues.redhat.com/browse/TEIID-4992 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Attachments: SetUtil.java > > > There will be a new osdq core library drop in maven central soon containing additional functions for Teiid to add. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5611) Add support for SCRAM-SHA-256

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5611?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5611: ---------------------------------- Fix Version/s: 13.1 (was: 13.x) > Add support for SCRAM-SHA-256 > ----------------------------- > > Key: TEIID-5611 > URL: https://issues.redhat.com/browse/TEIID-5611 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.1 > > > MongoDB has added support for a new security type, which needs additional support in the resource adapter. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5527) show plan over pg protocol needs some thought

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5527?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-5527. ----------------------------------- Fix Version/s: (was: 13.x) Resolution: Duplicate Issue Duplicate of TEIID-5740 > show plan over pg protocol needs some thought > --------------------------------------------- > > Key: TEIID-5527 > URL: https://issues.redhat.com/browse/TEIID-5527 > Project: Teiid > Issue Type: Quality Risk > Components: ODBC > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > > Depending upon the client and the particulars of processing - simple or extended query protocol - issuing a show plan may not give the relevant plan. For example if you obtain a resultset using the jdbc client and a simple query has been issued, a show plan at the end of processing will actually show some of the under the covers metadata queries. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5860) Salesforce translator should support self joins

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5860?page=com.atlassian.jira.plugi... ] Work on TEIID-5860 started by Steven Hawkins. --------------------------------------------- > Salesforce translator should support self joins > ----------------------------------------------- > > Key: TEIID-5860 > URL: https://issues.redhat.com/browse/TEIID-5860 > Project: Teiid > Issue Type: Enhancement > Components: Salesforce Connector > Reporter: Renat Eskenin > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.1 > > > In this query > {code} > SELECT originalLicense.Id,originalLicense.Status__c,originalLicense.ReplacementLicenseID__c,originalLicense.LicenseId__c,originalLicense.vlic_Contract_Number__c,replacementLicense.LicenseId__c as replacementLicenseId ,replacementLicense.LicenseId__c as replacementLicenseLicenseId FROM Product_License__c originalLicense LEFT OUTER JOIN /*+ MAKEDEP */ Product_License__c replacementLicense ON originalLicense.ReplacementLicenseID__c = replacementLicense.Id where originalLicense.vlic_Contract_Number__c = :contractNumber > {code} > We have two requests to salesforce, but could generate a single SOQL query. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2020