February 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Updated: (TEIID-997) Investigate adding new metrics that added value for the user to monitor their servers

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-997?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-997: --------------------------------- Fix Version/s: 7.0 (was: 6.0.0) Affects Version/s: 7.0 > Investigate adding new metrics that added value for the user to monitor their servers > ------------------------------------------------------------------------------------- > > Key: TEIID-997 > URL: https://jira.jboss.org/jira/browse/TEIID-997 > Project: Teiid > Issue Type: Task > Components: Jopr Plugin > Affects Versions: 7.0 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 7.0 > > Attachments: Phase2Proposed.odt > > > Investigate which statics that should be added that provide better value to the user for monitoring their servers. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-997) Investigate adding new metrics that added value for the user to monitor their servers

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-997?page=com.atlassian.jira.plug... ] Van Halbert moved JBEDSP-770 to TEIID-997: ------------------------------------------ Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-997 (was: JBEDSP-770) Component/s: Jopr Plugin (was: JON Plugin) Fix Version/s: 6.0.0 (was: 6.0.0) > Investigate adding new metrics that added value for the user to monitor their servers > ------------------------------------------------------------------------------------- > > Key: TEIID-997 > URL: https://jira.jboss.org/jira/browse/TEIID-997 > Project: Teiid > Issue Type: Task > Components: Jopr Plugin > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 6.0.0 > > Attachments: Phase2Proposed.odt > > > Investigate which statics that should be added that provide better value to the user for monitoring their servers. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-994) Unable to execute Oracle pipelined table function as procedure

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-994?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-994: ------------------------------- Summary: Unable to execute Oracle pipelined table function as procedure (was: Unable to execute Oracle pipelined table function as procedure [Tripos POC]) > Unable to execute Oracle pipelined table function as procedure > -------------------------------------------------------------- > > Key: TEIID-994 > URL: https://jira.jboss.org/jira/browse/TEIID-994 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors, Query Engine > Reporter: Steven Hawkins > > Oracle pipelined table functions (can be used in Oracle queries as TABLE(...)) that can be put in the FROM clause and used as if they were tables although they are really procedures. We found that we imported this table function, although didn't get it quite right - the result set was wrong, which may just be a deficiency of the JDBC import metadata. We were able to map the proc to a table and execute but when we did we got a PL/SQL error from the db. > Because this is a proc, we are executing it as a CallableStatement down in the JDBC connector which apparently does not work with DataDirect. I'm not sure how we can detect and do something different but seems like we need to have some metadata (procedure name in source?) that can tell us that this proc needs to be run differently and have the Oracle JDBC Connector deal with this properly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-994) Unable to execute Oracle pipelined table function as procedure [Tripos POC]

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-994?page=com.atlassian.jira.plug... ] Van Halbert updated TEIID-994: ------------------------------ Description: Oracle pipelined table functions (can be used in Oracle queries as TABLE(...)) that can be put in the FROM clause and used as if they were tables although they are really procedures. We found that we imported this table function, although didn't get it quite right - the result set was wrong, which may just be a deficiency of the JDBC import metadata. We were able to map the proc to a table and execute but when we did we got a PL/SQL error from the db. Because this is a proc, we are executing it as a CallableStatement down in the JDBC connector which apparently does not work with DataDirect. I'm not sure how we can detect and do something different but seems like we need to have some metadata (procedure name in source?) that can tell us that this proc needs to be run differently and have the Oracle JDBC Connector deal with this properly. was: Defect Tracker #20072: At Tripos, they have some Oracle pipelined table functions (can be used in Oracle queries as TABLE(...)) that can be put in the FROM clause and used as if they were tables although they are really procedures. We found that we imported this table function, although didn't get it quite right - the result set was wrong, which may just be a deficiency of the JDBC import metadata. We were able to map the proc to a table and execute but when we did we got a PL/SQL error from the db. Because this is a proc, we are executing it as a CallableStatement down in the JDBC connector which apparently does not work with DataDirect. I'm not sure how we can detect and do something different but seems like we need to have some metadata (procedure name in source?) that can tell us that this proc needs to be run differently and have the Oracle JDBC Connector deal with this properly. > Unable to execute Oracle pipelined table function as procedure [Tripos POC] > --------------------------------------------------------------------------- > > Key: TEIID-994 > URL: https://jira.jboss.org/jira/browse/TEIID-994 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors, Query Engine > Reporter: Steven Hawkins > > Oracle pipelined table functions (can be used in Oracle queries as TABLE(...)) that can be put in the FROM clause and used as if they were tables although they are really procedures. We found that we imported this table function, although didn't get it quite right - the result set was wrong, which may just be a deficiency of the JDBC import metadata. We were able to map the proc to a table and execute but when we did we got a PL/SQL error from the db. > Because this is a proc, we are executing it as a CallableStatement down in the JDBC connector which apparently does not work with DataDirect. I'm not sure how we can detect and do something different but seems like we need to have some metadata (procedure name in source?) that can tell us that this proc needs to be run differently and have the Oracle JDBC Connector deal with this properly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-994) Unable to execute Oracle pipelined table function as procedure [Tripos POC]

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-994?page=com.atlassian.jira.plug... ] Van Halbert moved JBEDSP-894 to TEIID-994: ------------------------------------------ Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-994 (was: JBEDSP-894) Component/s: Misc. Connectors Query Engine (was: Connectors) (was: Query) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5.1) > Unable to execute Oracle pipelined table function as procedure [Tripos POC] > --------------------------------------------------------------------------- > > Key: TEIID-994 > URL: https://jira.jboss.org/jira/browse/TEIID-994 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors, Query Engine > Reporter: Steven Hawkins > > Defect Tracker #20072: At Tripos, they have some Oracle pipelined table functions (can be used in Oracle queries as TABLE(...)) that can be put in the FROM clause and used as if they were tables although they are really procedures. We found that we imported this table function, although didn't get it quite right - the result set was wrong, which may just be a deficiency of the JDBC import metadata. We were able to map the proc to a table and execute but when we did we got a PL/SQL error from the db. > Because this is a proc, we are executing it as a CallableStatement down in the JDBC connector which apparently does not work with DataDirect. I'm not sure how we can detect and do something different but seems like we need to have some metadata (procedure name in source?) that can tell us that this proc needs to be run differently and have the Oracle JDBC Connector deal with this properly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-993) Enhance XML processing to execute relational queries in parallel when possible

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-993?page=com.atlassian.jira.plug... ] Van Halbert moved JBEDSP-1180 to TEIID-993: ------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-993 (was: JBEDSP-1180) Component/s: Query Engine (was: Query) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5) > Enhance XML processing to execute relational queries in parallel when possible > ------------------------------------------------------------------------------ > > Key: TEIID-993 > URL: https://jira.jboss.org/jira/browse/TEIID-993 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Steven Hawkins > > Per feedback from Barry, was reviewing XML processing and because we execute all queries serially in our XML processing. However, conceptually, we could often execute multiple mapping class and/or temp table queries in parallel. When time permits it might be benefitial to investigate this. > All mapping classes at depth "n" in the document model are independent of each other, so they can be executed in parallel. Each mapping class may have input sets to any ancestor mapping class up to depth "n-1", or may select from any temp table up to depth "n" (the same depth). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-992) Improve update of source costing statistics

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-992?page=com.atlassian.jira.plug... ] Van Halbert moved JBEDSP-1178 to TEIID-992: ------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-992 (was: JBEDSP-1178) Component/s: Misc. Connectors Query Engine (was: Designer) Fix Version/s: (was: Future Versions) > Improve update of source costing statistics > ------------------------------------------- > > Key: TEIID-992 > URL: https://jira.jboss.org/jira/browse/TEIID-992 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors, Query Engine > Reporter: Marc Shirley > > It is very important that we support the ability to update source statistics at runtime. This is important due to the changing nature of read/write sources and differences between a development data source and a production data source. > The following options should be possible: > 1) Update model/source statistics on VDB deployment. > 2) Update model/source statistics on connector startup. > 3) Update model/source statistics on at a scheduled time. > 4) Update model/source statistics upon a manual request. > case 5920 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-991) Request for support of Sybase IQ as a supported data source

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-991?page=com.atlassian.jira.plug... ] Van Halbert moved JBEDSP-1138 to TEIID-991: ------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-991 (was: JBEDSP-1138) Component/s: Misc. Connectors (was: Connectors) Affects Version/s: (was: Future Versions) > Request for support of Sybase IQ as a supported data source > ----------------------------------------------------------- > > Key: TEIID-991 > URL: https://jira.jboss.org/jira/browse/TEIID-991 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Marc Shirley > > Per client: > We'd like the ability to have a built-in connector type for Sybase IQ, > just the same as Sybase ASE We have been getting inquiries and we've > had to decline one project because we didn't support Sybase IQ out of > the box. We foresee that Sybase IQ will be getting some play within > important Data Warehouses and Data Marts within the firm. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-981) Ability to cache XML documents

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-981?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-981. ---------------------------------- Resolution: Done Added the ability to cache xml document model results and xquery results as part of the result set caching refactoring. > Ability to cache XML documents > ------------------------------ > > Key: TEIID-981 > URL: https://jira.jboss.org/jira/browse/TEIID-981 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Lance Phillips > Assignee: Steven Hawkins > Fix For: 7.0 > > > We can currently cache relational result sets but have to re-create the XML document. XML being verbose this re-creation could take some time. This requirement would probably need a materialized flag on the document model, and the ability to store the XML document in an RDBMS (As a blob?) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-981) Ability to cache XML documents

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-981?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-981: --------------------------------- Fix Version/s: 7.0 Affects Version/s: 6.0.0 Assignee: Steven Hawkins > Ability to cache XML documents > ------------------------------ > > Key: TEIID-981 > URL: https://jira.jboss.org/jira/browse/TEIID-981 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Lance Phillips > Assignee: Steven Hawkins > Fix For: 7.0 > > > We can currently cache relational result sets but have to re-create the XML document. XML being verbose this re-creation could take some time. This requirement would probably need a materialized flag on the document model, and the ability to store the XML document in an RDBMS (As a blob?) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 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 2010