October 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1248) Clob usability

by Steven Hawkins (JIRA)

Clob usability -------------- Key: TEIID-1248 URL: https://jira.jboss.org/browse/TEIID-1248 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 8.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 8.0 In many circumstances, clobs should be treated as charsequences to allow for use in string functions (concat returning clob, insert, left, etc.). There have also been customer requests to treat clobs as comparable, but that there are a lot of places including at design time where we validate against clobs being comparable that it may not be a good idea. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1700) Move odbc cursor logic to engine

by Steven Hawkins (JIRA)

Move odbc cursor logic to engine -------------------------------- Key: TEIID-1700 URL: https://issues.jboss.org/browse/TEIID-1700 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 8.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.0 ODBC added support for declared cursors, which would be a good general/procedure language feature. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
9
0 / 0

[JBoss JIRA] (TEIID-2265) Nullpointer exception when running an update statement for the second time

by Vineela Gampa (JIRA)

Vineela Gampa created TEIID-2265: ------------------------------------ Summary: Nullpointer exception when running an update statement for the second time Key: TEIID-2265 URL: https://issues.jboss.org/browse/TEIID-2265 Project: Teiid Issue Type: Bug Components: Common Affects Versions: 8.1 Reporter: Vineela Gampa Assignee: Steven Hawkins -- 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

12 years, 2 months

2
4
0 / 0

[JBoss JIRA] (TEIID-2085) Additional feature to TEIID-1726

by Debbie Steigner (JIRA)

12 years, 2 months

2
3
0 / 0

[JBoss JIRA] (TEIID-2263) makedep makenotdep hints should allow for more complicated scenarios

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2263: ------------------------------------- Summary: makedep makenotdep hints should allow for more complicated scenarios Key: TEIID-2263 URL: https://issues.jboss.org/browse/TEIID-2263 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins In the option clause makedep and makenotdep take what are typically fully-qualified names and mark all matching tables/views in the query. This is not generally a good idea. We should allow for something akin to oracle global table syntax (view.)*table to drill down more specifically. Ideally we'd also account for subqueries and set operations as well. -- 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

12 years, 2 months

1
1
0 / 0

[JBoss JIRA] (TEIID-2223) Compiled Groovy cannot deploy a dynamic VDB, using AdminShell methods, that is recognized as ACTIVE by the Groovy script

by Paul Nittel (JIRA)

Paul Nittel created TEIID-2223: ---------------------------------- Summary: Compiled Groovy cannot deploy a dynamic VDB, using AdminShell methods, that is recognized as ACTIVE by the Groovy script Key: TEIID-2223 URL: https://issues.jboss.org/browse/TEIID-2223 Project: Teiid Issue Type: Bug Components: AdminApi Affects Versions: 7.7.2 Reporter: Paul Nittel Assignee: Steven Hawkins This is a weird case. If I deploy a dynamic VDB from a compiled Groovy script, it is not seen as ACTIVE by the script. The server log shows it is active. If I use a non-compiled Groovy script, it all works fine. To add to the intrigue, if the compiled script periodically polls to see if the VDB is active, and I go to the Virtual Databases display in RHQ, the script magically sees the VDB as ACTIVE. I'm attaching the materials used in this test. -- 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

12 years, 2 months

4
11
0 / 0

