June 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1071) Modify validation errors element in schema for VDB configuration file to include attribute for location of error

by John Verhaeg (JIRA)

Modify validation errors element in schema for VDB configuration file to include attribute for location of error ---------------------------------------------------------------------------------------------------------------- Key: TEIID-1071 URL: https://jira.jboss.org/jira/browse/TEIID-1071 Project: Teiid Issue Type: Feature Request Affects Versions: 6.2.0 Reporter: John Verhaeg Assignee: Steven Hawkins Fix For: 7.0 The Designer needs this information to allow the user to navigate to the offending object within a model. So, we either need a specific attribute for location, or a generic properties element like within the model and entry elements -- 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, 8 months

3
4
0 / 0

[JBoss JIRA] Closed: (TEIID-969) Time, date, and timestamp literals are being sent to Oracle as to_timestamp() regardless of their data type

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-969?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-969. ------------------------------- > Time, date, and timestamp literals are being sent to Oracle as to_timestamp() regardless of their data type > ----------------------------------------------------------------------------------------------------------- > > Key: TEIID-969 > URL: https://jira.jboss.org/browse/TEIID-969 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 6.0.0 > Environment: MMServer 5.5.3 > Oracle 10i > Oracle ANSI Connector > Reporter: Larry O'Leary > Assignee: Larry O'Leary > Fix For: 7.0 > > Attachments: mylyn-context.zip > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Source model uses a MetaMatrix type of timestamp and a native type of DATE. In prior releases this seems to have resulted in literal values that are being compared to the modeled column to be sent to Oracle as to_date(). Now, they are being sent as to_timestamp() which results in indexes being ignoreed for columns that are of DATE type. -- 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

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1135) NPE when getting RowCount for SalesForce (from SQuirreL)

by Paul Nittel (JIRA)

NPE when getting RowCount for SalesForce (from SQuirreL) -------------------------------------------------------- Key: TEIID-1135 URL: https://jira.jboss.org/browse/TEIID-1135 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.0 Environment: Teiid 7 CR2, Fedora 12, Sun JDK Reporter: Paul Nittel Assignee: Steve Hawkins Attachments: bob-ds.xml, RowCountError.log, SalesFarceVDB.vdb To reproduce this test, I started JBossAS, went to SQuirreL, selected Salesforce.Contact, and selected the RowCount attribute. (As an aside, the 3 truststore errors appear before the NPE.) VDB, data source, and log file are attached. -- 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

14 years, 8 months

2
4
0 / 0

[JBoss JIRA] Resolved: (TEIID-108) xsd type conversion should be consistent

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-108?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins resolved TEIID-108. --------------------------------- Resolution: Done fixed the conversions used for xml document model documents, xmlquery/table passing, xmltable columns, and xmlelement/forest content. > xsd type conversion should be consistent > ---------------------------------------- > > Key: TEIID-108 > URL: https://jira.jboss.org/browse/TEIID-108 > Project: Teiid > Issue Type: Bug > Components: SOAP Services, XML Connector > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Fix For: 7.1 > > > Defect Tracker #23654: [This came from our consultant Jimmy Fernandez' Case 4795, for customer MITRE]. > Jimmy wrote: "When modeling Web Services with our Web Service to relational importer and the column type on the request table out are dateTime objects; the SOAP/XML connectors should be converting the specific column to the xsd:dateTime object specifications. It would not hurt to ensure that we are following the correct specification for other xsd objects as well." -- 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

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-108) xsd type conversion should be consistent

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-108?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins commented on TEIID-108: ------------------------------------- The workaround for 7.0 when using timestamp, date, or time types with xmltable is to wrap the xpath expression in an appropriate function, e.g. columns t timestamp path 'xs:dateTime(<some path>/text())' after this fix, you'll be able to just use columns t timestamp path '<some path>' > xsd type conversion should be consistent > ---------------------------------------- > > Key: TEIID-108 > URL: https://jira.jboss.org/browse/TEIID-108 > Project: Teiid > Issue Type: Bug > Components: SOAP Services, XML Connector > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Fix For: 7.1 > > > Defect Tracker #23654: [This came from our consultant Jimmy Fernandez' Case 4795, for customer MITRE]. > Jimmy wrote: "When modeling Web Services with our Web Service to relational importer and the column type on the request table out are dateTime objects; the SOAP/XML connectors should be converting the specific column to the xsd:dateTime object specifications. It would not hurt to ensure that we are following the correct specification for other xsd objects as well." -- 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

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-108) xsd type conversion should be consistent

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-108?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins updated TEIID-108: -------------------------------- Summary: xsd type conversion should be consistent (was: SOAP/XML Connectors should convert to the column type specified in WS request table) Fix Version/s: 7.1 (was: 8.x) Affects Version/s: 6.0.0 (was: 8.x) Component/s: SOAP Services Changing the defect to apply to all places were we are doing xsd type conversion: SQL/XML (xmltable, xmlelement, xml document model) > xsd type conversion should be consistent > ---------------------------------------- > > Key: TEIID-108 > URL: https://jira.jboss.org/browse/TEIID-108 > Project: Teiid > Issue Type: Bug > Components: SOAP Services, XML Connector > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Fix For: 7.1 > > > Defect Tracker #23654: [This came from our consultant Jimmy Fernandez' Case 4795, for customer MITRE]. > Jimmy wrote: "When modeling Web Services with our Web Service to relational importer and the column type on the request table out are dateTime objects; the SOAP/XML connectors should be converting the specific column to the xsd:dateTime object specifications. It would not hurt to ensure that we are following the correct specification for other xsd objects as well." -- 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

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-943) Fully implement client streaming of lobs/readers/streams

