September 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4444) Add a built-in delegating translator that allows overriding all supports

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4444?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4444: --------------------------------------- We'll need some documentation on this as well. And it may be good for Designer to touch on using this translator on top of a regular translator to twizzle capabilities. > Add a built-in delegating translator that allows overriding all supports > ------------------------------------------------------------------------ > > Key: TEIID-4444 > URL: https://issues.jboss.org/browse/TEIID-4444 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Labels: CR1 > Fix For: 9.1 > > > To assist in toggling specific capabilities without a patch, we should provide a built-in delegating translator that can selective toggle capabilities. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4468) Google translator evaluates 0 as not NULL for operator <>

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4468?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4468. ----------------------------------- Resolution: Done Updated the logic to add is not null checks anytime there is a predicate that could potentially match null. > Google translator evaluates 0 as not NULL for operator <> > ---------------------------------------------------------- > > Key: TEIID-4468 > URL: https://issues.jboss.org/browse/TEIID-4468 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12 > Reporter: Lucie Fabrikova > Assignee: Steven Hawkins > Fix For: 9.1, 9.0.5 > > > Query ""SELECT stringNum FROM bqt1.SmallA <> 0" returns also values NULL (empty cell in spreadsheet). > I.e., NULL is treated as different from 0. > If this is expected behavior, shouldn't it be in the documentation? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4468) Google translator evaluates 0 as not NULL for operator <>

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4468?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4468: ---------------------------------- Component/s: Misc. Connectors Fix Version/s: 9.1 9.0.5 Priority: Major (was: Minor) > Google translator evaluates 0 as not NULL for operator <> > ---------------------------------------------------------- > > Key: TEIID-4468 > URL: https://issues.jboss.org/browse/TEIID-4468 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12 > Reporter: Lucie Fabrikova > Assignee: Steven Hawkins > Fix For: 9.1, 9.0.5 > > > Query ""SELECT stringNum FROM bqt1.SmallA <> 0" returns also values NULL (empty cell in spreadsheet). > I.e., NULL is treated as different from 0. > If this is expected behavior, shouldn't it be in the documentation? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4471) Assertion error with temp table delete

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4471?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4471. ----------------------------------- Resolution: Done Added more assertions and generally used a copy to track the current values. > Assertion error with temp table delete > -------------------------------------- > > Key: TEIID-4471 > URL: https://issues.jboss.org/browse/TEIID-4471 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 9.1, 8.13.7, 9.0.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 8.13.7, 9.0.5 > > > Related to TEIID-4405 there are circumstances where a temp table deletion results in an assertion error of "delete failed". A possible scenario (that is dependent upon a number of factors, including batch sizes and garbage collection) requires the values stored by the tuple browser to get out of sync with what is stored by the page such that a delete is attempted twice. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4471) Assertion error with temp table delete

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4471: ------------------------------------- Summary: Assertion error with temp table delete Key: TEIID-4471 URL: https://issues.jboss.org/browse/TEIID-4471 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 9.0.4, 9.1, 8.13.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.1, 8.13.7, 9.0.5 Related to TEIID-4405 there are circumstances where a temp table deletion results in an assertion error of "delete failed". A possible scenario (that is dependent upon a number of factors, including batch sizes and garbage collection) requires the values stored by the tuple browser to get out of sync with what is stored by the page such that a delete is attempted twice. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4470) Google spreadsheet translator execution should not require metadata

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4470: ------------------------------------- Summary: Google spreadsheet translator execution should not require metadata Key: TEIID-4470 URL: https://issues.jboss.org/browse/TEIID-4470 Project: Teiid Issue Type: Quality Risk Components: Misc. Connectors Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: Open To Community The google translator uses the connection metadata at execution time rather than just relying on name in source and other metadata. An option should be added to just use the Teiid metadata. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4470) Google spreadsheet translator execution should not require metadata

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4470?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-4470: ------------------------------------- Assignee: (was: Steven Hawkins) > Google spreadsheet translator execution should not require metadata > ------------------------------------------------------------------- > > Key: TEIID-4470 > URL: https://issues.jboss.org/browse/TEIID-4470 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Reporter: Steven Hawkins > Priority: Minor > Fix For: Open To Community > > > The google translator uses the connection metadata at execution time rather than just relying on name in source and other metadata. An option should be added to just use the Teiid metadata. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4469) Insert with query expression does not apply source hint to target

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4469?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4469: ---------------------------------- Summary: Insert with query expression does not apply source hint to target (was: ProjectIntoNode does not pass source hints to the target source) > Insert with query expression does not apply source hint to target > ----------------------------------------------------------------- > > Key: TEIID-4469 > URL: https://issues.jboss.org/browse/TEIID-4469 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.1.6_2 > Reporter: Marc Shirley > Assignee: Steven Hawkins > > "INSERT INTO ... SELECT ..." statements result in a ProjectIntoNode which seems to prevent any source hints from being passed down to the relevant source. These work correctly with an "INSERT INTO ... VALUES ..." statement. I've included example user and final query plan data below for the non-working [1] and working [2] insert statements. > [1] source hint not applied to ProjectIntoNode: > USER COMMAND: > INSERT /*+sh test:'append' */ INTO test.TEST (ID, "VALUE") SELECT X.id AS ID, X."value" AS "VALUE" FROM (SELECT bqt.SMALLA.INTKEY AS id, bqt.SMALLA.INTNUM AS "value" FROM bqt.SMALLA WHERE bqt.SMALLA.INTKEY = 0) AS X > ... > OPTIMIZATION COMPLETE: > PROCESSOR PLAN: > ProjectIntoNode(0) output=[Count] test.TEST > AccessNode(1) output=[bqt.SMALLA.INTKEY AS ID, bqt.SMALLA.INTNUM AS "VALUE"] SELECT /*+sh test:'append' */ g_0.INTKEY, g_0.INTNUM FROM bqt.SMALLA AS g_0 WHERE g_0.INTKEY = 0 > [2] source hint applied to AccessNode: > USER COMMAND: > INSERT /*+sh test:'append' */ INTO test.TEST (ID, "VALUE") VALUES ('-1', '-1') > ... > OPTIMIZATION COMPLETE: > PROCESSOR PLAN: > AccessNode(0) output=[Count] INSERT /*+sh test:'append' */ INTO test.TEST (ID, "VALUE") VALUES ('-1', '-1') -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4469) ProjectIntoNode does not pass source hints to the target source

