[JBoss JIRA] (TEIID-4651) SybaseIQ translator: different order of arguments in LOCATE function
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4651?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4651.
-----------------------------------
Fix Version/s: 9.1.2
Resolution: Done
Switched the order of the first two parameters. There is also a limitation documented that their locate function only support a search string of under 256 characters, which may be a later issue.
> SybaseIQ translator: different order of arguments in LOCATE function
> --------------------------------------------------------------------
>
> Key: TEIID-4651
> URL: https://issues.jboss.org/browse/TEIID-4651
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.12.8.6_3
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 9.1.2, 9.2
>
>
> Teiid's and SAP IQ's LOCATE function differs in order of arguments. Translator is pushing the LOCATE function as is into the source, which results in undesirable results. This is critical issue, as the queries seemingly work, but are not producing correct results.
> See [SAP IQ LOCATE function docs|http://help.sap.com/saphelp_iq1611_iqrefbb/helpdata/en/a5/5fae8484f2...]
> Query:
> {code:sql}
> SELECT INTKEY, STRINGNUM, LOCATE(1,STRINGNUM) FROM BQT1.SmallA ORDER BY intkey
> {code}
> being pushed as:
> {code:sql}
> [SELECT g_0."intkey" AS c_0, g_0."stringnum" AS c_1, locate('1', g_0."stringnum") AS c_2 FROM "bqt-server"."dvqe"."SmallA" AS g_0 ORDER BY c_0]
> {code}
> Results in:
> || intkey || stringnum || expr3 ||
> |0 | -24 | 0|
> |1 | <null> | <null>|
> |2 | -22 | 0|
> |3 | -21 | 0|
> |4 | -20 | 0|
> |5 | -19 | 0|
> |6 | -18 | 0|
> |7 | -17 | 0|
> |8 | -16 | 0|
> |9 | -15 | 0|
> |10 | -14 | 0|
> |11 | -13 | 0|
> |12 | -12 | 0|
> |13 | -11 | 0|
> |14 | -10 | 0|
> |15 | -9 | 0|
> |16 | -8 | 0|
> |17 | <null> | <null>|
> |18 | -6 | 0|
> |19 | -5 | 0|
> |20 | -4 | 0|
> |21 | -3 | 0|
> |22 | -2 | 0|
> |23 | -1 | 0|
> |24 | 0 | 0|
> |25 | 1 | 1|
> |26 | 2 | 0|
> |27 | 3 | 0|
> |28 | 4 | 0|
> |29 | 5 | 0|
> |30 | 6 | 0|
> |31 | 7 | 0|
> |32 | 8 | 0|
> |33 | <null> | <null>|
> |34 | 10 | 0|
> |35 | 11 | 0|
> |36 | 12 | 0|
> |37 | 13 | 0|
> |38 | 14 | 0|
> |39 | 15 | 0|
> |40 | 16 | 0|
> |41 | 17 | 0|
> |42 | 18 | 0|
> |43 | 19 | 0|
> |44 | 20 | 0|
> |45 | 21 | 0|
> |46 | 22 | 0|
> |47 | 23 | 0|
> |48 | 24 | 0|
> |49 | <null> | <null> |
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months
[JBoss JIRA] (TEIID-4650) SybaseIQ translator: week function can't be pushed directly
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4650?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4650.
-----------------------------------
Fix Version/s: 9.1.2
Resolution: Done
Fixed by using an escape function. This will be an issue though similar to TEIID-4652 as the escape is not supported by j-connect. Based upon these and the prepared statement issue though, it will likely be that we only recommend the usage of the sql anywhere driver.
> SybaseIQ translator: week function can't be pushed directly
> -----------------------------------------------------------
>
> Key: TEIID-4650
> URL: https://issues.jboss.org/browse/TEIID-4650
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.12.8.6_3
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Fix For: 9.1.2, 9.2
>
>
> SybaseIQ translator pushes WEEK function calls directly to SAP IQ. SAP IQ doesn't support such function. See [Date and Time Functions docs|http://help.sap.com/saphelp_iq1611_iqrefbb/helpdata/en/a5/2b07be84f2...]
> Query:
> {code:sql}
> SELECT WEEK(dateValue) FROM BQT1.SMALLA;
> {code}
> Pushed source query:
> {code:sql}
> [SELECT week(g_0."datevalue") FROM "bqt-server"."dvqe"."SmallA" AS g_0]
> {code}
> Error in logs:
> {code}
> 08:14:15,830 WARN [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue19) Connector worker process failed for atomic-request=PYp5BTTPF3pK.8.0.2: org.teiid.translator.jdbc.JDBCExecutionException: 504 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT week(g_0."datevalue") FROM "bqt-server"."dvqe"."SmallA" AS g_0]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) [translator-jdbc-8.12.8.6_3-redhat-1.jar:8.12.8.6_3-redhat-1]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:366)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_71]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_71]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_71]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_71]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
> at com.sun.proxy.$Proxy80.execute(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_71]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:280)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_71]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_71]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_71]
> Caused by: com.sybase.jdbc4.jdbc.SybSQLException: SQL Anywhere Error -265: Procedure 'week' not found
> at com.sybase.jdbc4.tds.Tds.a(Unknown Source)
> at com.sybase.jdbc4.tds.Tds.nextResult(Unknown Source)
> at com.sybase.jdbc4.tds.Tds.getResultSetResult(Unknown Source)
> at com.sybase.jdbc4.tds.TdsCursor.open(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybStatement.executeQuery(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybPreparedStatement.executeQuery(Unknown Source)
> at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:462)
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:123) [translator-jdbc-8.12.8.6_3-redhat-1.jar:8.12.8.6_3-redhat-1]
> ... 18 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months
[JBoss JIRA] (TEIID-4652) SybaseIQ translator: DAYOFYEAR function not pushed correctly
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4652?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4652:
---------------------------------------
See http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.... this JDBC escape is supposed to be supported - which driver were you using?
> SybaseIQ translator: DAYOFYEAR function not pushed correctly
> ------------------------------------------------------------
>
> Key: TEIID-4652
> URL: https://issues.jboss.org/browse/TEIID-4652
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.12.8.6_3
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Fix For: 9.2
>
>
> DAYOFYEAR function is being pushed into SAP IQ datasource causing an error. The function doesn't seem to be supported directly in SAP IQ according to [SAP IQ docs|http://help.sap.com/saphelp_iq1611_iqrefbb/helpdata/en/a5/2b07be84f2...]
> Query used:
> {code:sql}
> SELECT IntKey, datevalue, DAYOFYEAR(datevalue) AS DayFromDate FROM BQT1.SmallA ORDER BY IntKey
> {code}
> Source query pushed:
> {code:sql}
> [SELECT g_0."intkey" AS c_0, g_0."datevalue" AS c_1, {fn dayofyear(g_0."datevalue")} AS c_2 FROM "bqt-server"."dvqe"."SmallA" AS g_0 ORDER BY c_0]
> {code}
> Causing an error coming from SAP IQ:
> {code}
> 09:08:30,130 WARN [org.teiid.CONNECTOR] (Worker11_QueryProcessorQueue58) Connector worker process failed for atomic-request=PYp5BTTPF3pK.20.0.12: org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."intkey" AS c_0, g_0."datevalue" AS c_1, {fn dayofyear(g_0."datevalue")} AS c_2 FROM "bqt-server"."dvqe"."SmallA" AS g_0 ORDER BY c_0]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) [translator-jdbc-8.12.8.6_3-redhat-1.jar:8.12.8.6_3-redhat-1]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:366)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_71]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_71]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_71]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_71]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
> at com.sun.proxy.$Proxy80.execute(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_71]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:280)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_71]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_71]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_71]
> Caused by: java.sql.SQLException: JZ0SI: A static function escape dayofyear was used which is not supported by this server.
> at com.sybase.jdbc4.jdbc.ErrorMessage.raiseError(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybStatement.processEscapes(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybStatement.doEscapeProcessing(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybPreparedStatement.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.a(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.prepareStatement(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.prepareStatement(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.prepareStatement(Unknown Source)
> at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.doPrepareStatement(BaseWrapperManagedConnection.java:744)
> at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.prepareStatement(BaseWrapperManagedConnection.java:730)
> at org.jboss.jca.adapters.jdbc.WrappedConnection.prepareStatement(WrappedConnection.java:405)
> at org.teiid.translator.jdbc.JDBCBaseExecution.getPreparedStatement(JDBCBaseExecution.java:196) [translator-jdbc-8.12.8.6_3-redhat-1.jar:8.12.8.6_3-redhat-1]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:121) [translator-jdbc-8.12.8.6_3-redhat-1.jar:8.12.8.6_3-redhat-1]
> ... 18 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months
[JBoss JIRA] (TEIID-4662) jBPM workbench may give us some hints for a moderner web ui
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-4662?page=com.atlassian.jira.plugin... ]
Kylin Soong updated TEIID-4662:
-------------------------------
Description:
I have installed a jBPM and looked it roughly, found that the jbpm workbench looks more beautiful, especially there is a DataSet panels, almost do the same work of what Our designer do, as [1], current, RDBMS. excel/csv file, Elastic Search be support to import and mapping in web UI.
Also the UI more moderner than our Designer, I would attach some screenshot
[1] https://docs.jboss.org/jbpm/release/6.5.0.Final/jbpm-docs/html/ch09.html#...
was:
I have installed a jBPM and looked it roughly, found that the jbpm workbench looks beautify, especially there is a DataSet panels, almost do the same work of what Our designer do, as [1], current, RDBMS. excel/csv file, Elastic Search be support to import and mapping in web UI.
Also the UI more moderner than our Designer, I would attach some screenshot
[1] https://docs.jboss.org/jbpm/release/6.5.0.Final/jbpm-docs/html/ch09.html#...
> jBPM workbench may give us some hints for a moderner web ui
> -----------------------------------------------------------
>
> Key: TEIID-4662
> URL: https://issues.jboss.org/browse/TEIID-4662
> Project: Teiid
> Issue Type: Feature Request
> Reporter: Kylin Soong
> Assignee: Steven Hawkins
> Attachments: screen-1.png, screen-2.png, screen-3.png, screen-4.png
>
>
> I have installed a jBPM and looked it roughly, found that the jbpm workbench looks more beautiful, especially there is a DataSet panels, almost do the same work of what Our designer do, as [1], current, RDBMS. excel/csv file, Elastic Search be support to import and mapping in web UI.
> Also the UI more moderner than our Designer, I would attach some screenshot
> [1] https://docs.jboss.org/jbpm/release/6.5.0.Final/jbpm-docs/html/ch09.html#...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months
[JBoss JIRA] (TEIID-4630) Polish the teiid rest generated war
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-4630?page=com.atlassian.jira.plugin... ]
Kylin Soong commented on TEIID-4630:
------------------------------------
Add some change to api doc page as attached figure.
> Polish the teiid rest generated war
> ------------------------------------
>
> Key: TEIID-4630
> URL: https://issues.jboss.org/browse/TEIID-4630
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 9.2
> Reporter: Kylin Soong
> Assignee: Kylin Soong
> Fix For: 9.2
>
> Attachments: rest-screen.png
>
>
> I have 2 aspect thoughts to beautify the rest war login/doc page:
> * Change the login type from default BASIC to Client-Login, which like Dashbuilder, once request
> {note}
> http://{HOST}:{PORT}/{VDB_BANE}_{VDB_VERSION}/api
> {note}
> first will redirect to client login page, rather than pop up a small rough login window.
> * Add a top green bar and log(as discussed in TEIIDDES-3006) to api doc page
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months
[JBoss JIRA] (TEIID-4630) Polish the teiid rest generated war
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-4630?page=com.atlassian.jira.plugin... ]
Kylin Soong updated TEIID-4630:
-------------------------------
Attachment: rest-screen.png
> Polish the teiid rest generated war
> ------------------------------------
>
> Key: TEIID-4630
> URL: https://issues.jboss.org/browse/TEIID-4630
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 9.2
> Reporter: Kylin Soong
> Assignee: Kylin Soong
> Fix For: 9.2
>
> Attachments: rest-screen.png
>
>
> I have 2 aspect thoughts to beautify the rest war login/doc page:
> * Change the login type from default BASIC to Client-Login, which like Dashbuilder, once request
> {note}
> http://{HOST}:{PORT}/{VDB_BANE}_{VDB_VERSION}/api
> {note}
> first will redirect to client login page, rather than pop up a small rough login window.
> * Add a top green bar and log(as discussed in TEIIDDES-3006) to api doc page
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months
[JBoss JIRA] (TEIID-4648) MySQL unsigned type detection is incorrect
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4648?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4648.
-----------------------------------
Resolution: Done
Added a check for UNSIGNED in the type name as the driver lists all of the types as "x UNSIGNED".
> MySQL unsigned type detection is incorrect
> ------------------------------------------
>
> Key: TEIID-4648
> URL: https://issues.jboss.org/browse/TEIID-4648
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.1.2, 9.2
>
>
> The MySQL JDBC driver hard codes for all integral types in the DatabaseMetaData getTypeInfo call that they are unsigned - even the signed types. This causes our logic to widen types that don't need widened.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months
[JBoss JIRA] (TEIID-4663) Support a more secure block mode for client/server encryption
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4663?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4663.
-----------------------------------
Resolution: Done
Added another parameter to the handshake to control if cbc is used. This change is not version specific, so it can be added as a patch as desired to older branches.
> Support a more secure block mode for client/server encryption
> -------------------------------------------------------------
>
> Key: TEIID-4663
> URL: https://issues.jboss.org/browse/TEIID-4663
> Project: Teiid
> Issue Type: Quality Risk
> Components: JDBC Driver, Server
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.0.6, 9.1.2, 9.2
>
>
> ECB is the current default for the socket transport encryption of secure messages. While this is relatively ok for small messages as we also have a message key acting as a CTR counter to some of the blocks, it does not provide strong security - especially for large data volume scenarios, such as when using larger login payloads or the secure requests option. We should default instead to CBC with an explicit initialization vector.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months