January 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1495) Validate the TeraData Translator

by Ramesh Reddy (JIRA)

Validate the TeraData Translator -------------------------------- Key: TEIID-1495 URL: https://issues.jboss.org/browse/TEIID-1495 Project: Teiid Issue Type: Task Components: JDBC Connector Affects Versions: 7.3 Reporter: Ramesh Reddy Fix For: 7.4 Currently the Teiid does provide a Teradata translator, however it has been taken from the old MMX code, however it was never validated with Teiid to make sure this works correctly with the data source. -- 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-1891) COMMAND Logging incorrectly reporting END USER COMMAND record count in EDS for forward only resultsets

by Johnathon Lee (Created) (JIRA)

COMMAND Logging incorrectly reporting END USER COMMAND record count in EDS for forward only resultsets ------------------------------------------------------------------------------------------------------ Key: TEIID-1891 URL: https://issues.jboss.org/browse/TEIID-1891 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1, 7.2, 7.3, 7.4, 7.5, 7.6 Reporter: Johnathon Lee Assignee: Steven Hawkins Fix For: 7.6.1, 8.0 Running a query [1] that returns 406 rows in sql client, near the end of my log I get this output [2]. [1] select * from CIS_Test.GetListOfLanguageNames [2] 2011-12-28 12:34:34,169 DEBUG [org.teiid.COMMAND_LOG] (Worker0_QueryProcessorQueue26) END USER COMMAND: endTime=2011-12-28 12:34:34.169 requestID=EED0CMZyYmnc.7 txID=null sessionID=EED0CMZyYmnc principal=teiid@teiid-security vdbName=CIStest vdbVersion=1 finalRowCount=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

12 years, 4 months

2
1
0 / 0

[JBoss JIRA] (TEIID-1890) Internal Materialized View - Load/Refresh and Assertion Failed

by Johnathon Lee (Created) (JIRA)

