September 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Commented: (TEIID-962) Create new system function to dump temp table contents to file.

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-962?page=com.atlassian.jira.plugin.sy... ] Steven Hawkins commented on TEIID-962: -------------------------------------- Another approach for those who want to treat text as tables (not just import/export) is to use the text table functionality of hsql http://hsqldb.org/doc/guide/ch06.html to represent the files as tables, then import the tables into teiid. We could also consider providing a wrapper of this approach in a more turnkey manner. > Create new system function to dump temp table contents to file. > ----------------------------------------------------------------- > > Key: TEIID-962 > URL: https://jira.jboss.org/browse/TEIID-962 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Environment: All > Reporter: Ken Johnson > Assignee: Steven Hawkins > Fix For: 7.2 > > > A requirement to produce a CSV file reflecting the contents of a query result set so it can be subsequently FTP'd or email'd. In Nov 07 implemented this feature using the exec connector, a shell script and mods to JDBCISQL. > Suggested capability: function will take the following parameters: > - Temp table name as string > - Target file name (path qualified) as string > - Delimiter as string > When invoked, the specified temp table contents will be written out to the specified file using the specified delimiter to separate the column values. > This generic capability will allow the CSV file thats needed and subsequently process it with other UDF functionality as necessary. > Open questions: > 1. How does file path behave in a clustered environment? Is it relative to the MM Server install dir or fully qualified? > Suggest this feature remain undocumented for the short term. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-1242) teiid VDB inconsistent behavior

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/browse/TEIID-1242?page=com.atlassian.jira.plugin.s... ] Ramesh Reddy resolved TEIID-1242. --------------------------------- Assignee: Ramesh Reddy Resolution: Rejected This is user error. You should be using the query as SELECT fullname, price FROM (EXEC TextFileData.getTextFiles('Company.txt') ) AS ff, TEXTTABLE(ff.file COLUMNS symbol string, fullname string, price string) AS c the "getTextFiles" method is exposed on a specific model. > teiid VDB inconsistent behavior > ------------------------------- > > Key: TEIID-1242 > URL: https://jira.jboss.org/browse/TEIID-1242 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.1 > Environment: RHEL5, openjdk, SOA-P 5.1.0.dev3 > Reporter: Aleksandar Kostadinov > Assignee: Ramesh Reddy > Attachments: teiid-text-example.tgz > > > A dynamic VDB doesn't work properly on first server startup. One needs to restart server once to get a proper query result. > To reproduce: > cd jbossas/server > cp -a all dataservices > cd dataservices > unzip teiid-7.1.0.Final-jboss-dist.zip > tar xvfz teiid-text-example.tgz #see the file attached > 1. setup jbossas config with teiid and VDB > 2. start server > 3. connect & query => ERROR org.teiid.jdbc.TeiidSQLException: > Remote org.teiid.api.exception.query.QueryResolverException: interoperability does not exist. > 4. restart server > 5. connect & query => result retrieved > test query I used through adminshell: "SELECT fullname, price FROM (EXEC Interoperability.getTextFiles('Company.txt') ) AS ff, TEXTTABLE(ff.file COLUMNS symbol string, fullname string, price string) AS c" > When query is failing I see this in server log: > 05:00:18,225 WARN [PROCESSOR] Processing exception 'interoperability does not exist.' for request 87zeTL/KvEF6.0. Exception type org.teiid.api.exception.query.QueryResolverException thrown from org.teiid.query.metadata.CompositeMetadataStore.getSchema(CompositeMetadataStore.java:65). Enable more detailed logging to see the entire stacktrace. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-1242) teiid VDB inconsistent behavior

by Aleksandar Kostadinov (JIRA)

