February 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2393) Insert columns should be displayed unqualified

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2393?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2393. ----------------------------------- Resolution: Done Updated the display logic for the engine. > Insert columns should be displayed unqualified > ---------------------------------------------- > > Key: TEIID-2393 > URL: https://issues.jboss.org/browse/TEIID-2393 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 7.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.3 > > > For backwards compatibility we allow the parser to parse qualified insert columns, but we've also allowed the string logic to display them as qualified, which is unnecessary. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2393) Insert columns should be displayed unqualified

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2393: ------------------------------------- Summary: Insert columns should be displayed unqualified Key: TEIID-2393 URL: https://issues.jboss.org/browse/TEIID-2393 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 8.3 For backwards compatibility we allow the parser to parse qualified insert columns, but we've also allowed the string logic to display them as qualified, which is unnecessary. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2392) Pushdown common table query invalid

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2392?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2392. ----------------------------------- Resolution: Done ensured that the with clause columns are passed down and that we're always using the unqualified name in the column declaration. > Pushdown common table query invalid > ----------------------------------- > > Key: TEIID-2392 > URL: https://issues.jboss.org/browse/TEIID-2392 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.3 > > > If a common table expression that can produce a query that contains different column names than either the assumed or explicit names in the with clause, then the pushed query can contain invalid column references. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2392) Pushdown common table query invalid

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2392: ------------------------------------- Summary: Pushdown common table query invalid Key: TEIID-2392 URL: https://issues.jboss.org/browse/TEIID-2392 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.3 If a common table expression that can produce a query that contains different column names than either the assumed or explicit names in the with clause, then the pushed query can contain invalid column references. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2322) ReusableExecution issue with large dependent joins

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2322?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2322. ----------------------------------- Fix Version/s: 8.3 Resolution: Done Switched our internal paradigm for tracking reusable executions from node id to something resembling a pool. node ids are generally not sufficient for tracking due to: - concurrent source queries from the same node (this issue) - and the ids are not unique across independent plans (such as using a cached virtual procedure plan within a relational plan) which means that we would could return the wrong executions. Command affinity is likely, but not enforced. Thus the pooling approach means that the ReusableExecution.reset method must be observed as the command may change between usages of the execution. > ReusableExecution issue with large dependent joins > -------------------------------------------------- > > Key: TEIID-2322 > URL: https://issues.jboss.org/browse/TEIID-2322 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.3 > > > Large dependent joins can be split among multiple queries that can be issued in parallel with the same node id (but different execution ids). The reusable execution is reusing based upon node id, so the logic either needs to create multiple executions for the parallel case or we need to be explicit about this possibility and have the translator developer check the execution id in the translator and respond appropriately. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2372) Providing functionality to set source table cardinality when metadata loaded

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2372?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2372: --------------------------------------- by object I mean object type - TABLE,VIEW,etc. So a full example could look like: ALTER FOREIGN TABLE foo ADD cardinality 100, ALTER COLUMN bar ADD updatable true, DROP something Since the COLUMN keyword is optional, we could just leave that out initially and also not expect a keyword for parameter. > Providing functionality to set source table cardinality when metadata loaded > ---------------------------------------------------------------------------- > > Key: TEIID-2372 > URL: https://issues.jboss.org/browse/TEIID-2372 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.2 > Reporter: Jack Ma > Assignee: Ramesh Reddy > Fix For: 8.3 > > > Want to have a easy way to set the source table cardinality when source model metadata loaded -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2372) Providing functionality to set source table cardinality when metadata loaded

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2372?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2372: ------------------------------------- ALTER object name action[, ...] we expect the "object name" to be unique across all the objects in the given schema? for ALTER [COLUMN] name ADD|SET|DROP option pair[, ...] How to find out parent object, if we use this for COLUMN or PARAMETER? Or you suggesting like ALTER table ALTER COLUMN column ADD cardinality 100, updatable true may be can you give couple examples? > Providing functionality to set source table cardinality when metadata loaded > ---------------------------------------------------------------------------- > > Key: TEIID-2372 > URL: https://issues.jboss.org/browse/TEIID-2372 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.2 > Reporter: Jack Ma > Assignee: Ramesh Reddy > Fix For: 8.3 > > > Want to have a easy way to set the source table cardinality when source model metadata loaded -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2372) Providing functionality to set source table cardinality when metadata loaded

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2372?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2372: --------------------------------------- Looking at the working sql 2011 draft, they generally use: ALTER object name action[, ...] where action can be: ADD|SET|DROP option pair or ALTER [COLUMN] name ADD|SET|DROP option pair[, ...] > Providing functionality to set source table cardinality when metadata loaded > ---------------------------------------------------------------------------- > > Key: TEIID-2372 > URL: https://issues.jboss.org/browse/TEIID-2372 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.2 > Reporter: Jack Ma > Assignee: Ramesh Reddy > Fix For: 8.3 > > > Want to have a easy way to set the source table cardinality when source model metadata loaded -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2372) Providing functionality to set source table cardinality when metadata loaded

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2372?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2372: -------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) Fix Version/s: 8.3 Complexity: High Component/s: Query Engine I checked SQL/MED syntax here http://wiki.postgresql.org/wiki/SQL/MED, they do not seem to provide any standard DDL for this. I propose we do ALTER [FOREIGN] TABLE|VIEW|PROCEDURE {name} [[COLUMN|PARAMETER] {sub-name}] ADD|DROP {prop-name} [TO {prop-value}] > Providing functionality to set source table cardinality when metadata loaded > ---------------------------------------------------------------------------- > > Key: TEIID-2372 > URL: https://issues.jboss.org/browse/TEIID-2372 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.2 > Reporter: Jack Ma > Assignee: Ramesh Reddy > Fix For: 8.3 > > > Want to have a easy way to set the source table cardinality when source model metadata loaded -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2372) Providing functionality to set source table cardinality when metadata loaded

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2372?page=com.atlassian.jira.plugin... ] Ramesh Reddy edited comment on TEIID-2372 at 2/12/13 9:59 PM: -------------------------------------------------------------- I checked SQL/MED syntax here http://wiki.postgresql.org/wiki/SQL/MED, they do not seem to provide any standard DDL for this. I propose we do {code} ALTER [FOREIGN] TABLE|VIEW|PROCEDURE {name} [[COLUMN|PARAMETER] {sub-name}] ADD|DROP {prop-name} [TO {prop-value}] {code} was (Author: rareddy): I checked SQL/MED syntax here http://wiki.postgresql.org/wiki/SQL/MED, they do not seem to provide any standard DDL for this. I propose we do ALTER [FOREIGN] TABLE|VIEW|PROCEDURE {name} [[COLUMN|PARAMETER] {sub-name}] ADD|DROP {prop-name} [TO {prop-value}] > Providing functionality to set source table cardinality when metadata loaded > ---------------------------------------------------------------------------- > > Key: TEIID-2372 > URL: https://issues.jboss.org/browse/TEIID-2372 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.2 > Reporter: Jack Ma > Assignee: Ramesh Reddy > Fix For: 8.3 > > > Want to have a easy way to set the source table cardinality when source model metadata loaded -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2013