Internal Materialized View - Load/Refresh and Assertion Failed -------------------------------------------------------------- Key: TEIID-1890 URL: https://issues.jboss.org/browse/TEIID-1890 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 7.3, 7.4, 7.6 Environment: Windows Server 2008 R2 64 bits, JBoss EAP 5.1 Reporter: Johnathon Lee Assignee: Steven Hawkins We have about 20 tables translated to 20 materialized view (internal with cache hint - /*+ cache(ttl:14400000) */). 2 dreaded behaviours: 1. On start up with application (application starts hitting app), certain query will cause ASSERTION FAILED 2. On reloading cache, teiid starts to fails with same behaviour. 2011-12-14 18:26:40,201 WARN [org.teiid.CONNECTOR] (Worker2228_QueryProcessorQueue1132419) Connector worker process failed for atomic-request=mCMnhhZ9fLcU.100.3.334092 [JDBCExecutionException] 0: Error Code:0 Message:'ASSERTION FAILED: expected reference to be not null' error executing statement(s):[....] 1 [TeiidSQLException]ASSERTION FAILED: expected reference to be not null 2 [TeiidException]ASSERTION FAILED: expected reference to be not null 3 [AssertionError]ASSERTION FAILED: expected reference to be not null at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:90) at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:263) at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:281) at org.teiid.dqp.internal.process.DataTierTupleSource.access$000(DataTierTupleSource.java:71) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:123) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:120) at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:107) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:188) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:116) at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:290) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: org.teiid.jdbc.TeiidSQLException: ASSERTION FAILED: expected reference to be not null at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:109) at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:69) at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:497) at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:214) at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:342) at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:86) ... 12 more Caused by: [TeiidException]ASSERTION FAILED: expected reference to be not null 1 [AssertionError]ASSERTION FAILED: expected reference to be not null at org.teiid.client.ResultsMessage.setException(ResultsMessage.java:177) at org.teiid.dqp.internal.process.RequestWorkItem.sendError(RequestWorkItem.java:557) at org.teiid.dqp.internal.process.RequestWorkItem.attemptClose(RequestWorkItem.java:335) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:218) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49) ... 6 more Caused by: java.lang.AssertionError: ASSERTION FAILED: expected reference to be not null at org.teiid.core.util.Assertion.failed(Assertion.java:73) at org.teiid.core.util.Assertion.isNotNull(Assertion.java:100) at org.teiid.core.util.Assertion.isNotNull(Assertion.java:92) at org.teiid.query.processor.relational.RelationalNode.getProjectionIndexes(RelationalNode.java:366) at org.teiid.query.tempdata.TempTable$QueryTupleSource.<init>(TempTable.java:141) at org.teiid.query.tempdata.TempTable$QueryTupleSource.<init>(TempTable.java:130) at org.teiid.query.tempdata.TempTable.createTupleSource(TempTable.java:410) at org.teiid.query.tempdata.TempTable.createTupleSource(TempTable.java:402) at org.teiid.query.tempdata.TempTableDataManager.registerQuery(TempTableDataManager.java:437) at org.teiid.query.tempdata.TempTableDataManager.registerRequest(TempTableDataManager.java:182) at org.teiid.query.tempdata.TempTableDataManager.registerRequest(TempTableDataManager.java:170) at org.teiid.query.processor.relational.AccessNode.registerRequest(AccessNode.java:197) at org.teiid.query.processor.relational.AccessNode.open(AccessNode.java:118) at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:250) at org.teiid.query.processor.relational.JoinStrategy.openLeft(JoinStrategy.java:95) at org.teiid.query.processor.relational.JoinNode.open(JoinNode.java:138) at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:250) at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:250) at org.teiid.query.processor.relational.UnionAllNode.open(UnionAllNode.java:72) at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:250) at org.teiid.query.processor.relational.UnionAllNode.open(UnionAllNode.java:72) at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:250) at org.teiid.query.processor.relational.UnionAllNode.open(UnionAllNode.java:72) at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:250) at org.teiid.query.processor.relational.UnionAllNode.open(UnionAllNode.java:72) at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:250) at org.teiid.query.processor.relational.RelationalPlan.open(RelationalPlan.java:152) at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:134) at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:105) at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:115) at org.teiid.query.processor.relational.SubqueryAwareEvaluator.evaluateSubquery(SubqueryAwareEvaluator.java:129) at org.teiid.query.eval.Evaluator.evaluate(Evaluator.java:445) at org.teiid.query.eval.Evaluator.evaluateTVL(Evaluator.java:218) at org.teiid.query.eval.Evaluator.evaluate(Evaluator.java:203) at org.teiid.query.processor.relational.SelectNode.nextBatchDirect(SelectNode.java:102) at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:274) at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:162) at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:274) at org.teiid.query.processor.BatchIterator.finalRow(BatchIterator.java:70) at org.teiid.common.buffer.AbstractTupleSource.getCurrentTuple(AbstractTupleSource.java:69) at org.teiid.query.processor.BatchIterator.getCurrentTuple(BatchIterator.java:82) at org.teiid.common.buffer.AbstractTupleSource.nextTuple(AbstractTupleSource.java:48) at org.teiid.query.processor.relational.SortUtility.initialSort(SortUtility.java:214) at org.teiid.query.processor.relational.SortUtility.sort(SortUtility.java:168) at org.teiid.query.processor.relational.SortNode.sortPhase(SortNode.java:96) at org.teiid.query.processor.relational.SortNode.nextBatchDirect(SortNode.java:85) at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:274) at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:161) at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:150) at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:105) at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:115) at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:250) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:184) ... 7 more 2011-12-14 18:26:40,201 WARN [org.teiid.PROCESSOR] (Worker2205_QueryProcessorQueue1132421) Processing exception 'Error Code:0 Message:Error Code:0 Message:'ASSERTION FAILED: expected reference to be not null' error executing statement(s): [....] for request mCMnhhZ9fLcU.100. Exception type org.teiid.core.TeiidProcessingException thrown from org.teiid.core.util.Assertion.failed(Assertion.java:73). Enable more detailed logging to see the entire stacktrace. -- 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
1
0 / 0

[JBoss JIRA] (TEIID-1888) Query timeout is superceded by synch ttl

by Johnathon Lee (Created) (JIRA)

Query timeout is superceded by synch ttl ---------------------------------------- Key: TEIID-1888 URL: https://issues.jboss.org/browse/TEIID-1888 Project: Teiid Issue Type: Bug Components: JDBC Driver Affects Versions: 7.4.1 Reporter: Johnathon Lee Assignee: Steven Hawkins Fix For: 7.6.1, 8.0 The query execution future is using a get call which is subject to the default synch ttl. -- 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
1
0 / 0

