March 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-1911) Deploy time cached VDB metadata is being deleted during shutdown.

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-1911: ----------------------------------- Summary: Deploy time cached VDB metadata is being deleted during shutdown. Key: TEIID-1911 URL: https://issues.jboss.org/browse/TEIID-1911 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Priority: Critical Fix For: 8.0 Due to https://issues.jboss.org/browse/AS7-3431 the metadata is always being deleted during the shutdown. This will be bigger issue with dynamic VDBs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
6
0 / 0

[JBoss JIRA] (TEIID-1964) Queries which exceed the query timeout value are reported as canceled with no reference to the reason (timed out)

by Paul Nittel (JIRA)

Paul Nittel created TEIID-1964: ---------------------------------- Summary: Queries which exceed the query timeout value are reported as canceled with no reference to the reason (timed out) Key: TEIID-1964 URL: https://issues.jboss.org/browse/TEIID-1964 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.7 Reporter: Paul Nittel Assignee: Steven Hawkins Attachments: TimedOut.log While testing the query timeout value setting for VDBs in the Designer, I found there was no way for a user to easily understand why requests were being canceled due to a timeout. The log shows nothing other than it was canceled. The phrase timeout did not appear in the log. We really should report the cause of the cancellation. I'll attach the log excerpt. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
3
0 / 0

[JBoss JIRA] (TEIID-1935) TransformationMetadata.getXMLSchemas relative paths fail on windows

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-1935: ------------------------------------- Summary: TransformationMetadata.getXMLSchemas relative paths fail on windows Key: TEIID-1935 URL: https://issues.jboss.org/browse/TEIID-1935 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.6 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.7 The use of File logic makes getting the parent path dependent on the platform. The logic is only currently correct for filesystems that use the / separator. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
2
0 / 0

[JBoss JIRA] (TEIID-1972) Non-stagable cardinality dependent aggregate should prevent the creation of a staged grouping

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-1972: ------------------------------------- Summary: Non-stagable cardinality dependent aggregate should prevent the creation of a staged grouping Key: TEIID-1972 URL: https://issues.jboss.org/browse/TEIID-1972 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.4 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.7.1 The use of a stagable and non-stagable cardinality dependent aggregate (e.g. count(x) and array_agg) over a join will still result in a staged grouping being created that can change the results. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
2
0 / 0

[JBoss JIRA] (TEIID-1969) Missing message for key JDBCQueryExecution.Error_executing_query__1

by Mark Drilling (JIRA)

Mark Drilling created TEIID-1969: ------------------------------------ Summary: Missing message for key JDBCQueryExecution.Error_executing_query__1 Key: TEIID-1969 URL: https://issues.jboss.org/browse/TEIID-1969 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.0 Reporter: Mark Drilling Assignee: Steven Hawkins Priority: Minor Ran into the following missing message when testing Teiid 8.0 Beta1 Code:1146 Message:TEIID11008:<Missing message for key "JDBCQueryExecution.Error_executing_query__1" in: org.teiid.translator.jdbc.i18n> 1 [MySQLSyntaxErrorException]Table 'test12Mar.ACCOUNT' doesn't exist at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:90) at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:235) at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:355) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:144) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:141) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1751) Scalar function reference issues

by Steven Hawkins (JIRA)

Scalar function reference issues -------------------------------- Key: TEIID-1751 URL: https://issues.jboss.org/browse/TEIID-1751 Project: Teiid Issue Type: Bug Components: Documentation Affects Versions: 7.4.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.4.1, 7.6 Generic issue for on-going corrections/improvements to scalar function docs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
3
0 / 0

[JBoss JIRA] (TEIID-1976) Metadata TYPE_NAME value is null for String Columns

by Mark Drilling (JIRA)

Mark Drilling created TEIID-1976: ------------------------------------ Summary: Metadata TYPE_NAME value is null for String Columns Key: TEIID-1976 URL: https://issues.jboss.org/browse/TEIID-1976 Project: Teiid Issue Type: Bug Components: Common Affects Versions: 8.0 Reporter: Mark Drilling Assignee: Ramesh Reddy The metadata TYPE_NAME value for string datatypes is apparently returning null. I am running against a JBoss AS7.1Final server with Teiid 8.0Beta2. My application (openshift web client) establishes connection from a DataSource, eg connection = dataSource.getConnection(), then resultSet = connection.getMetaData().getColumns(); when iterating thru the resultSet, the value for columnName="TYPE_NAME" is null for string types. Other types seem to return a correct value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

3
13
0 / 0

[JBoss JIRA] (TEIID-1978) SalesForce getDeleted function does not return deleted objects list

by Paul Nittel (JIRA)

Paul Nittel created TEIID-1978: ---------------------------------- Summary: SalesForce getDeleted function does not return deleted objects list Key: TEIID-1978 URL: https://issues.jboss.org/browse/TEIID-1978 Project: Teiid Issue Type: Bug Components: Salesforce Connector Reporter: Paul Nittel Assignee: Steven Hawkins While testing the SalesForce connector, I noticed the getDeleted function was not returning any results, when there should be. See Steps to Reproduce. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
5
0 / 0

[JBoss JIRA] (TEIID-1944) After changing model to replace primary key with a unique key, the deployment of the vdb errors saying PrimaryKey does not exist

by Van Halbert (JIRA)

Van Halbert created TEIID-1944: ---------------------------------- Summary: After changing model to replace primary key with a unique key, the deployment of the vdb errors saying PrimaryKey does not exist Key: TEIID-1944 URL: https://issues.jboss.org/browse/TEIID-1944 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 7.4.1 Reporter: Van Halbert Assignee: Steven Hawkins Attachments: dummy-ds.xml, server.log, Trade.vdb In designer, I removed a primary key and replaced it with a unique key, and changed the foreign key to now reference the unique key, and all built with no errors. When deploying vdb to server, you see this exception (partial, see attachment for full log): Caused by: mmuuid:15f67b60-e387-4092-bbc5-0b7726585f52 PrimaryKey does not exist. at org.teiid.metadata.index.IndexMetadataFactory.getPrimaryKey(IndexMetadataFactory.java:353) at org.teiid.metadata.index.IndexMetadataFactory.getTables(IndexMetadataFactory.java:295) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
6
0 / 0

[JBoss JIRA] (TEIID-1959) Add a way to exclude tables/procedures from JDBC import

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-1959: ------------------------------------- Summary: Add a way to exclude tables/procedures from JDBC import Key: TEIID-1959 URL: https://issues.jboss.org/browse/TEIID-1959 Project: Teiid Issue Type: Enhancement Components: JDBC Connector Affects Versions: 7.7 Reporter: Steven Hawkins Assignee: Steven Hawkins The JDBC importer provides a simplistic pass-through for table/procedure inclusion, but that can make it cumbersome to exclude a small subset of tables/procedures. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2012