[ https://jira.jboss.org/browse/TEIID-1242?page=com.atlassian.jira.plugin.s... ] Aleksandar Kostadinov moved SOA-2254 to TEIID-1242: --------------------------------------------------- Project: Teiid (was: JBoss Enterprise SOA Platform) Key: TEIID-1242 (was: SOA-2254) Affects Version/s: 7.1 (was: 5.1.0.dev2) Affects Testing: (was: [Blocks Testing]) Security: (was: Public) Component/s: Server (was: EDS) > teiid VDB inconsistent behavior > ------------------------------- > > Key: TEIID-1242 > URL: https://jira.jboss.org/browse/TEIID-1242 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.1 > Environment: RHEL5, openjdk, SOA-P 5.1.0.dev3 > Reporter: Aleksandar Kostadinov > Attachments: teiid-text-example.tgz > > > A dynamic VDB doesn't work properly on first server startup. One needs to restart server once to get a proper query result. > To reproduce: > cd jbossas/server > cp -a all dataservices > cd dataservices > unzip teiid-7.1.0.Final-jboss-dist.zip > tar xvfz teiid-text-example.tgz #see the file attached > 1. setup jbossas config with teiid and VDB > 2. start server > 3. connect & query => ERROR org.teiid.jdbc.TeiidSQLException: > Remote org.teiid.api.exception.query.QueryResolverException: interoperability does not exist. > 4. restart server > 5. connect & query => result retrieved > test query I used through adminshell: "SELECT fullname, price FROM (EXEC Interoperability.getTextFiles('Company.txt') ) AS ff, TEXTTABLE(ff.file COLUMNS symbol string, fullname string, price string) AS c" > When query is failing I see this in server log: > 05:00:18,225 WARN [PROCESSOR] Processing exception 'interoperability does not exist.' for request 87zeTL/KvEF6.0. Exception type org.teiid.api.exception.query.QueryResolverException thrown from org.teiid.query.metadata.CompositeMetadataStore.getSchema(CompositeMetadataStore.java:65). Enable more detailed logging to see the entire stacktrace. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-239) ENHANCEMENT: Costing beyond cardinality sould be propogated

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-239?page=com.atlassian.jira.plugin.sy... ] Steven Hawkins updated TEIID-239: --------------------------------- Fix Version/s: 8.0 (was: 7.2) pushing to 8 > ENHANCEMENT: Costing beyond cardinality sould be propogated > ----------------------------------------------------------- > > Key: TEIID-239 > URL: https://jira.jboss.org/browse/TEIID-239 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Priority: Minor > Fix For: 8.0 > > > Defect Tracker #24037: Currently values for ndv and nnv are recalculated at each plan node based upon the value at the physical layer. This is not a good estimate. Instead, these values should be propagated through the plan just like the cardinality and adjusted appropriately for join, unions, etc. It may also be good to allow the use of costing metadata on virtual layers. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-999) Create valid capabilities support for MS Excel and MS Access JDBC-ODBC Connectors

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-999?page=com.atlassian.jira.plugin.sy... ] Steven Hawkins updated TEIID-999: --------------------------------- Fix Version/s: 8.0 (was: 7.2) pushing to 8 > Create valid capabilities support for MS Excel and MS Access JDBC-ODBC Connectors > --------------------------------------------------------------------------------- > > Key: TEIID-999 > URL: https://jira.jboss.org/browse/TEIID-999 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Environment: MS Excel 2003 > Reporter: Larry O'Leary > Fix For: 8.0 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Create a capabilities set that can be used by the MS Access and MS Excel connectors. We currently offer the MS Excel connector which is using the generic JDBC capabilities and translators and the MS Access connector which is using its own capabilities and translators but they do not reflect MS Access. > The replacement connector types should work very much like the current ones but reflect the base capabilities offered by MS JET 4 and specific capabilities as defined by the MS Excel and MS Access limitations to the MS JET 4 implementation. At bare minimum we should support push-down of all currently defined capabilities and remove any current ones that are not valid for MS JET/MS Access/MS Excel. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-65) Precision of BigInteger and BigDecimal need to be limited

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-65?page=com.atlassian.jira.plugin.sys... ] Steven Hawkins updated TEIID-65: -------------------------------- Fix Version/s: 8.0 (was: 7.2) pushing to 8 > Precision of BigInteger and BigDecimal need to be limited > --------------------------------------------------------- > > Key: TEIID-65 > URL: https://jira.jboss.org/browse/TEIID-65 > Project: Teiid > Issue Type: Sub-task > Components: Common > Affects Versions: 8.x > Reporter: Steven Hawkins > Fix For: 8.0 > > > To ensure database and string conversion compatibility BigInteger and BigDecimal should be limited to 1000 digits of precision (taken from PostGres). -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1239) Preview Data in Teiid 7.0

by Monika Ahuja (JIRA)

Preview Data in Teiid 7.0 ------------------------- Key: TEIID-1239 URL: https://jira.jboss.org/browse/TEIID-1239 Project: Teiid Issue Type: Bug Components: JDBC Driver Affects Versions: 7.0 Environment: Eclipse Helios Reporter: Monika Ahuja Assignee: Steven Hawkins Scenario: I created a Metadata model using Teiid jdbc connector. I created a packaged diagram. In packaged diagram When I goto a table inside a database and click on preview data. I get the following error: DriverConnectionBase.error.driverDefinitionNotSpecified: null. Using the driver properties defined in database profile instead. I tried setting the connection profile for the my importeddata.xmi (right clicking, selecting modeling-->set connection profile--> selecting the connection in database). I saved my model. To see if my connection settings were set I right clicked on metadatamodel.xmi again and selected modeling -> Set connection profile, but the previously selected connection was missing. So, the moment I try to preview data I get the same error "DriverConnectionBase.error.driverDefinitionNotSpecified: null. Using the driver properties defined in database profile instead." -- 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, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2010