January 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2241) Provide a CLI script to add Teiid into any configuration in AS7 standalone mode

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2241?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2241. --------------------------------- Resolution: Done Added "teiid-standalone-mode-install.cli" script to the kit in the "bin/scripts" directory. The installation document is updated about the availability of the script to add Teiid to any configuration of JBoss AS. > Provide a CLI script to add Teiid into any configuration in AS7 standalone mode > ------------------------------------------------------------------------------- > > Key: TEIID-2241 > URL: https://issues.jboss.org/browse/TEIID-2241 > Project: Teiid > Issue Type: Feature Request > Components: Build/Kits > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.3 > > > In order to install Teiid in a existing configuration, the standalone-teiid.xml script needs to be provided in CLI form, just like what it offers for the domain mode. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2205) Temp table and procedure block transactions issue

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2205?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2205: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=893128 > Temp table and procedure block transactions issue > ------------------------------------------------- > > Key: TEIID-2205 > URL: https://issues.jboss.org/browse/TEIID-2205 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.6 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 8.2 > > > The Request class is not correctly setting the transactioncontext on the commandcontext, so downstream transaction logic in temp tables and procedure blocks will not work properly. > Block/temp table work will fail to isolate correctly and not rollback. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2179) User defined aggregate function return type is ignored

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2179?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2179: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=893127 > User defined aggregate function return type is ignored > ------------------------------------------------------ > > Key: TEIID-2179 > URL: https://issues.jboss.org/browse/TEIID-2179 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.2 > > > The resolver is using the type of the first argument rather than the declared return type. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2160) data type for XMLTable for ordinality column is incorrect

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2160?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2160: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=893125 > data type for XMLTable for ordinality column is incorrect > --------------------------------------------------------- > > Key: TEIID-2160 > URL: https://issues.jboss.org/browse/TEIID-2160 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.1 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.2 > > > The XMLTable XMLColumn for ordinality constructor is hard-coding a type of STRING, rather than INTEGER. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2286) add native query support for spreadsheets

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2286?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2286. --------------------------------- Resolution: Done Native query support feature has been added; The documentation updated for google spreadsheet. > add native query support for spreadsheets > ----------------------------------------- > > Key: TEIID-2286 > URL: https://issues.jboss.org/browse/TEIID-2286 > Project: Teiid > Issue Type: Sub-task > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Minor > Fix For: 8.3 > > > google supports pivoting and other language features not supported by our sql, that should be accessible. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2338) common table expression performance

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2338?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2338: --------------------------------------- After some more thought the only case where this logic is generally applicable is with correlated subqueries against a common table. However the work for TEIID-2339 will largely handle that case as it will allow us to plan most subqueries as joins rather than repeated scans. Will likely just reassess as an xml specific enhancement based upon the existing auto-indexing logic. > common table expression performance > ----------------------------------- > > Key: TEIID-2338 > URL: https://issues.jboss.org/browse/TEIID-2338 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > Large common table expressions should be indexed based upon their usage in the query to improve performance. > Also given that we will now back-off of bad dependent joins, we should be more optimistic with using common tables as dependent joins (which would also reduce the need for an index). -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2345) source hints are not honoured for nested sqls

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2345?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2345: --------------------------------------- I'll add an example to make this clear, but the usage of keep aliases is using square braces to indicate the syntax as optional. So you'd use: {code}SELECT /*+ sh KEEP ALIASES:'foo' bar:'leading' */ ...{code} KEEP ALIASES simply directs the optimizer to allow the aliases used in the user query flow to source presumably because the hint is specific to some tables and the user needs a stable way to reference them (and doesn't want to use the auto generated aliases). Otherwise KEEP ALIASES does not change the functionality of how the source hint is propagated to the source executions. > If i use below general hint is available only to the first execution. What do you mean by first execution? There is only a single source access represented by that user query. > source hints are not honoured for nested sqls > --------------------------------------------- > > Key: TEIID-2345 > URL: https://issues.jboss.org/browse/TEIID-2345 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.1 > Reporter: Vineela Gampa > Assignee: Steven Hawkins > > Hi > I want to use general hints below. I observed i was able to put my sourcehint as below which yields generalhint information to data_window procedure. As per this document https://docs.jboss.org/author/display/TEIID/Query+Plans if i use KEEP_ALIASES general hint is available for all nested queries but i was not able to get it working > SELECT /*+ sh[KEEP ALIASES]:'foo' bar:'leading' */ \r\n" when i use something like this general hint is null in all the executions. > If i use below general hint is available only to the first execution. > "SELECT /*+ sh:'foo' bar:'leading' */ \r\n" > + " chorus_results.* \r\n" > + "FROM (\r\n" > + " EXEC data_window('select pkey, counter from testing.bigtable WHERE pkey=? LIMIT 300', ?)\r\n" > + ") AS chorus_data_window, ARRAYTABLE(chorus_data_window.tuple COLUMNS pkey long, counter long) AS chorus_results LIMIT 0, 20", -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2312) Allow resource adaptor to support "security-domain"

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2312?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2312. --------------------------------- Resolution: Done Adding ability to define security-domain for ldap, salesforce, ws(basic auth) and google-spreadsheet to consume the user name and credentials from the security context during the resource-adaptor's connection request. This enables user to pass-in logged in user's credentials to the above sources, where by each logged in user does not have to share a common connection. > Allow resource adaptor to support "security-domain" > --------------------------------------------------- > > Key: TEIID-2312 > URL: https://issues.jboss.org/browse/TEIID-2312 > Project: Teiid > Issue Type: Enhancement > Components: Server > Affects Versions: 8.1 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.3 > > > Currently > * LDAP > * Salesforce > * Google > connectors require user-id/password for making connections with underlying systems, but I do not think they support defining the "security-domain" so that the logged-in user's credentials can be passed through to sources. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2345) source hints are not honoured for nested sqls

by Vineela Gampa (JIRA)

[ https://issues.jboss.org/browse/TEIID-2345?page=com.atlassian.jira.plugin... ] Vineela Gampa updated TEIID-2345: --------------------------------- Issue Type: Bug (was: Feature Request) Description: Hi I want to use general hints below. I observed i was able to put my sourcehint as below which yields generalhint information to data_window procedure. As per this document https://docs.jboss.org/author/display/TEIID/Query+Plans if i use KEEP_ALIASES general hint is available for all nested queries but i was not able to get it working SELECT /*+ sh[KEEP ALIASES]:'foo' bar:'leading' */ \r\n" when i use something like this general hint is null in all the executions. If i use below general hint is available only to the first execution. "SELECT /*+ sh:'foo' bar:'leading' */ \r\n" + " chorus_results.* \r\n" + "FROM (\r\n" + " EXEC data_window('select pkey, counter from testing.bigtable WHERE pkey=? LIMIT 300', ?)\r\n" + ") AS chorus_data_window, ARRAYTABLE(chorus_data_window.tuple COLUMNS pkey long, counter long) AS chorus_results LIMIT 0, 20", was: Hi I want to use general hints below. I observed i was able to put my sourcehint as below which yields generalhint information to data_window procedure. "SELECT /*+ sh:'foo' bar:'leading' */ \r\n" + " chorus_results.* \r\n" + "FROM (\r\n" + " EXEC data_window('select pkey, counter from testing.bigtable WHERE pkey=? LIMIT 300', ?)\r\n" + ") AS chorus_data_window, ARRAYTABLE(chorus_data_window.tuple COLUMNS pkey long, counter long) AS chorus_results LIMIT 0, 20", > source hints are not honoured for nested sqls > --------------------------------------------- > > Key: TEIID-2345 > URL: https://issues.jboss.org/browse/TEIID-2345 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.1 > Reporter: Vineela Gampa > Assignee: Steven Hawkins > > Hi > I want to use general hints below. I observed i was able to put my sourcehint as below which yields generalhint information to data_window procedure. As per this document https://docs.jboss.org/author/display/TEIID/Query+Plans if i use KEEP_ALIASES general hint is available for all nested queries but i was not able to get it working > SELECT /*+ sh[KEEP ALIASES]:'foo' bar:'leading' */ \r\n" when i use something like this general hint is null in all the executions. > If i use below general hint is available only to the first execution. > "SELECT /*+ sh:'foo' bar:'leading' */ \r\n" > + " chorus_results.* \r\n" > + "FROM (\r\n" > + " EXEC data_window('select pkey, counter from testing.bigtable WHERE pkey=? LIMIT 300', ?)\r\n" > + ") AS chorus_data_window, ARRAYTABLE(chorus_data_window.tuple COLUMNS pkey long, counter long) AS chorus_results LIMIT 0, 20", -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2345) source hints are not honoured for nested sqls

by Vineela Gampa (JIRA)

Vineela Gampa created TEIID-2345: ------------------------------------ Summary: source hints are not honoured for nested sqls Key: TEIID-2345 URL: https://issues.jboss.org/browse/TEIID-2345 Project: Teiid Issue Type: Feature Request Affects Versions: 8.1 Reporter: Vineela Gampa Assignee: Steven Hawkins Hi I want to use general hints below. I observed i was able to put my sourcehint as below which yields generalhint information to data_window procedure. "SELECT /*+ sh:'foo' bar:'leading' */ \r\n" + " chorus_results.* \r\n" + "FROM (\r\n" + " EXEC data_window('select pkey, counter from testing.bigtable WHERE pkey=? LIMIT 300', ?)\r\n" + ") AS chorus_data_window, ARRAYTABLE(chorus_data_window.tuple COLUMNS pkey long, counter long) AS chorus_results LIMIT 0, 20", -- 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, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2013