February 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5898) Wrong force-wsc jar in translator / force.api module 41

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5898?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5898: ---------------------------------- Priority: Critical (was: Major) > Wrong force-wsc jar in translator / force.api module 41 > ------------------------------------------------------- > > Key: TEIID-5898 > URL: https://issues.redhat.com/browse/TEIID-5898 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 12.2 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 13.1, 12.3.2, 13.0.3 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > For some reason between 12.1 and 12.2 the wrong force-wsc began to be picked up in the 41 translator. This was not due to TEIID-5713 as the 12.1.2 kit is correct, so this was likely introduced by the wildfly related refactoring (but it's not clear why). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5898) Wrong force-wsc jar in translator / force.api module 41

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5898?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5898: ---------------------------------- Affects Version/s: 12.2 > Wrong force-wsc jar in translator / force.api module 41 > ------------------------------------------------------- > > Key: TEIID-5898 > URL: https://issues.redhat.com/browse/TEIID-5898 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 12.2 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.1, 12.3.2, 13.0.3 > > > For some reason between 12.1 and 12.2 the wrong force-wsc began to be picked up in the 41 translator. This was not due to TEIID-5713 as the 12.1.2 kit is correct, so this was likely introduced by the wildfly related refactoring (but it's not clear why). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5898) Wrong force-wsc jar in translator / force.api module 41

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5898?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5898: ---------------------------------- Original Estimate: 4 hours Remaining Estimate: 4 hours > Wrong force-wsc jar in translator / force.api module 41 > ------------------------------------------------------- > > Key: TEIID-5898 > URL: https://issues.redhat.com/browse/TEIID-5898 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 12.2 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.1, 12.3.2, 13.0.3 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > For some reason between 12.1 and 12.2 the wrong force-wsc began to be picked up in the 41 translator. This was not due to TEIID-5713 as the 12.1.2 kit is correct, so this was likely introduced by the wildfly related refactoring (but it's not clear why). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5898) Wrong force-wsc jar in translator / force.api module 41

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5898: ------------------------------------- Summary: Wrong force-wsc jar in translator / force.api module 41 Key: TEIID-5898 URL: https://issues.redhat.com/browse/TEIID-5898 Project: Teiid Issue Type: Bug Components: Build/Kits Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 13.0.3, 13.1, 12.3.2 For some reason between 12.1 and 12.2 the wrong force-wsc began to be picked up in the 41 translator. This was not due to TEIID-5713 as the 12.1.2 kit is correct, so this was likely introduced by the wildfly related refactoring (but it's not clear why). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5897) Update srcclr.yml to on 1.0.x branch to run -Prelease profile

by Van Halbert (Jira)

[ https://issues.redhat.com/browse/TEIID-5897?page=com.atlassian.jira.plugi... ] Van Halbert commented on TEIID-5897: ------------------------------------ The [source clear analysis | https://redhatmiddleware.sourceclear.io/workspaces/YEEu3dq/projects/13153...], with this change now has no CVE issues, due to the previous jetty issue was only seen when test were analized. > Update srcclr.yml to on 1.0.x branch to run -Prelease profile > ------------------------------------------------------------- > > Key: TEIID-5897 > URL: https://issues.redhat.com/browse/TEIID-5897 > Project: Teiid > Issue Type: Quality Risk > Components: Build/Kits > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Blocker > > Update the 1.0.x branch srcclr.yml file so that source clear runs the -Prelease profile and the same dependencies are analyzed that are included when the -Prelease profile is run when the code is released. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5897) Update srcclr.yml to on 1.0.x branch to run -Prelease profile

by Van Halbert (Jira)

[ https://issues.redhat.com/browse/TEIID-5897?page=com.atlassian.jira.plugi... ] Van Halbert commented on TEIID-5897: ------------------------------------ PR submitted to add the -Prelease profile to the srcclr.yaml > Update srcclr.yml to on 1.0.x branch to run -Prelease profile > ------------------------------------------------------------- > > Key: TEIID-5897 > URL: https://issues.redhat.com/browse/TEIID-5897 > Project: Teiid > Issue Type: Quality Risk > Components: Build/Kits > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Blocker > > Update the 1.0.x branch srcclr.yml file so that source clear runs the -Prelease profile and the same dependencies are analyzed that are included when the -Prelease profile is run when the code is released. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5897) Update srcclr.yml to on 1.0.x branch to run -Prelease profile

by Van Halbert (Jira)

[ https://issues.redhat.com/browse/TEIID-5897?page=com.atlassian.jira.plugi... ] Van Halbert updated TEIID-5897: ------------------------------- Git Pull Request: https://github.com/teiid/oreva/pull/29 > Update srcclr.yml to on 1.0.x branch to run -Prelease profile > ------------------------------------------------------------- > > Key: TEIID-5897 > URL: https://issues.redhat.com/browse/TEIID-5897 > Project: Teiid > Issue Type: Quality Risk > Components: Build/Kits > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Blocker > > Update the 1.0.x branch srcclr.yml file so that source clear runs the -Prelease profile and the same dependencies are analyzed that are included when the -Prelease profile is run when the code is released. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5897) Update srcclr.yml to on 1.0.x branch to run -Prelease profile

by Van Halbert (Jira)

Van Halbert created TEIID-5897: ---------------------------------- Summary: Update srcclr.yml to on 1.0.x branch to run -Prelease profile Key: TEIID-5897 URL: https://issues.redhat.com/browse/TEIID-5897 Project: Teiid Issue Type: Quality Risk Components: Build/Kits Reporter: Van Halbert Assignee: Van Halbert Update the 1.0.x branch srcclr.yml file so that source clear runs the -Prelease profile and the same dependencies are analyzed that are included when the -Prelease profile is run when the code is released. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

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?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)

4 years, 10 months

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: ---------------------------------- Original Estimate: 5 hours Remaining Estimate: 5 hours Story Points: 1 > 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 > Remaining Estimate: 5 hours > > 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)

4 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2020