[JBoss JIRA] (TEIID-5384) CHAR_LENGTH function
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5384?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5384.
-----------------------------------
Resolution: Done
Updated the grammar and docs to support this syntax. It maps in the parser or the rewriter to existing sql support.
> CHAR_LENGTH function
> --------------------
>
> Key: TEIID-5384
> URL: https://issues.jboss.org/browse/TEIID-5384
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Lukáš Svačina
> Assignee: Steven Hawkins
> Fix For: 11.0
>
>
> Should work same as LENGTH function.
> Use case: universal query builder from JOOQ uses CHAR_LENGTH function (probably ANSI compatible one?)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (TEIID-5385) POSITION function
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5385?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5385.
-----------------------------------
Resolution: Done
Updated the grammar and docs to support this syntax. It maps in the parser or the rewriter to existing sql support.
> POSITION function
> -----------------
>
> Key: TEIID-5385
> URL: https://issues.jboss.org/browse/TEIID-5385
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Lukáš Svačina
> Assignee: Steven Hawkins
> Fix For: 11.0
>
>
> syntax should work as: POSITION(something in something)
> Use case: universal query builder from JOOQ uses POSITION function (probably ANSI compatible one?)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (TEIID-5383) CURRENT_DATE without parens doesn't work
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5383?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5383.
-----------------------------------
Resolution: Done
Updated the grammar and docs to support this syntax. It maps in the parser or the rewriter to existing sql support.
> CURRENT_DATE without parens doesn't work
> ----------------------------------------
>
> Key: TEIID-5383
> URL: https://issues.jboss.org/browse/TEIID-5383
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Lukáš Svačina
> Assignee: Steven Hawkins
> Priority: Minor
> Fix For: 11.0
>
>
> CURRENT_DATE don't work (parse exception)
> CURDATE() versions work well
> Use case: universal query builder from JOOQ uses CURRENT_DATE function name format (probably ANSI compatible one?)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (TEIID-5387) Procedure import from SAP IQ doesn't work
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5387?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5387:
----------------------------------
Priority: Major (was: Critical)
Generally there isn't an expectation that procedure import will work against all sources as we haven't see universal support. This is an issue internal to the driver, similar to http://stackoverflow.com/questions/30632084/how-do-i-execute-preparedstat...
Are there other driver versions you can test?
> Procedure import from SAP IQ doesn't work
> -----------------------------------------
>
> Key: TEIID-5387
> URL: https://issues.jboss.org/browse/TEIID-5387
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.12.13.6_4
> Reporter: Jan Martiska
> Assignee: Steven Hawkins
>
> If I try to import any procedure (using native metadata repository) stored in SAP IQ database, I get this exception during import:
> {noformat}
> [mppr] 10:34:33,664 WARN [org.teiid.RUNTIME] (teiid-async-threads - 4) TEIID50036 VDB teiid5180.1 model "teiid5180" metadata failed to load. Reason:TEIID11010 java.sql.SQLException: JZ0SA: Prepared Statement: Input parameter not set, index: 4.: org.teiid.translator.TranslatorException: TEIID11010 java.sql.SQLException: JZ0SA: Prepared Statement: Input parameter not set, index: 4.
> [mppr] at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:302)
> [mppr] at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:70)
> [mppr] at org.teiid.query.metadata.NativeMetadataRepository.getMetadata(NativeMetadataRepository.java:96) [teiid-engine-8.12.14.6_4-redhat-64-2.jar:8.12.14.6_4-redhat-64-2]
> [mppr] at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:62) [teiid-engine-8.12.14.6_4-redhat-64-2.jar:8.12.14.6_4-redhat-64-2]
> [mppr] at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) [teiid-engine-8.12.14.6_4-redhat-64-2.jar:8.12.14.6_4-redhat-64-2]
> [mppr] at org.teiid.jboss.VDBService$6.run(VDBService.java:395) [teiid-jboss-integration-8.12.14.6_4-redhat-64-2.jar:8.12.14.6_4-redhat-64-2]
> [mppr] at org.teiid.jboss.VDBService$7.run(VDBService.java:446) [teiid-jboss-integration-8.12.14.6_4-redhat-64-2.jar:8.12.14.6_4-redhat-64-2]
> [mppr] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_151]
> [mppr] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_151]
> [mppr] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_151]
> [mppr] at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> [mppr] Caused by: java.sql.SQLException: JZ0SA: Prepared Statement: Input parameter not set, index: 4.
> [mppr] at com.sybase.jdbc4.jdbc.SybConnection.getAllExceptions(SybConnection.java:2780)
> [mppr] at com.sybase.jdbc4.jdbc.SybStatement.handleSQLE(SybStatement.java:2665)
> [mppr] at com.sybase.jdbc4.jdbc.SybCallableStatement.sendRpc(SybCallableStatement.java:1716)
> [mppr] at com.sybase.jdbc4.jdbc.SybCallableStatement.executeQuery(SybCallableStatement.java:145)
> [mppr] at com.sybase.jdbc4.jdbc.SybDatabaseMetaData.returnResults(SybDatabaseMetaData.java:4286)
> [mppr] at com.sybase.jdbc4.jdbc.SybDatabaseMetaData.getProcedureColumns(SybDatabaseMetaData.java:2912)
> [mppr] at org.teiid.translator.jdbc.JDBCMetdataProcessor.getProcedures(JDBCMetdataProcessor.java:234)
> [mppr] at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:194)
> [mppr] at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:300)
> [mppr] ... 10 more
> [mppr]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (TEIID-5387) Procedure import from SAP IQ doesn't work
by Jan Martiska (JIRA)
[ https://issues.jboss.org/browse/TEIID-5387?page=com.atlassian.jira.plugin... ]
Jan Martiska updated TEIID-5387:
--------------------------------
Description:
If I try to import any procedure (using native metadata repository) stored in SAP IQ database, I get this exception during import:
{noformat}
[mppr] 10:34:33,664 WARN [org.teiid.RUNTIME] (teiid-async-threads - 4) TEIID50036 VDB teiid5180.1 model "teiid5180" metadata failed to load. Reason:TEIID11010 java.sql.SQLException: JZ0SA: Prepared Statement: Input parameter not set, index: 4.: org.teiid.translator.TranslatorException: TEIID11010 java.sql.SQLException: JZ0SA: Prepared Statement: Input parameter not set, index: 4.
[mppr] at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:302)
[mppr] at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:70)
[mppr] at org.teiid.query.metadata.NativeMetadataRepository.getMetadata(NativeMetadataRepository.java:96) [teiid-engine-8.12.14.6_4-redhat-64-2.jar:8.12.14.6_4-redhat-64-2]
[mppr] at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:62) [teiid-engine-8.12.14.6_4-redhat-64-2.jar:8.12.14.6_4-redhat-64-2]
[mppr] at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) [teiid-engine-8.12.14.6_4-redhat-64-2.jar:8.12.14.6_4-redhat-64-2]
[mppr] at org.teiid.jboss.VDBService$6.run(VDBService.java:395) [teiid-jboss-integration-8.12.14.6_4-redhat-64-2.jar:8.12.14.6_4-redhat-64-2]
[mppr] at org.teiid.jboss.VDBService$7.run(VDBService.java:446) [teiid-jboss-integration-8.12.14.6_4-redhat-64-2.jar:8.12.14.6_4-redhat-64-2]
[mppr] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_151]
[mppr] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_151]
[mppr] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_151]
[mppr] at org.jboss.threads.JBossThread.run(JBossThread.java:122)
[mppr] Caused by: java.sql.SQLException: JZ0SA: Prepared Statement: Input parameter not set, index: 4.
[mppr] at com.sybase.jdbc4.jdbc.SybConnection.getAllExceptions(SybConnection.java:2780)
[mppr] at com.sybase.jdbc4.jdbc.SybStatement.handleSQLE(SybStatement.java:2665)
[mppr] at com.sybase.jdbc4.jdbc.SybCallableStatement.sendRpc(SybCallableStatement.java:1716)
[mppr] at com.sybase.jdbc4.jdbc.SybCallableStatement.executeQuery(SybCallableStatement.java:145)
[mppr] at com.sybase.jdbc4.jdbc.SybDatabaseMetaData.returnResults(SybDatabaseMetaData.java:4286)
[mppr] at com.sybase.jdbc4.jdbc.SybDatabaseMetaData.getProcedureColumns(SybDatabaseMetaData.java:2912)
[mppr] at org.teiid.translator.jdbc.JDBCMetdataProcessor.getProcedures(JDBCMetdataProcessor.java:234)
[mppr] at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:194)
[mppr] at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:300)
[mppr] ... 10 more
[mppr]
{noformat}
was:
If I try to import any procedure (using native metadata repository) stored in SAP IQ database, I get this exception:
{noformat}
[mppr] 10:34:33,664 WARN [org.teiid.RUNTIME] (teiid-async-threads - 4) TEIID50036 VDB teiid5180.1 model "teiid5180" metadata failed to load. Reason:TEIID11010 java.sql.SQLException: JZ0SA: Prepared Statement: Input parameter not set, index: 4.: org.teiid.translator.TranslatorException: TEIID11010 java.sql.SQLException: JZ0SA: Prepared Statement: Input parameter not set, index: 4.
[mppr] at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:302)
[mppr] at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:70)
[mppr] at org.teiid.query.metadata.NativeMetadataRepository.getMetadata(NativeMetadataRepository.java:96) [teiid-engine-8.12.14.6_4-redhat-64-2.jar:8.12.14.6_4-redhat-64-2]
[mppr] at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:62) [teiid-engine-8.12.14.6_4-redhat-64-2.jar:8.12.14.6_4-redhat-64-2]
[mppr] at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) [teiid-engine-8.12.14.6_4-redhat-64-2.jar:8.12.14.6_4-redhat-64-2]
[mppr] at org.teiid.jboss.VDBService$6.run(VDBService.java:395) [teiid-jboss-integration-8.12.14.6_4-redhat-64-2.jar:8.12.14.6_4-redhat-64-2]
[mppr] at org.teiid.jboss.VDBService$7.run(VDBService.java:446) [teiid-jboss-integration-8.12.14.6_4-redhat-64-2.jar:8.12.14.6_4-redhat-64-2]
[mppr] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_151]
[mppr] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_151]
[mppr] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_151]
[mppr] at org.jboss.threads.JBossThread.run(JBossThread.java:122)
[mppr] Caused by: java.sql.SQLException: JZ0SA: Prepared Statement: Input parameter not set, index: 4.
[mppr] at com.sybase.jdbc4.jdbc.SybConnection.getAllExceptions(SybConnection.java:2780)
[mppr] at com.sybase.jdbc4.jdbc.SybStatement.handleSQLE(SybStatement.java:2665)
[mppr] at com.sybase.jdbc4.jdbc.SybCallableStatement.sendRpc(SybCallableStatement.java:1716)
[mppr] at com.sybase.jdbc4.jdbc.SybCallableStatement.executeQuery(SybCallableStatement.java:145)
[mppr] at com.sybase.jdbc4.jdbc.SybDatabaseMetaData.returnResults(SybDatabaseMetaData.java:4286)
[mppr] at com.sybase.jdbc4.jdbc.SybDatabaseMetaData.getProcedureColumns(SybDatabaseMetaData.java:2912)
[mppr] at org.teiid.translator.jdbc.JDBCMetdataProcessor.getProcedures(JDBCMetdataProcessor.java:234)
[mppr] at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:194)
[mppr] at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:300)
[mppr] ... 10 more
[mppr]
{noformat}
> Procedure import from SAP IQ doesn't work
> -----------------------------------------
>
> Key: TEIID-5387
> URL: https://issues.jboss.org/browse/TEIID-5387
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.12.13.6_4
> Reporter: Jan Martiska
> Assignee: Steven Hawkins
> Priority: Critical
>
> If I try to import any procedure (using native metadata repository) stored in SAP IQ database, I get this exception during import:
> {noformat}
> [mppr] 10:34:33,664 WARN [org.teiid.RUNTIME] (teiid-async-threads - 4) TEIID50036 VDB teiid5180.1 model "teiid5180" metadata failed to load. Reason:TEIID11010 java.sql.SQLException: JZ0SA: Prepared Statement: Input parameter not set, index: 4.: org.teiid.translator.TranslatorException: TEIID11010 java.sql.SQLException: JZ0SA: Prepared Statement: Input parameter not set, index: 4.
> [mppr] at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:302)
> [mppr] at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:70)
> [mppr] at org.teiid.query.metadata.NativeMetadataRepository.getMetadata(NativeMetadataRepository.java:96) [teiid-engine-8.12.14.6_4-redhat-64-2.jar:8.12.14.6_4-redhat-64-2]
> [mppr] at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:62) [teiid-engine-8.12.14.6_4-redhat-64-2.jar:8.12.14.6_4-redhat-64-2]
> [mppr] at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) [teiid-engine-8.12.14.6_4-redhat-64-2.jar:8.12.14.6_4-redhat-64-2]
> [mppr] at org.teiid.jboss.VDBService$6.run(VDBService.java:395) [teiid-jboss-integration-8.12.14.6_4-redhat-64-2.jar:8.12.14.6_4-redhat-64-2]
> [mppr] at org.teiid.jboss.VDBService$7.run(VDBService.java:446) [teiid-jboss-integration-8.12.14.6_4-redhat-64-2.jar:8.12.14.6_4-redhat-64-2]
> [mppr] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_151]
> [mppr] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_151]
> [mppr] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_151]
> [mppr] at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> [mppr] Caused by: java.sql.SQLException: JZ0SA: Prepared Statement: Input parameter not set, index: 4.
> [mppr] at com.sybase.jdbc4.jdbc.SybConnection.getAllExceptions(SybConnection.java:2780)
> [mppr] at com.sybase.jdbc4.jdbc.SybStatement.handleSQLE(SybStatement.java:2665)
> [mppr] at com.sybase.jdbc4.jdbc.SybCallableStatement.sendRpc(SybCallableStatement.java:1716)
> [mppr] at com.sybase.jdbc4.jdbc.SybCallableStatement.executeQuery(SybCallableStatement.java:145)
> [mppr] at com.sybase.jdbc4.jdbc.SybDatabaseMetaData.returnResults(SybDatabaseMetaData.java:4286)
> [mppr] at com.sybase.jdbc4.jdbc.SybDatabaseMetaData.getProcedureColumns(SybDatabaseMetaData.java:2912)
> [mppr] at org.teiid.translator.jdbc.JDBCMetdataProcessor.getProcedures(JDBCMetdataProcessor.java:234)
> [mppr] at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:194)
> [mppr] at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:300)
> [mppr] ... 10 more
> [mppr]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (TEIID-5387) Procedure import from SAP IQ doesn't work
by Jan Martiska (JIRA)
Jan Martiska created TEIID-5387:
-----------------------------------
Summary: Procedure import from SAP IQ doesn't work
Key: TEIID-5387
URL: https://issues.jboss.org/browse/TEIID-5387
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.12.13.6_4
Reporter: Jan Martiska
Assignee: Steven Hawkins
Priority: Critical
If I try to import any procedure (using native metadata repository) stored in SAP IQ database, I get this exception:
{noformat}
[mppr] 10:34:33,664 WARN [org.teiid.RUNTIME] (teiid-async-threads - 4) TEIID50036 VDB teiid5180.1 model "teiid5180" metadata failed to load. Reason:TEIID11010 java.sql.SQLException: JZ0SA: Prepared Statement: Input parameter not set, index: 4.: org.teiid.translator.TranslatorException: TEIID11010 java.sql.SQLException: JZ0SA: Prepared Statement: Input parameter not set, index: 4.
[mppr] at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:302)
[mppr] at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:70)
[mppr] at org.teiid.query.metadata.NativeMetadataRepository.getMetadata(NativeMetadataRepository.java:96) [teiid-engine-8.12.14.6_4-redhat-64-2.jar:8.12.14.6_4-redhat-64-2]
[mppr] at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:62) [teiid-engine-8.12.14.6_4-redhat-64-2.jar:8.12.14.6_4-redhat-64-2]
[mppr] at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) [teiid-engine-8.12.14.6_4-redhat-64-2.jar:8.12.14.6_4-redhat-64-2]
[mppr] at org.teiid.jboss.VDBService$6.run(VDBService.java:395) [teiid-jboss-integration-8.12.14.6_4-redhat-64-2.jar:8.12.14.6_4-redhat-64-2]
[mppr] at org.teiid.jboss.VDBService$7.run(VDBService.java:446) [teiid-jboss-integration-8.12.14.6_4-redhat-64-2.jar:8.12.14.6_4-redhat-64-2]
[mppr] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_151]
[mppr] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_151]
[mppr] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_151]
[mppr] at org.jboss.threads.JBossThread.run(JBossThread.java:122)
[mppr] Caused by: java.sql.SQLException: JZ0SA: Prepared Statement: Input parameter not set, index: 4.
[mppr] at com.sybase.jdbc4.jdbc.SybConnection.getAllExceptions(SybConnection.java:2780)
[mppr] at com.sybase.jdbc4.jdbc.SybStatement.handleSQLE(SybStatement.java:2665)
[mppr] at com.sybase.jdbc4.jdbc.SybCallableStatement.sendRpc(SybCallableStatement.java:1716)
[mppr] at com.sybase.jdbc4.jdbc.SybCallableStatement.executeQuery(SybCallableStatement.java:145)
[mppr] at com.sybase.jdbc4.jdbc.SybDatabaseMetaData.returnResults(SybDatabaseMetaData.java:4286)
[mppr] at com.sybase.jdbc4.jdbc.SybDatabaseMetaData.getProcedureColumns(SybDatabaseMetaData.java:2912)
[mppr] at org.teiid.translator.jdbc.JDBCMetdataProcessor.getProcedures(JDBCMetdataProcessor.java:234)
[mppr] at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:194)
[mppr] at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:300)
[mppr] ... 10 more
[mppr]
{noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (TEIID-5386) Wrong procedure import from MS SQL Server
by Jan Martiska (JIRA)
Jan Martiska created TEIID-5386:
-----------------------------------
Summary: Wrong procedure import from MS SQL Server
Key: TEIID-5386
URL: https://issues.jboss.org/browse/TEIID-5386
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.12.13.6_4
Reporter: Jan Martiska
Assignee: Steven Hawkins
When using automatic procedure import from SQL Server (I used 2016) with a model like this:
{noformat}
<model name="mymodel">
<property name="importer.useFullSchemaName" value="false"/>
<property name="importer.UseQualifiedName" value="false" />
<property name="importer.procedureNamePattern" value="echo%"/>
<property name="importer.importProcedures" value="true" />
<source connection-jndi-name="java:/mssql2016"
name="mySource" translator-name="sqlserver" />
</model>
{noformat}
There is a procedure named {{echo}} in SQL server. It is imported into the VDB as {{"mymodel"."echo;1"}} (not sure why the ;1). When I afterwards try to execute it using
{noformat}
EXEC "mymodel"."echo;1"();
{noformat}, I will get this exception from SQL server which suggests that Teiid mapped the procedure to the wrong name in the source database:
{noformat}
com.microsoft.sqlserver.jdbc.SQLServerException: Could not find stored procedure 'echo;1'.
{noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (TEIID-5372) Enhance docker support
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5372?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5372:
---------------------------------------
> we have "thorntail-teiid-examples" but not yet "openshift-teiid-examples"
I'm ok with having both Thorntail and OpenShift examples as needed.
> we need a way to showcase how we can take the same example and deploy standalone and OpenShift
Yes, we can create a subtask to convert all of the old embedded examples to either Thorntail or full OpenShift.
> What else can we think of improvements here?
Per some other discussions, perhaps a static build time validation when the metadata is fully specified.
Define how other artifacts make it into the archive - just a maven assembly?
> Enhance docker support
> ----------------------
>
> Key: TEIID-5372
> URL: https://issues.jboss.org/browse/TEIID-5372
> Project: Teiid
> Issue Type: Enhancement
> Reporter: Rafal Korytkowski
> Assignee: Rafal Korytkowski
> Priority: Optional
>
> Currently there's limited support for docker in Teiid, which can be enabled by adding -Ddocker=true to the build command. The generated image is based on CentOS and running standalone on the Wildfly server. Latest builds are pushed to https://hub.docker.com/r/jboss/teiid/, but versions are not tagged automatically with releases. Development with Docker is not supported.
> Proposed changes:
> 1. Produce docker image based on Alpine, which is better suited for microservices, in addition to CentOS.
> 2. Automatically tag versions in Docker when doing releases.
> 3. Support development by providing a docker-compose file with the possibility to start server in a debug mode and enabled auto-redeployment of code changes.
> 4. Optionally provide a Docker image for building code using maven in Docker. Having Docker as the only prerequisite is convenient for CI environments and makes the build environment agnostic.
> [~shawkins], [~rareddy], thoughts?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months