October 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2173) Need a way to clear validation errors on VDBMetaData / ModelMetaData.

by Mark Drilling (JIRA)

Mark Drilling created TEIID-2173: ------------------------------------ Summary: Need a way to clear validation errors on VDBMetaData / ModelMetaData. Key: TEIID-2173 URL: https://issues.jboss.org/browse/TEIID-2173 Project: Teiid Issue Type: Enhancement Components: AdminApi Affects Versions: 8.1 Reporter: Mark Drilling Assignee: Ramesh Reddy Scenario: I am working with a VDB in object form, then deploy the xml form of it via the AdminAPI. Later, I retrieve the VDBMetaData object - using adminAPI.getVDBs(). Then I want to make some changes to it and attempt a redeploy. Problem; If there was a problem with the original VDB deployment, the VDBMetaData object may have validation errors. In order to successfully redeploy, I need to clear the validation errors. I dont see a way to conveniently clear the model errors so I can attempt a redeploy. Can you add a method to clear the validation errors or clone the model without errors, so that I can redeploy? -- 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, 1 month

2
3
0 / 0

[JBoss JIRA] (TEIID-2141) create an objecttable table function

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2141: ------------------------------------- Summary: create an objecttable table function Key: TEIID-2141 URL: https://issues.jboss.org/browse/TEIID-2141 Project: Teiid Issue Type: Feature Request Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.2 Analogous to xmltable, we should offer an objecttable function to get values off of an object. The choice of scripting/path language could even be configurable. This would help eliminate some of the common complexity of relational-object translations and can be used to perform denoralization without a join - and could be first implemented to in databasemetadata views to speed up databasemetadata query processing. -- 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, 1 month

1
4
0 / 0

[JBoss JIRA] (TEIID-2174) DDL metadata types are case sensitive

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2174: ------------------------------------- Summary: DDL metadata types are case sensitive Key: TEIID-2174 URL: https://issues.jboss.org/browse/TEIID-2174 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.2 The map used to lookup types is case sensitive. -- 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, 1 month

1
2
0 / 0

[JBoss JIRA] (TEIID-2156) File translator should throw an error when data file not found

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2156: ----------------------------------- Summary: File translator should throw an error when data file not found Key: TEIID-2156 URL: https://issues.jboss.org/browse/TEIID-2156 Project: Teiid Issue Type: Enhancement Components: Misc. Connectors Affects Versions: 8.1, 8.0 Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 8.2 Currently when the File translator does not find the underlying file it considers as data not available, thus returns no results. There is configuration property "isExceptionIfFileNotFound" currently available that can be set to throw an exception if the data file not found. This by default is not turned off, this should be turned on by default. -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] (TEIID-2112) consistent handling of local timezone on xsd:date, xsd:datetime, and xsd:time values that have no timezone specified.

by Johnathon Lee (JIRA)

Johnathon Lee created TEIID-2112: ------------------------------------ Summary: consistent handling of local timezone on xsd:date, xsd:datetime, and xsd:time values that have no timezone specified. Key: TEIID-2112 URL: https://issues.jboss.org/browse/TEIID-2112 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 7.4.4 Reporter: Johnathon Lee Assignee: Steven Hawkins The server is taking the incoming ts string and converting it to a Z value via the server timezone (handled by STax). When the response document is delivered Saxon converts a non-timezoned value into an assumed Z value - which is not consistent with the STax handling. This is within the bounds of XML processing as the absence of timezone information leaves the timezone interpretation up to the implementation - "timezone of some unspecified locality as prescribed by the appropriate legal authority". However, these two paths should be consistent,so a patch would set the local timezone on xsd:date, xsd:datetime, and xsd:time values that have no timezone specified. -- 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, 1 month

4
21
0 / 0

[JBoss JIRA] (TEIID-2034) Add ISPN integration

by Van Halbert (JIRA)