by Marc Shirley (JIRA)

Marc Shirley created TEIID-4469: ----------------------------------- Summary: ProjectIntoNode does not pass source hints to the target source Key: TEIID-4469 URL: https://issues.jboss.org/browse/TEIID-4469 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.7.1.6_2 Reporter: Marc Shirley Assignee: Steven Hawkins "INSERT INTO ... SELECT ..." statements result in a ProjectIntoNode which seems to prevent any source hints from being passed down to the relevant source. These work correctly with an "INSERT INTO ... VALUES ..." statement. I've included example user and final query plan data below for the non-working [1] and working [2] insert statements. [1] source hint not applied to ProjectIntoNode: USER COMMAND: INSERT /*+sh test:'append' */ INTO test.TEST (ID, "VALUE") SELECT X.id AS ID, X."value" AS "VALUE" FROM (SELECT bqt.SMALLA.INTKEY AS id, bqt.SMALLA.INTNUM AS "value" FROM bqt.SMALLA WHERE bqt.SMALLA.INTKEY = 0) AS X ... OPTIMIZATION COMPLETE: PROCESSOR PLAN: ProjectIntoNode(0) output=[Count] test.TEST AccessNode(1) output=[bqt.SMALLA.INTKEY AS ID, bqt.SMALLA.INTNUM AS "VALUE"] SELECT /*+sh test:'append' */ g_0.INTKEY, g_0.INTNUM FROM bqt.SMALLA AS g_0 WHERE g_0.INTKEY = 0 [2] source hint applied to AccessNode: USER COMMAND: INSERT /*+sh test:'append' */ INTO test.TEST (ID, "VALUE") VALUES ('-1', '-1') ... OPTIMIZATION COMPLETE: PROCESSOR PLAN: AccessNode(0) output=[Count] INSERT /*+sh test:'append' */ INTO test.TEST (ID, "VALUE") VALUES ('-1', '-1') -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3329) Rationalize older spatial support with the new

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3329?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3329: --------------------------------------- Also we'd have to leave the old method signatures there for compatibility. > Rationalize older spatial support with the new > ---------------------------------------------- > > Key: TEIID-3329 > URL: https://issues.jboss.org/browse/TEIID-3329 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Reporter: Steven Hawkins > Fix For: 9.1 > > > MongoDB and Oracle had existing spatial support that should be updated to account for the new support if possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2016