July 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2021) Fail the VDB deployment when translator is not available

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2021: ----------------------------------- Summary: Fail the VDB deployment when translator is not available Key: TEIID-2021 URL: https://issues.jboss.org/browse/TEIID-2021 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.0 VDBDeployer checks for the override translator types, however it does not check for the base translators that are configured in the VDB. So, when a VDB with unknown translator is deployed, it gets deployed but never exposes any error information as to why the VDB is not "active". -- 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

11 years, 9 months

2
9
0 / 0

[JBoss JIRA] (TEIID-2032) Add ability to add OPTIONS on Key types in DDL

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2032: ----------------------------------- Summary: Add ability to add OPTIONS on Key types in DDL Key: TEIID-2032 URL: https://issues.jboss.org/browse/TEIID-2032 Project: Teiid Issue Type: Enhancement Components: Query Engine Affects Versions: 8.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.1 In the DDL based matadata the extended properties through OPTIONS keyword can be specified on the Tables, columns,procedures and functions. Extend this feature to include the Primary Keys and Foreign keys etc. -- 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

11 years, 9 months

2
2
0 / 0

[JBoss JIRA] (TEIID-2019) Remove all references to "javax.xml.bind" classes in the Teiid and support stream based xml

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2019: ----------------------------------- Summary: Remove all references to "javax.xml.bind" classes in the Teiid and support stream based xml Key: TEIID-2019 URL: https://issues.jboss.org/browse/TEIID-2019 Project: Teiid Issue Type: Task Components: Common Affects Versions: 8.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.0 -- 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

11 years, 9 months

2
2
0 / 0

[JBoss JIRA] (TEIID-1980) JDBC connection QueryTimeout property appears to be ignored

by Paul Nittel (JIRA)

Paul Nittel created TEIID-1980: ---------------------------------- Summary: JDBC connection QueryTimeout property appears to be ignored Key: TEIID-1980 URL: https://issues.jboss.org/browse/TEIID-1980 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.4 Reporter: Paul Nittel Assignee: Steven Hawkins While testing an EDS patch, I tried to constrain a query by adding ;QueryTimeout=1 to my JDBC connection string. This had no apparent effect. (The query--a repeated UNION ALL of huge tables, followed by a descending ORDER BY--takes over 30 seconds.) I also tried 3 and 10 second timeouts, but all allowed the query to continue to completion. -- 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

11 years, 9 months

4
11
0 / 0

[JBoss JIRA] (TEIID-2008) Allow client max object size to be settable

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2008: ------------------------------------- Summary: Allow client max object size to be settable Key: TEIID-2008 URL: https://issues.jboss.org/browse/TEIID-2008 Project: Teiid Issue Type: Quality Risk Components: JDBC Driver Affects Versions: 7.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.0 The default 32 MB for max object size may be too small in custom scenarios or when there are numerous warnings attached to results. This should be a settable property via the client settings properties. -- 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

11 years, 9 months

1
2
0 / 0

[JBoss JIRA] (TEIID-2024) DataTierManager.could_not_obtain_connector_binding error says it can't find Connection Factory

by Van Halbert (JIRA)

Van Halbert created TEIID-2024: ---------------------------------- Summary: DataTierManager.could_not_obtain_connector_binding error says it can't find Connection Factory Key: TEIID-2024 URL: https://issues.jboss.org/browse/TEIID-2024 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.7.1 Reporter: Van Halbert Assignee: Steven Hawkins Priority: Minor Got this error: [TeiidComponentException]Could not obtain connection factory for model EDG in VDB name= hotrod, version 1 at org.teiid.dqp.internal.process.DataTierManagerImpl.createRequest(DataTierManagerImpl.java:569) at org.teiid.dqp.internal.process.DataTierManagerImpl.registerRequest(DataTierManagerImpl.java:183 and looking at the code, it appears the source names defined for the model are null or empty. I think the message is alluding to the wrong thing it can't find. -- 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

11 years, 9 months

2
8
0 / 0

[JBoss JIRA] (TEIID-2075) Value of 'NEW' attribute is not set when an update procedure is executed

by heidi muehlebach (JIRA)

11 years, 9 months

2
3
0 / 0

[JBoss JIRA] (TEIID-2033) Use of OPTIONS during the DDL metadata import, overwrites default behavior on the record

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2033: ----------------------------------- Summary: Use of OPTIONS during the DDL metadata import, overwrites default behavior on the record Key: TEIID-2033 URL: https://issues.jboss.org/browse/TEIID-2033 Project: Teiid Issue Type: Bug Reporter: Ramesh Reddy Assignee: Ramesh Reddy When metadata is being loaded using the DDL, if the OPTIONS is used to define the metadata, this operation will overwrite any default settings for all the known properties that are defined on the metadata objects. This operation should only set the properties that are defined using this construct and leave the defaults that are defined the metadata record as is. -- 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

11 years, 9 months

2
3
0 / 0

[JBoss JIRA] (TEIID-2001) Skip loading of Function/Other models during the Index Based VDBs

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2001: ----------------------------------- Summary: Skip loading of Function/Other models during the Index Based VDBs Key: TEIID-2001 URL: https://issues.jboss.org/browse/TEIID-2001 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.0 Teiid only can read metadata from the PHYSICAL and VIRTUAL models, the OTHER (XSD) or FUNCTION models are there to represent the vdb structure but no metadata is actually loaded. FUNCTION model is still being loaded as original at the parse time. Lack of metadata is being flagged as an error during load, this needs to be fixed. -- 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

11 years, 9 months

2
2
0 / 0

[JBoss JIRA] (TEIID-1989) Interval counter

by Mark Addleman (JIRA)

Mark Addleman created TEIID-1989: ------------------------------------ Summary: Interval counter Key: TEIID-1989 URL: https://issues.jboss.org/browse/TEIID-1989 Project: Teiid Issue Type: Feature Request Reporter: Mark Addleman Assignee: Steven Hawkins In order to coordinate reusable executions across time windows, the CommandContext should include a counter of the number of intervals that have been executed. An interval is defined as all participating executions returning null. For more details, see https://community.jboss.org/thread/197562?start=0&tstart=0 -- 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

11 years, 9 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2012