Van Halbert created TEIID-2034: ---------------------------------- Summary: Add ISPN integration Key: TEIID-2034 URL: https://issues.jboss.org/browse/TEIID-2034 Project: Teiid Issue Type: Sub-task Components: Misc. Connectors Reporter: Van Halbert Assignee: Van Halbert Fix For: 7.7.1 -- 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, 1 month

2
3
0 / 0

[JBoss JIRA] (TEIID-2126) xmltype derserialization fails with jdk1.5 jar

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2126: ------------------------------------- Summary: xmltype derserialization fails with jdk1.5 jar Key: TEIID-2126 URL: https://issues.jboss.org/browse/TEIID-2126 Project: Teiid Issue Type: Feature Request Components: JDBC Driver Affects Versions: 8.0 Reporter: Steven Hawkins Assignee: Steven Hawkins The jdk 1.5 jdbc jar is actually a 1.4 compatible jar. Our version 1 serialization expected by 8.0+ clients writes XMLType values directly to the output which leads to the deserialization getting out of place since it cannot read a retrotranslated value that is no longer an enum as an enum. -- 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, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (TEIID-1460) Have teiid emulate a native postgresql database connection

by Graeme Gillies (JIRA)

Have teiid emulate a native postgresql database connection ---------------------------------------------------------- Key: TEIID-1460 URL: https://issues.jboss.org/browse/TEIID-1460 Project: Teiid Issue Type: Feature Request Components: Server Affects Versions: 7.3 Environment: All environments Reporter: Graeme Gillies Assignee: Steven Hawkins Priority: Minor Currently we are using postgresql-odbc, and unixODBC to connect to teiid via the emulated postgresql ODBC connection on port 35432. Unfortunately, this is cumbersome to use, requires fiddling with setting up ODBC, and is difficult for integration into non-java languages (that have to use the ODBC connection). What we would like is for teiid to emulate a postgresql database such that we can point typical postgresql tools (such as psql) to port 35432 (or some other port) and they will "work". That would also allow us to use each languages native/preferred method of connecting to a postgresql database to connect to teiid. E.g. DBD::Postgres for perl, ruby-pg for ruby, pg/pgdb in python, etc. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
17
0 / 0

[JBoss JIRA] (TEIID-2145) DDL options clause with namespace prefix is failing to parse correctly

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2145: ----------------------------------- Summary: DDL options clause with namespace prefix is failing to parse correctly Key: TEIID-2145 URL: https://issues.jboss.org/browse/TEIID-2145 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.1 Reporter: Ramesh Reddy Assignee: Steven Hawkins when there is namespace prefix in the options clause with DDL metadata it fails to parse colon (:) as the prefix separator. for example ddl below will fail {code} SET NAMESPACE 'http://teiid.org/rest' AS REST; CREATE VIRTUAL PROCEDURE g1Table() RETURNS TABLE (xml_out xml) OPTIONS (UPDATECOUNT 0, REST:METHOD 'GET', REST:URI 'g1') AS BEGIN SELECT XMLELEMENT(NAME "all", XMLAGG(XMLELEMENT(NAME "row", XMLFOREST(e1, e2)))) AS xml_out FROM Txns.G1; END {code} either Teiid needs to find another delimiter or escape it or parser it as string rather than in id() in the parser -- 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, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1374) Nested correlated reference issue with rewritten queries

by Steven Hawkins (JIRA)

Nested correlated reference issue with rewritten queries -------------------------------------------------------- Key: TEIID-1374 URL: https://jira.jboss.org/browse/TEIID-1374 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins In a query such as "select * from bqt1.smalla where exists (select intnum from bqt1.smalla x where smalla.intnum = x.intnum and exists (select intnum from bqt1.smalla where exists (select intnum from bqt1.smalla x where smalla.intnum = x.intnum)))" we will inappropriately report that the top exists subquery has 2 correlated references since we see the more deeply nested smalla.intnum also. This is generally not a issue, it can introduce errors in places where subqueries are rewritten, such as with subquery optimization or inherently updatable view queries. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2012