April 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-538) Using adminapi, importing VDB subsequent times causes a an exception that says the VDB already exist in the extensions

by Van Halbert (JIRA)

Using adminapi, importing VDB subsequent times causes a an exception that says the VDB already exist in the extensions ---------------------------------------------------------------------------------------------------------------------- Key: TEIID-538 URL: https://jira.jboss.org/jira/browse/TEIID-538 Project: Teiid Issue Type: Bug Components: AdminApi, Server Affects Versions: 6.1.1 Reporter: Van Halbert Assignee: Van Halbert A VDB cannot be imported more than once because subsequent imports causes an exception that says the VDB already exist in the extensions. There are 2 problems here: 1. The actual exception, SQL Exception - invalid sql, wasn't seen 2. The sql being used was missing a ending quote. -- 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

15 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-479) Teiid embedded non-delegating classloader issues

by Steven Hawkins (JIRA)

Teiid embedded non-delegating classloader issues ------------------------------------------------ Key: TEIID-479 URL: https://jira.jboss.org/jira/browse/TEIID-479 Project: Teiid Issue Type: Bug Components: Embedded Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Ramesh Reddy Priority: Critical Fix For: 6.0.0 The non-delegating classloader for lib and patches entries will create problems if any of the jars duplicate classes from a higher level classloader - without overriding all of the referenced classes. See TEIIDDES-141 for a similar situation in a designer install. -- 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

15 years, 7 months

2
6
0 / 0

[JBoss JIRA] Created: (TEIID-482) Web Services Tab not Displaying in Console

by Ted Jones (JIRA)

Web Services Tab not Displaying in Console ------------------------------------------ Key: TEIID-482 URL: https://jira.jboss.org/jira/browse/TEIID-482 Project: Teiid Issue Type: Bug Components: Console Affects Versions: 6.0.0 Reporter: Ted Jones Assignee: Steven Hawkins Fix For: 6.1.0 The tab used for publishing the WSDL URL for a Web Services VDB to a UDDI Registry is not displaying in the Console. -- 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

15 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-528) java.lang.NumberFormatException thrown by LogConfigurationProvider due to missing properties in Configuration

by Van Halbert (JIRA)

java.lang.NumberFormatException thrown by LogConfigurationProvider due to missing properties in Configuration ------------------------------------------------------------------------------------------------------------- Key: TEIID-528 URL: https://jira.jboss.org/jira/browse/TEIID-528 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 6.1.0 Reporter: Van Halbert Assignee: Van Halbert The NumberFormatException is being thrown because the metamatrix.log property does not exist in the Configuration object. This is a newly exposed issue due to the system properties in the config.xml were removed and were relying on the Configuration component type to provide the defaults. -- 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

15 years, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIID-522) JDBC DatabaseMetadata methods do not accept empty string as catalog name

by Greg Haber (JIRA)

JDBC DatabaseMetadata methods do not accept empty string as catalog name ------------------------------------------------------------------------- Key: TEIID-522 URL: https://jira.jboss.org/jira/browse/TEIID-522 Project: Teiid Issue Type: Bug Components: JDBC Driver Environment: http://anonsvn.jboss.org/repos/teiid/trunk/client-jdbc/src/main/java/com/... rev 809 Reporter: Greg Haber Assignee: Steven Hawkins This is related to internal support ticket I-T #212065 (which was against MetaMatrix 5.5SP2). To resolve that ticket (where a third party software package expected different behavior from the MetaMatrix JDBC driver than it actually had), we made three changes: 1) DatabaseMetaData.supportsSchemaInDataManipulation() was changed to return true (which is correct) - looks like this change was also brought over to Teiid 2) DatabaseMetaData.supportsCatalogInDataManipulation() was changed to return the value of the boolean driver property "supportsCatalog". This change didn't come over to Teiid (in Teiid this method always returns "false"). I'm fine with the current Teiid behavior, since we don't have a notion of catalog, so really "false" is the correct response here. 3) The DatabaseMetaData methods getColumns, getExportedKeys, getImportedKeys, getIndexInfo, getPrimaryKeys, getProcedureColumns, getProcedures, and getTables all have a parameter for catalog name. In the current Teiid implementation of MMDatabaseMetaData, if catalog is non-null an empty response is returned. This is actually incorrect behavior according to both 1.5 and 1.6 javadoc - see http://java.sun.com/javase/6/docs/api/java/sql/DatabaseMetaData.html#getT... where it says: catalog - a catalog name; must match the catalog name as it is stored in the database; "" retrieves those without a catalog; null means that the catalog name should not be used to narrow the search So, since Teiid does not have the notion of a catalog, it should accept either null or the empty string as valid values for the catalog parameter. In the MMx 5.5.x code base, all of these methods were changed to only return empty responses if catalog was non-null, and also was not the empty string: if ((catalog != null) && (catalog.length() > 0)) { This same change should be made to Teiid. -- 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