by Steven Hawkins (JIRA)

Fully implement client streaming of lobs/readers/streams -------------------------------------------------------- Key: TEIID-943 URL: https://jira.jboss.org/jira/browse/TEIID-943 Project: Teiid Issue Type: Feature Request Components: JDBC Driver Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.1 Client transmission of large objects is either not implemented or is implemented through fully materializing. We should instead allow for streaming backed by temp files on the server. -- 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, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIID-1045) Provide a admin method to "export" a Data Source.

by Ramesh Reddy (JIRA)

Provide a admin method to "export" a Data Source. ------------------------------------------------- Key: TEIID-1045 URL: https://jira.jboss.org/jira/browse/TEIID-1045 Project: Teiid Issue Type: Feature Request Components: AdminApi Affects Versions: 7.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Priority: Minor Fix For: 7.0 As of 7.0 M3, there is no admin method to export a data source that is defined inside the AS. This needs to be supported for the tooling purposes. Also, the "addDataSource" only supports to create XA data sources. It should also allow to create "local" data sources. -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-944) Provide a separate Admin connection

by Ramesh Reddy (JIRA)

Provide a separate Admin connection ----------------------------------- Key: TEIID-944 URL: https://jira.jboss.org/jira/browse/TEIID-944 Project: Teiid Issue Type: Sub-task Components: AdminApi, Server Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.0 Currently the Admin API can be accessed from JDBC API and as well a separate connection on the same port as the JDBC connection. Since in the container environment the Admin API is based on the Profile Service this needs to be on its own connection that is subject to the same authorization checks as of the profile service/jmx-console. It will no longer available on the JDBC connection. Although, we can still serve the both connections on same port as the JDBC, by having a separate port the traffic on the Admin connection can be by default encrypted always, and the number of IO threads will be limited and do not hog the JDBC connection threads. -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-851) API improvements for custom connector development

by Mark Drilling (JIRA)

API improvements for custom connector development ------------------------------------------------- Key: TEIID-851 URL: https://jira.jboss.org/jira/browse/TEIID-851 Project: Teiid Issue Type: Feature Request Components: Connector API Affects Versions: 6.1.0 Reporter: Mark Drilling Assignee: Steven Hawkins Priority: Minor I'm building a custom connector, and I was trying to figure out a way to get information on whether or not a certain column in a Source Model is a Primary or Foreign Key. Here's an example of the code I've been trying: MetadataID mdID = group.getMetadataID(); //group is an IGroup String tableName = metadata.getObject(mdID).getNameInSource(); However, there doesn't appear to be a way to determine which column is Primary or Foreign Key. One thing I did notice playing around with the API, the MetadataObject contains a TableRecordImpl object that contains all sorts of MetaData info. That class appears to have tons of great info, along with getters and setters, including one called getForeignKeyIDs. Don't know if there's maybe a reason it's abstracted such that we can't get to it, but being able to get that and the other info out of that object could be highly beneficial. Maybe this is something that could be added to the API in the future? -- 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, 8 months

3
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2010