[JBoss JIRA] (TEIID-1887) Netezza translator using INTNNOT when it should use INT4NOT

by Johnathon Lee (Created) (JIRA)

Netezza translator using INTNNOT when it should use INT4NOT ----------------------------------------------------------- Key: TEIID-1887 URL: https://issues.jboss.org/browse/TEIID-1887 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.6 Reporter: Johnathon Lee Assignee: Steven Hawkins Fix For: 7.6.1, 8.0 This was found during query testing. The query in question is RDBMS_Test_Queries_5700_TestQuery153. With Netezza as the source, this query: SELECT IntKey, BITNOT(IntKey) as BitPart FROM BQT1.SmallA ORDER BY IntKey Produces: Caught SQLException: Error Code:1100 Message:Remote org.teiid.core.TeiidProcessingException: Error Code:1100 Message:Source: Error Code:1100 Message:'ERROR: Function 'INTNNOT(INT4)' does not exist Unable to identify a function that satisfies the given argument types You may need to add explicit typecasts ' error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."INTKEY" AS c_0, intNnot(g_0."INTKEY") AS c_1 FROM "SMALLA" AS g_0 ORDER BY c_0] Dev responded with: [It appears] this should be calling INT4NOT. The Netezza users guide is a little unclear. More queries failing in a similar fashion: SELECT IntKey, BITXOR(IntKey, 1010) as BitPart FROM BQT1.SmallA ORDER BY IntKey Caught SQLException: Error Code:1100 Message:Remote org.teiid.core.TeiidProcessingException: Error Code:1100 Message:Source: Error Code:1100 Message:'ERROR: Function 'INTNXOR(INT4, INT4)' does not exist Unable to identify a function that satisfies the given argument types You may need to add explicit typecasts ' error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."INTKEY" AS c_0, intNxor(g_0."INTKEY", 1010) AS c_1 FROM "SMALLA" AS g_0 ORDER BY c_0] SELECT IntKey, BITOR(IntKey, 1010) as BitPart FROM BQT1.SmallA ORDER BY IntKey Caught SQLException: Error Code:1100 Message:Remote org.teiid.core.TeiidProcessingException: Error Code:1100 Message:Source: Error Code:1100 Message:'ERROR: Function 'INTNOR(INT4, INT4)' does not exist Unable to identify a function that satisfies the given argument types You may need to add explicit typecasts ' error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."INTKEY" AS c_0, intNor(g_0."INTKEY", 1010) AS c_1 FROM "SMALLA" AS g_0 ORDER BY c_0] SELECT IntKey, BITAND(IntKey, 1010) as BitPart FROM BQT1.SmallA ORDER BY IntKey Caught SQLException: Error Code:1100 Message:Remote org.teiid.core.TeiidProcessingException: Error Code:1100 Message:Source: Error Code:1100 Message:'ERROR: Function 'INTNAND(INT4, INT4)' does not exist Unable to identify a function that satisfies the given argument types You may need to add explicit typecasts ' error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."INTKEY" AS c_0, intNand(g_0."INTKEY", 1010) AS c_1 FROM "SMALLA" AS g_0 ORDER BY c_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

12 years, 4 months

2
1
0 / 0

[JBoss JIRA] (TEIID-1885) Teiid is handling MySQL5.0 returning DAYNAME as a blob

by Johnathon Lee (Created) (JIRA)

Teiid is handling MySQL5.0 returning DAYNAME as a blob ------------------------------------------------------ Key: TEIID-1885 URL: https://issues.jboss.org/browse/TEIID-1885 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.6 Reporter: Johnathon Lee Assignee: Steven Hawkins Fix For: 7.6.1, 8.0 Attachments: QT_MySql50_Push.vdb SELECT IntKey, DAYNAME(datevalue) FROM BQT1.SmallA ORDER BY IntKey LIMIT 10 Fails with: Caught SQLException: Invalid conversion from type class org.teiid.core.types.BlobType with value 'javax.sql.rowset.serial.SerialBlob@6482112e' to type class java.lang.String Dev indicaters, "The driver returns the bytes, which we treat as a blob. We have an explicit workaround in the translator for the char function, but I've never seen this outside of the char function. There may be an issue with the http://dev.mysql.com/doc/refman/5.5/en/server-system-variables.html#sysva... setting also that could influence how the value is returned." The server setting is en_US. -- 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
1
0 / 0

