June 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4228) ODBC "Parse Statements" option can result in changes in LENGTH metadata for columns

by Steve Tran (JIRA)

[ https://issues.jboss.org/browse/TEIID-4228?page=com.atlassian.jira.plugin... ] Steve Tran commented on TEIID-4228: ----------------------------------- The JDBC Importer is setting the Precision Field to 0. I changed the precision to 15 to match a different table that has similar datatypes and the problem went away. This might be a regression in Teiid Designer because this other table I matched was previously imported with Teiid Designer too. > ODBC "Parse Statements" option can result in changes in LENGTH metadata for columns > ----------------------------------------------------------------------------------- > > Key: TEIID-4228 > URL: https://issues.jboss.org/browse/TEIID-4228 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 8.7 > Environment: Connections through ODBC driver > Reporter: Marc Shirley > Assignee: Steven Hawkins > Priority: Minor > Fix For: 9.x > > > Connections through ODBC driver with the driver setting "Parse Statements" option enabled can result in incorrect length values being passed to the client. In some cases (such as SQL Server linked server capabilities), this can result in the client throwing exceptions due to the expected LENGTH changing during the course of the query execution. > This may be limited to columns with precision set to 0, as the SQL Server linked server case was corrected when the precision was changed from 0 to 9 for the column specified in the error. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4295) TEIID31150 when using date function with MSSQL

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4295?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4295. ----------------------------------- Resolution: Out of Date Tested the same scenario against latest without an issue. > TEIID31150 when using date function with MSSQL > ---------------------------------------------- > > Key: TEIID-4295 > URL: https://issues.jboss.org/browse/TEIID-4295 > Project: Teiid > Issue Type: Feature Request > Reporter: Mark Tawk > Assignee: Steven Hawkins > > I'm using teiid version 8.11.3 > I have a field of type date over mssql 2012, when applying a date function over it, i get directly the error : > org.teiid.jdbc.TeiidSQLException: TEIID31150 The function 'YEAR(testmark.mydate)' is ambiguous. Use schema qualification. > if I change the field type to datetime, the query executes successfully. > Here is the simplified query i'm testing with: > select YEAR("testmark"."mydate") as "testmark_mydate" from "implify_dataModel_at"."implify_data"."implify_red2"."testmark" "testmark" LIMIT 0 , 10 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4304) Correct handling with subquery in on clause

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4304?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4304: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1351182, https://bugzilla.redhat.com/show_bug.cgi?id=1351303 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1351182) > Correct handling with subquery in on clause > ------------------------------------------- > > Key: TEIID-4304 > URL: https://issues.jboss.org/browse/TEIID-4304 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 9.0.1, 8.7.8.6_2 > > > With the translator capability supportsSubqueryInOn false, we can still plan a query with a subquery in the on clause if non-join criteria on the inner side of a left outer join is used in the user query on clause (it is temporarily pushed out of the join and then added back in rule collapse source). > Additionally the oracle translator should not support subquery in on for oracle 11 and earlier. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4304) Correct handling with subquery in on clause

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4304?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4304: --------------------------------------- This will needed queued for 8.12.x as well. > Correct handling with subquery in on clause > ------------------------------------------- > > Key: TEIID-4304 > URL: https://issues.jboss.org/browse/TEIID-4304 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 9.0.1, 8.7.8.6_2 > > > With the translator capability supportsSubqueryInOn false, we can still plan a query with a subquery in the on clause if non-join criteria on the inner side of a left outer join is used in the user query on clause (it is temporarily pushed out of the join and then added back in rule collapse source). > Additionally the oracle translator should not support subquery in on for oracle 11 and earlier. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3866) with clause used by subquery repeated in the subquery

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3866?page=com.atlassian.jira.plugin... ] Johnathon Lee reopened TEIID-3866: ---------------------------------- > with clause used by subquery repeated in the subquery > ----------------------------------------------------- > > Key: TEIID-3866 > URL: https://issues.jboss.org/browse/TEIID-3866 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.13, 8.12.4 > > > A query such as: > with eee as (select * from pm1.g1) select * from pm1.g2 where pm1.g2.e1 in (select e1 from eee) > will result in a push down that repeats the with clause in the subquery: > ... (with eee ... select e1 from eee) > It is sufficient to rely on the parent to define the common table. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3866) with clause used by subquery repeated in the subquery

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3866?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3866: --------------------------------- Fix Version/s: 8.7.8.6_2 > with clause used by subquery repeated in the subquery > ----------------------------------------------------- > > Key: TEIID-3866 > URL: https://issues.jboss.org/browse/TEIID-3866 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.13, 8.12.4, 8.7.8.6_2 > > > A query such as: > with eee as (select * from pm1.g1) select * from pm1.g2 where pm1.g2.e1 in (select e1 from eee) > will result in a push down that repeats the with clause in the subquery: > ... (with eee ... select e1 from eee) > It is sufficient to rely on the parent to define the common table. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4304) Correct handling with subquery in on clause

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4304?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4304: --------------------------------- Fix Version/s: 8.7.8.6_2 > Correct handling with subquery in on clause > ------------------------------------------- > > Key: TEIID-4304 > URL: https://issues.jboss.org/browse/TEIID-4304 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 9.0.1, 8.7.8.6_2 > > > With the translator capability supportsSubqueryInOn false, we can still plan a query with a subquery in the on clause if non-join criteria on the inner side of a left outer join is used in the user query on clause (it is temporarily pushed out of the join and then added back in rule collapse source). > Additionally the oracle translator should not support subquery in on for oracle 11 and earlier. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3754) Remove OData V2 implementation of the Server

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3754?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3754: --------------------------------------- Yes, I think we are good. > Remove OData V2 implementation of the Server > -------------------------------------------- > > Key: TEIID-3754 > URL: https://issues.jboss.org/browse/TEIID-3754 > Project: Teiid > Issue Type: Task > Components: OData > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 9.1 > > > We need to remove server implementation of OData V2 specification from Teiid in favor of OData V4. > The OData V2 translator, we should keep, however that may needs to be updated/re-written using the Olingo. However that is separate issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3754) Remove OData V2 implementation of the Server

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3754?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3754: ------------------------------------- Do we feel confident to pull the plug on this? +1 from my side. > Remove OData V2 implementation of the Server > -------------------------------------------- > > Key: TEIID-3754 > URL: https://issues.jboss.org/browse/TEIID-3754 > Project: Teiid > Issue Type: Task > Components: OData > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 9.1 > > > We need to remove server implementation of OData V2 specification from Teiid in favor of OData V4. > The OData V2 translator, we should keep, however that may needs to be updated/re-written using the Olingo. However that is separate issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4247) OData - support date and time functions

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4247?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-4247. --------------------------------- Resolution: Done > OData - support date and time functions > --------------------------------------- > > Key: TEIID-4247 > URL: https://issues.jboss.org/browse/TEIID-4247 > Project: Teiid > Issue Type: Feature Request > Components: OData > Affects Versions: 8.12.x > Reporter: Andrej Šmigala > Assignee: Ramesh Reddy > Fix For: 9.1 > > > The functions date() and time() are currently not supported in odata queries, e.g. running query {noformat}http://localhost:8080/odata4/olingo_basic/Source/SimpleDataTable?$filter=timeval%20gt%20time(now()){noformat} > returns {code:xml} > <?xml version='1.0' encoding='UTF-8'?> > <error xmlns="http://docs.oasis-open.org/odata/ns/metadata"> > <code>TEIID16027</code> > <message>TEIID16027 Function time is not currently supported </message> > </error> > {code} > This is allowed behaviour per the [odata spec|http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/par...], but it would be good to have these functions implemented. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2016