August 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3613) Greedy join planning above exhaustive threshold issues

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3613: ------------------------------------- Summary: Greedy join planning above exhaustive threshold issues Key: TEIID-3613 URL: https://issues.jboss.org/browse/TEIID-3613 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.12 For large join regions (above 6 tables), the greedy choice of the next table to add is not correct. It is not initially removing the already chosen order, and it is not appropriately costing when a start index is passed to the scoring function. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3531) Better planning of bushy join trees

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3531?page=com.atlassian.jira.plugin... ] Work on TEIID-3531 started by Steven Hawkins. --------------------------------------------- > Better planning of bushy join trees > ----------------------------------- > > Key: TEIID-3531 > URL: https://issues.jboss.org/browse/TEIID-3531 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12 > > > The primary join planning logic considers left linear trees. We also have a hint to preserve structure and some planning that reuses existing subtrees, but nothing general around considering bushy trees. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3612) NPE in connectorworkitem after close

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3612?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3612. ----------------------------------- Resolution: Done Nulled out the execution and checked for that in the more method. > NPE in connectorworkitem after close > ------------------------------------ > > Key: TEIID-3612 > URL: https://issues.jboss.org/browse/TEIID-3612 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12 > > > An NPE can occur if the connectorworkitem has pending asynch more work that is cancelled, but still runs. Then the logic to call close (which is added as a completion listener and effectively executed immediately as the work will report isDone=true) can occur before the pending call to next. > We should have an explicit check in more to prevent seeing the exception. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3612) NPE in connectorworkitem after close

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3612: ------------------------------------- Summary: NPE in connectorworkitem after close Key: TEIID-3612 URL: https://issues.jboss.org/browse/TEIID-3612 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 8.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.12 An NPE can occur if the connectorworkitem has pending asynch more work that is cancelled, but still runs. Then the logic to call close (which is added as a completion listener and effectively executed immediately as the work will report isDone=true) can occur before the pending call to next. We should have an explicit check in more to prevent seeing the exception. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3544) teiid-odata-*.war not deploying in EAP when using domain

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3544?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3544: ------------------------------------------------ Alex Szczuczko <aszczucz(a)redhat.com> changed the Status of [bug 1233001|https://bugzilla.redhat.com/show_bug.cgi?id=1233001] from MODIFIED to ON_QA > teiid-odata-*.war not deploying in EAP when using domain > -------------------------------------------------------- > > Key: TEIID-3544 > URL: https://issues.jboss.org/browse/TEIID-3544 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7.1.6_2 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 8.7.1.6_2 > > > The Teiid odata war, located: > modules/system/layers/dv/org/jboss/teiid/main/deployments/teiid-odata-8.7.1.6_2-redhat-2.war > was not being deployed. It's working in standalone. > The workaround in domain mode is to re-deploy the war using the admin console. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3611) Create a quickstart to demonstrate REST Service Through VDB

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3611?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3611: ------------------------------------ Can you check this quick start : https://github.com/teiid/teiid-quickstarts/tree/master/webservices-as-a-d... > Create a quickstart to demonstrate REST Service Through VDB > ----------------------------------------------------------- > > Key: TEIID-3611 > URL: https://issues.jboss.org/browse/TEIID-3611 > Project: Teiid > Issue Type: Feature Request > Components: Quick Starts > Affects Versions: 8.12 > Reporter: Kylin Soong > Assignee: Kylin Soong > Fix For: 8.12 > > > Create a quickstart to demonstrate REST Service Through VDB -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3611) Create a quickstart to demonstrate REST Service Through VDB

by Kylin Soong (JIRA)

Kylin Soong created TEIID-3611: ---------------------------------- Summary: Create a quickstart to demonstrate REST Service Through VDB Key: TEIID-3611 URL: https://issues.jboss.org/browse/TEIID-3611 Project: Teiid Issue Type: Feature Request Components: Quick Starts Affects Versions: 8.12 Reporter: Kylin Soong Assignee: Kylin Soong Fix For: 8.12 Create a quickstart to demonstrate REST Service Through VDB -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3600) DB2 - error getting substring if "from position" is out of range

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3600?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3600. ----------------------------------- Resolution: Done Updated the from expression to have a max equal to the string length. Also updated the community docs to describe the issues with substring. We may end up just needing to prevent pushdown as db2 also doesn't support negative indexing which is allowed for the from argument in Teiid. > DB2 - error getting substring if "from position" is out of range > ---------------------------------------------------------------- > > Key: TEIID-3600 > URL: https://issues.jboss.org/browse/TEIID-3600 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.12 > > > If second argument of a SUBSTRING(x,y,z) function is out of range of first argument an exception is thrown [1]. Source-specific command [2]. > [1] > Caused by: com.ibm.db2.jcc.am.SqlDataException: DB2 SQL Error: SQLCODE=-138, SQLSTATE=22011, SQLERRMC=null, DRIVER=4.12.55 > at com.ibm.db2.jcc.am.hd.a(hd.java:668) > at com.ibm.db2.jcc.am.hd.a(hd.java:60) > ... > [2] > SELECT substr(varchar(g_0.TimestampValue), 40, CASE WHEN 0 > (length(varchar(g_0.TimestampValue)) - (40 - 1)) THEN (length(varchar(g_0.TimestampValue)) - (40 - 1)) ELSE 0 END) FROM SmallA AS g_0 WHERE g_0.IntKey = 1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3600) DB2 - error getting substring if "from position" is out of range

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-3600?page=com.atlassian.jira.plugin... ] Juraj Duráni commented on TEIID-3600: ------------------------------------- I agree that address differences in substring function of variety vendors would be daunting. +1 for documentation. > I think the resolution here will be to account for the db2 exceptional case, What exactly do you mean? To fix the issue for db2 and make the behavior consistent with default Teiid's behavior or to add additional note to the Documentation? I recommend to fix the issue, because an exception by executing substring function is not very expected. > DB2 - error getting substring if "from position" is out of range > ---------------------------------------------------------------- > > Key: TEIID-3600 > URL: https://issues.jboss.org/browse/TEIID-3600 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.12 > > > If second argument of a SUBSTRING(x,y,z) function is out of range of first argument an exception is thrown [1]. Source-specific command [2]. > [1] > Caused by: com.ibm.db2.jcc.am.SqlDataException: DB2 SQL Error: SQLCODE=-138, SQLSTATE=22011, SQLERRMC=null, DRIVER=4.12.55 > at com.ibm.db2.jcc.am.hd.a(hd.java:668) > at com.ibm.db2.jcc.am.hd.a(hd.java:60) > ... > [2] > SELECT substr(varchar(g_0.TimestampValue), 40, CASE WHEN 0 > (length(varchar(g_0.TimestampValue)) - (40 - 1)) THEN (length(varchar(g_0.TimestampValue)) - (40 - 1)) ELSE 0 END) FROM SmallA AS g_0 WHERE g_0.IntKey = 1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3610) Add support for SPARQL

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3610?page=com.atlassian.jira.plugin... ] Van Halbert closed TEIID-3610. ------------------------------ Resolution: Deferred Waiting for more direction. > Add support for SPARQL > ----------------------- > > Key: TEIID-3610 > URL: https://issues.jboss.org/browse/TEIID-3610 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Van Halbert > Assignee: Steven Hawkins > > Add support for SPARQL -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 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 August 2015