[JBoss JIRA] (TEIID-965) Need Excel file importer / connector

by Ripan Karmakar (Commented) (JIRA)

[ https://issues.jboss.org/browse/TEIID-965?page=com.atlassian.jira.plugin.... ] Ripan Karmakar commented on TEIID-965: -------------------------------------- Thanks Ramesh for the info. It would be really great if you can elaborate on the connector mentioned above. Can you please specify the line where we need to make a change. > Need Excel file importer / connector > ------------------------------------ > > Key: TEIID-965 > URL: https://issues.jboss.org/browse/TEIID-965 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 7.0 > Reporter: Steven Hawkins > Fix For: Open To Community > > > Really need to add an Excel connector in SP1. The easiest way to do this is probably with one of the open source JDBC drivers that work over Excel files. > Something like: > https://xlsql.dev.java.net/ - Excel JDBC driver (GPL unfortunately, so we probably can't distribute the driver) > http://www.andykhan.com/jexcelapi/ - Java Excel API (GPL too) > http://xlsjdbc.sourceforge.net/ - LGPL (uses Apache POI), really cheesy and maybe not being updated > http://jakarta.apache.org/poi/ - Excel API, event-based and not particularly friendly > http://www.vistaportal.com/products/vistajdbc-QA.htm - commercial -- 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
0
0 / 0

[JBoss JIRA] (TEIID-965) Need Excel file importer / connector

by Ramesh Reddy (Commented) (JIRA)

[ https://issues.jboss.org/browse/TEIID-965?page=com.atlassian.jira.plugin.... ] Ramesh Reddy commented on TEIID-965: ------------------------------------ I believe the query you used with (a) or (d) are correct ones, if you used the default sheet name. If you renamed the sheet name then the table name would different. Use of (b) and (c) are not applicable as they are treating the EXCEL file as the text file, and the connection you created is with JDBC <-> ODBC bridge driver. Currently Excel files can not be read with text connectors, they are only accessed with JDBC ODBC bridge. > Need Excel file importer / connector > ------------------------------------ > > Key: TEIID-965 > URL: https://issues.jboss.org/browse/TEIID-965 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 7.0 > Reporter: Steven Hawkins > Fix For: Open To Community > > > Really need to add an Excel connector in SP1. The easiest way to do this is probably with one of the open source JDBC drivers that work over Excel files. > Something like: > https://xlsql.dev.java.net/ - Excel JDBC driver (GPL unfortunately, so we probably can't distribute the driver) > http://www.andykhan.com/jexcelapi/ - Java Excel API (GPL too) > http://xlsjdbc.sourceforge.net/ - LGPL (uses Apache POI), really cheesy and maybe not being updated > http://jakarta.apache.org/poi/ - Excel API, event-based and not particularly friendly > http://www.vistaportal.com/products/vistajdbc-QA.htm - commercial -- 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
0
0 / 0

[JBoss JIRA] (TEIID-965) Need Excel file importer / connector

by Ripan Karmakar (Commented) (JIRA)

[ https://issues.jboss.org/browse/TEIID-965?page=com.atlassian.jira.plugin.... ] Ripan Karmakar commented on TEIID-965: -------------------------------------- We have created one client program to fetch data from text and csv data files taking Teiid support. This is working fine. We are using Teiid 7.6.0 and the JBoss 5.1.0 GA. But facing problem for excel (.xls) and xml files through we have followed the same approach. The config are as below: 1.excel-file-ds.xml: <?xml version="1.0" encoding="UTF-8"?> <datasources> <no-tx-datasource> <jndi-name>excel-file</jndi-name>  <connection-url>jdbc:odbc:Driver={Microsoft Excel Driver (*.xls)};DBQ=C:/abcd.xls</connection-url> <driver-class>sun.jdbc.odbc.JdbcOdbcDriver</driver-class> <transaction-isolation>TRANSACTION_NONE</transaction-isolation> <min-pool-size>1</min-pool-size> <max-pool-size>1</max-pool-size> <idle-timeout-minutes>5</idle-timeout-minutes> </no-tx-datasource> </datasources> 2. Added entry in portfolio-vdb.xml: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <vdb name="DynamicPortfolio" version="1"> <description>A Dynamic VDB</description> <property name="UseConnectorMetadata" value="true" /> <model name="ExcelData"> <source name="excel-connector" translator-name="jdbc-simple" connection-jndi-name="java:excel-file"/> </model> </vdb> 3. abcd.xls Name Address Country ZipCode John 1st Street USA 12222 Mac 2nd Street USA 34421 Peter 3rd Street USA 54321 The connection Code: String url = "jdbc:teiid:" + vdb + "@mm://" + host + ":" + port; Class.forName("org.teiid.jdbc.TeiidDriver"); DriverManager.getConnection(url, user, password); The connection is getting created successfully. But while executing the query we are not getting any result output. code snipet looks like this sql = "SELECT * from (call ExcelDS.getTextFiles('abcd.xls')) f, TEXTTABLE(f.file COLUMNS NAME string,ADDRESS string,COUNTRY string,ZIPCODE bigdecimal HEADER) as stock "; statement = connection.createStatement(); results = statementForCSV.executeQuery(sql); results.next(); Running the program in debugging mode in eclipse we can see that the connection and statement all are created successfully but not getting any data from the ResultSet results. Observations: We have also tried to change the query but not succeed. a. sql = "SELECT * from [Sheet1$]"; // not working b. sql = "SELECT * from (call ExcelData.getTextFiles('Sheet1$'))"; // not working c. sql = "select * from (call ExcelDS.getTextFiles('abcd.xls'[Sheet1$])) "; // not working d. sql = "select * from ExcelDS.[Sheet1$] "; // not working When we tried to connect to the Teiid datasource, we can see that the table name as: c:/abcd.Sheet1$ May be this is the reason that the tables cann't be queried. Can you also suggest what sql query needs to be used to query the excel. Exception: with sql: "select * from ExcelData.c:/abcd.Sheet1$"; Exception in thread "main" org.teiid.jdbc.TeiidSQLException: Remote org.teiid.api.exception.query.QueryParserException: Parsing error: Encountered ":" at line 1, column 26. > Need Excel file importer / connector > ------------------------------------ > > Key: TEIID-965 > URL: https://issues.jboss.org/browse/TEIID-965 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 7.0 > Reporter: Steven Hawkins > Fix For: Open To Community > > > Really need to add an Excel connector in SP1. The easiest way to do this is probably with one of the open source JDBC drivers that work over Excel files. > Something like: > https://xlsql.dev.java.net/ - Excel JDBC driver (GPL unfortunately, so we probably can't distribute the driver) > http://www.andykhan.com/jexcelapi/ - Java Excel API (GPL too) > http://xlsjdbc.sourceforge.net/ - LGPL (uses Apache POI), really cheesy and maybe not being updated > http://jakarta.apache.org/poi/ - Excel API, event-based and not particularly friendly > http://www.vistaportal.com/products/vistajdbc-QA.htm - commercial -- 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
0
0 / 0

[JBoss JIRA] (TEIID-965) Need Excel file importer / connector

by Steven Hawkins (Commented) (JIRA)

[ https://issues.jboss.org/browse/TEIID-965?page=com.atlassian.jira.plugin.... ] Steven Hawkins commented on TEIID-965: -------------------------------------- Ripan, what error are you getting? Did you create the physical model via an import from the jdbc/odbc driver? > Need Excel file importer / connector > ------------------------------------ > > Key: TEIID-965 > URL: https://issues.jboss.org/browse/TEIID-965 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 7.0 > Reporter: Steven Hawkins > Fix For: Open To Community > > > Really need to add an Excel connector in SP1. The easiest way to do this is probably with one of the open source JDBC drivers that work over Excel files. > Something like: > https://xlsql.dev.java.net/ - Excel JDBC driver (GPL unfortunately, so we probably can't distribute the driver) > http://www.andykhan.com/jexcelapi/ - Java Excel API (GPL too) > http://xlsjdbc.sourceforge.net/ - LGPL (uses Apache POI), really cheesy and maybe not being updated > http://jakarta.apache.org/poi/ - Excel API, event-based and not particularly friendly > http://www.vistaportal.com/products/vistajdbc-QA.htm - commercial -- 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
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2012