15 years, 7 months

3
7
0 / 0

[JBoss JIRA] Created: (TEIID-491) Cancelation of atomic requests should be based upon atomic requestid

by Steven Hawkins (JIRA)

Cancelation of atomic requests should be based upon atomic requestid -------------------------------------------------------------------- Key: TEIID-491 URL: https://jira.jboss.org/jira/browse/TEIID-491 Project: Teiid Issue Type: Quality Risk Components: AdminApi Affects Versions: 6.1.0 Reporter: Steven Hawkins Priority: Minor Fix For: 6.0.0 Atomic requests are currently canceled by node id, which is not unique. -- 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

15 years, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (TEIID-529) Simplify ConnectorCapabilities

by Steven Hawkins (JIRA)

Simplify ConnectorCapabilities ------------------------------ Key: TEIID-529 URL: https://jira.jboss.org/jira/browse/TEIID-529 Project: Teiid Issue Type: Quality Risk Components: Connector API Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.0 In making the other connector changes I would like to open a dialog on refining the connector capabilities mechanism. At a minimum I would like to just use basicconnectorcapabilities rather than having the connectorcapabilities interface, which noonne is told to implement directly anyway. A more aggressive approach would be to use the same approach as dqp, a map with an enum key. -- 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

15 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-525) Eliminate redundencies in capabilities override and existing binding properties.

by Steven Hawkins (JIRA)

Eliminate redundencies in capabilities override and existing binding properties. -------------------------------------------------------------------------------- Key: TEIID-525 URL: https://jira.jboss.org/jira/browse/TEIID-525 Project: Teiid Issue Type: Quality Risk Components: Connector API Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.0 The max in size can now be specified by both an override and an existing setting for some connector types (such as JDBC). We should probably just rely on the override in cases like this. -- 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

15 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (TEIID-470) New AdminAPI method needed to support deploying a Connector Binding to a VM

by Van Halbert (JIRA)

New AdminAPI method needed to support deploying a Connector Binding to a VM --------------------------------------------------------------------------- Key: TEIID-470 URL: https://jira.jboss.org/jira/browse/TEIID-470 Project: Teiid Issue Type: Feature Request Components: AdminApi Affects Versions: 6.1.0 Reporter: Van Halbert Assignee: Van Halbert Add a method that enables the deployment of one or more connector bindings to one or more vms. And the opposite, remove from deployment, will be needed. This is currently needed to support command line importvdb option that allows the deployment of the bindings associated with the imported vdb. Also, this will be needed in the future by the newly developed configuration tool. -- 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

15 years, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIID-493) Define a new modeling construct that can create a defaulted parameter.

by John Doyle (JIRA)

Define a new modeling construct that can create a defaulted parameter. ---------------------------------------------------------------------- Key: TEIID-493 URL: https://jira.jboss.org/jira/browse/TEIID-493 Project: Teiid Issue Type: Feature Request Components: Query Engine Reporter: John Doyle Assignee: Steven Hawkins Priority: Minor I would like to be able to define on a physical model a defaulted parameter value for a column, much like an access pattern with a default value. At runtime the default value would be sent as a parameter if the user did not supply a value in the query. The use case that brought this to mind is the Salesforce connector. Each Salesforce object exposes a isDeleted column and since most uses of the connector do not want to see deleted objects, the user will have to know that they need to have isDeleted=false in the query. Having a 'defaulted access pattern' would allow us to encapsulate this SF API leakage better. -- 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

15 years, 8 months

2
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2009