[JBoss JIRA] (TEIID-2262) Add ability to move VDB to ACTIVE/UP state from Admin Console

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2262?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2262. ----------------------------------- Assignee: (was: Ken Johnson) Resolution: Out of Date The status of a vdb in 8.1 is loading/failed/active/removed. There is no inactive state. The terminal failed state is only entered on a metadata error, not if a jndi name is incorret. > Add ability to move VDB to ACTIVE/UP state from Admin Console > ------------------------------------------------------------- > > Key: TEIID-2262 > URL: https://issues.jboss.org/browse/TEIID-2262 > Project: Teiid > Issue Type: Feature Request > Components: Jopr Plugin > Reporter: Marc Shirley > > Currently, a VDB that is deployed to a server, but does not deploy successfully (for instance, because a datasource referenced by the VDB is not active) must be redeployed to the server to fix the inactive status. In the case of an incorrect JNDI name being used within the VDB, the JNDI name can be corrected through the Admin Console, but there is no way to redeploy or move the VDB to an active state from the Admin Console. This causes confusion due to being able to make changes to the configuration, but not being able to effect those changes on a currently INACTIVE/DOWN status VDB. > There was expectation to be able to administer the VDB from Admin Console due to the ability to alter the configuration properties in the UI. However, if the initial deployment fails and results in the VDB being marked as DOWN/INACTIVE, then they are unable to rectify this without fully redeploying the VDB. > Would like the ability to update the JNDI names and effect those changes on the currently deployed VDB to move it from an INACTIVE to an ACTIVE state. > This can be tested with the below steps: > 1) Configure a VDB with an incorrect JNDI name > 2) Deploy the VDB to an EDS server > 3) Log into the Admin Console > 4) Navigate to the VDB > 5) Confirm the VDB is listed in an INACTIVE state > 5) Modify the incorrect JNDI name to point to a valid datasource > 6) Confirm that the VDB has moved to an ACTIVE state -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2262) Add ability to move VDB to ACTIVE/UP state from Admin Console

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2262?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2262: ------------------------------------- I do not believe this is an issue with Teiid 8.2.x > Add ability to move VDB to ACTIVE/UP state from Admin Console > ------------------------------------------------------------- > > Key: TEIID-2262 > URL: https://issues.jboss.org/browse/TEIID-2262 > Project: Teiid > Issue Type: Feature Request > Components: Jopr Plugin > Reporter: Marc Shirley > Assignee: Ken Johnson > > Currently, a VDB that is deployed to a server, but does not deploy successfully (for instance, because a datasource referenced by the VDB is not active) must be redeployed to the server to fix the inactive status. In the case of an incorrect JNDI name being used within the VDB, the JNDI name can be corrected through the Admin Console, but there is no way to redeploy or move the VDB to an active state from the Admin Console. This causes confusion due to being able to make changes to the configuration, but not being able to effect those changes on a currently INACTIVE/DOWN status VDB. > There was expectation to be able to administer the VDB from Admin Console due to the ability to alter the configuration properties in the UI. However, if the initial deployment fails and results in the VDB being marked as DOWN/INACTIVE, then they are unable to rectify this without fully redeploying the VDB. > Would like the ability to update the JNDI names and effect those changes on the currently deployed VDB to move it from an INACTIVE to an ACTIVE state. > This can be tested with the below steps: > 1) Configure a VDB with an incorrect JNDI name > 2) Deploy the VDB to an EDS server > 3) Log into the Admin Console > 4) Navigate to the VDB > 5) Confirm the VDB is listed in an INACTIVE state > 5) Modify the incorrect JNDI name to point to a valid datasource > 6) Confirm that the VDB has moved to an ACTIVE state -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2262) Add ability to move VDB to ACTIVE/UP state from Admin Console

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2262?page=com.atlassian.jira.plugin... ] Van Halbert moved PRODMGT-257 to TEIID-2262: -------------------------------------------- Project: Teiid (was: Product Management) Key: TEIID-2262 (was: PRODMGT-257) Workflow: jira (was: JBoss Platforms RFE Workflow v2) Affects Version/s: (was: 5) Background and Context: (was: Customer segment and other factors don't contribute, but it seems a good thing for the product.) Component/s: Jopr Plugin (was: Enterprise SOA Platform (SOA-P)) > Add ability to move VDB to ACTIVE/UP state from Admin Console > ------------------------------------------------------------- > > Key: TEIID-2262 > URL: https://issues.jboss.org/browse/TEIID-2262 > Project: Teiid > Issue Type: Feature Request > Components: Jopr Plugin > Reporter: Marc Shirley > Assignee: Ken Johnson > > Currently, a VDB that is deployed to a server, but does not deploy successfully (for instance, because a datasource referenced by the VDB is not active) must be redeployed to the server to fix the inactive status. In the case of an incorrect JNDI name being used within the VDB, the JNDI name can be corrected through the Admin Console, but there is no way to redeploy or move the VDB to an active state from the Admin Console. This causes confusion due to being able to make changes to the configuration, but not being able to effect those changes on a currently INACTIVE/DOWN status VDB. > There was expectation to be able to administer the VDB from Admin Console due to the ability to alter the configuration properties in the UI. However, if the initial deployment fails and results in the VDB being marked as DOWN/INACTIVE, then they are unable to rectify this without fully redeploying the VDB. > Would like the ability to update the JNDI names and effect those changes on the currently deployed VDB to move it from an INACTIVE to an ACTIVE state. > This can be tested with the below steps: > 1) Configure a VDB with an incorrect JNDI name > 2) Deploy the VDB to an EDS server > 3) Log into the Admin Console > 4) Navigate to the VDB > 5) Confirm the VDB is listed in an INACTIVE state > 5) Modify the incorrect JNDI name to point to a valid datasource > 6) Confirm that the VDB has moved to an ACTIVE state -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1377) Teiid Designer (DTP) Execute All sends all queries at once to Server - Server should handle these bulk queries

by Paul Nittel (JIRA)

Teiid Designer (DTP) Execute All sends all queries at once to Server - Server should handle these bulk queries -------------------------------------------------------------------------------------------------------------- Key: TEIID-1377 URL: https://jira.jboss.org/browse/TEIID-1377 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.1.1 Reporter: Paul Nittel Assignee: Steven Hawkins When a series of SELECT statements are sent to the server via Execute All, the server should execute the SQL statements in appropriate fashion (as when the queries are directed to other RDBMSes, such as Oracle). At present, no exceptions are thrown, but the queries fail to execute. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

5
11
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2012