[JBoss JIRA] (TEIID-2020) Running Sybase procedure with jconnect driver in Teiid fails
by Debbie Steigner (JIRA)
Debbie Steigner created TEIID-2020:
--------------------------------------
Summary: Running Sybase procedure with jconnect driver in Teiid fails
Key: TEIID-2020
URL: https://issues.jboss.org/browse/TEIID-2020
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.4.1
Reporter: Debbie Steigner
Assignee: Steven Hawkins
On the attached Sybase_test.vdb, run the following
exec sp_rows_between(1,6,'SmallA')
You'll receive the below error:
[TranslatorException] ZZZZZ: Error Code:ZZZZZ Message:'{ ?= call sp_rows_between(?,?,?)}' error executing statement(s): {1}
1 [SybSQLException]Execute cursor 'jconnect_implicit_3' is declared on a procedure which contains a non-SELECT or a SELECT with a COMPUTE clause. For the declaration of this cursor to be legal it should have a single SELECT statement without a COMPUTE clause.
at org.teiid.translator.jdbc.JDBCProcedureExecution.execute(JDBCProcedureExecution.java:70)
at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:264)
at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:338)
at org.teiid.dqp.internal.process.DataTierTupleSource.access$000(DataTierTupleSource.java:80)
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:138)
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:135)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:121)
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:230)
at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:118)
at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:288)
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: com.sybase.jdbc3.jdbc.SybSQLException: Execute cursor 'jconnect_implicit_3' is declared on a procedure which contains a non-SELECT or a SELECT with a COMPUTE clause. For the declaration of this cursor to be legal it should have a single SELECT statement without a COMPUTE clause.
at com.sybase.jdbc3.tds.Tds.a(Unknown Source)
I can use DBVisualizer and the same jConnect driver and run the exact same procedure with correct results.
--
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
[JBoss JIRA] (TEIID-2028) Previewing data from Designer getting mergeVDB NPE on server
by Paul Nittel (JIRA)
Paul Nittel created TEIID-2028:
----------------------------------
Summary: Previewing data from Designer getting mergeVDB NPE on server
Key: TEIID-2028
URL: https://issues.jboss.org/browse/TEIID-2028
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.7.1
Environment: SOA 5.3 ER2
Reporter: Paul Nittel
Assignee: Steven Hawkins
Running Deisnger I attempted to preview a table imported from JDBC. It failed and the attached was found in the server.log. Here's a sample:
2 [UndeclaredThrowableException]Failed to invoke method 'mergeVDBs' on component 'RuntimeEngineDeployer' with parameters [SimpleMetaType:java.lang.String:PREVIEW_fb30e436-f182-45c5-b65c-934d9547b389_ModelingJdbc_Books_DB2_for_Linux_UNIX_and_Windows, SimpleMetaType:int:1, SimpleMetaType:java.lang.String:PREVIEW_fb30e436-f182-45c5-b65c-934d9547b389_ModelingJdbc_project, SimpleMetaType:int:1].
3 [NullPointerException]
at org.teiid.client.util.ExceptionUtil.convertException(ExceptionUtil.java:72)
at org.teiid.jboss.deployers.RuntimeEngineDeployer$3.invoke(RuntimeEngineDeployer.java:400)
at $Proxy473.mergeVDBs(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
--
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
[JBoss JIRA] (TEIID-2103) Replace System VDB with DDL based metadata
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-2103:
-----------------------------------
Summary: Replace System VDB with DDL based metadata
Key: TEIID-2103
URL: https://issues.jboss.org/browse/TEIID-2103
Project: Teiid
Issue Type: Enhancement
Components: Embedded, Server
Affects Versions: 8.0
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
Fix For: 8.1
Currently System VDB is based on Designer based VDB which requires the vdb indexing logic to be present to load into system. Now that DDL based metadata facility is available, should consider removing the Designer based VDB over the DDL based. This has couple different advantages
1) Removes the dependency indexing logic to load
2) Embedded Teiid can also have System functionality (currently it does not)
3) Modifications to System metadata will be much easier
4) Teiid would be master copy that defines this, right now Designer has its own copy, Teiid has its own, keeping them in sync is proven to be hard based on recent JIRA
as a initial step the "getSchema" method could be utilized to convert the current System.vdb into DDL form.
--
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
[JBoss JIRA] (TEIID-2065) In the rhq-plugin.xml, the not-used attribute of c:option (deprecated) to be replaced with simple-property
by Van Halbert (JIRA)
Van Halbert created TEIID-2065:
----------------------------------
Summary: In the rhq-plugin.xml, the not-used attribute of c:option (deprecated) to be replaced with simple-property
Key: TEIID-2065
URL: https://issues.jboss.org/browse/TEIID-2065
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.7.1
Reporter: Van Halbert
Assignee: Steven Hawkins
Priority: Minor
These warnings need to be cleaned up in the rhq-plugin.xml. A deprecated attribute of c:option (deprecated) needs to be replaced with simple-property.
2011-09-30 17:46:54,514 WARN [ConfigurationMetadataParser] !!
For simple-property [status], attribute 'default' on c:option is useless and deprecated.
Please use the 'default' attribute on the c:simple-property.
The deprecated attribute will be removed in the future.
!!
2011-09-30 17:46:54,514 WARN [ConfigurationMetadataParser] !!
For simple-property [connectionType], attribute 'default' on c:option is useless and deprecated.
Please use the 'default' attribute on the c:simple-property.
The deprecated attribute will be removed in the future.
!!
2011-09-30 17:46:54,516 WARN [ConfigurationMetadataParser] !!
For simple-property [cacheType], attribute 'default' on c:option is useless and deprecated.
Please use the 'default' attribute on the c:simple-property.
The deprecated attribute will be removed in the future.
--
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