[JBoss JIRA] (TEIID-3073) Tableau Connection Issues
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3073?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3073:
----------------------------------
Fix Version/s: 8.10
Putting into 8.10 to see if any progress can be made.
> Tableau Connection Issues
> -------------------------
>
> Key: TEIID-3073
> URL: https://issues.jboss.org/browse/TEIID-3073
> Project: Teiid
> Issue Type: Bug
> Components: ODBC, Server
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 8.10
>
> Attachments: server.log, server.log, tablue-wireshark.pcapng
>
>
> It has been reported that using Tableu with Teiid ODBC port show the following errors. These need to be investigated and fixed
> {code}
> This ODBC driver does not support important capabilities used by Tableau.
> This unsupported function is required for relative date filters: The date part named 'week' for the date function: DATETRUNC(date_part, date, [start_of_week])
> -----
> Tableau identified the following warnings for the ODBC data source named 'streamyx_sales (streamyx_sales.streamyx_sales) (TMJDV)':
> This aggregation is unsupported: Attribute
> This aggregation is unsupported: Std. Dev
> This aggregation is unsupported: Std. Dev (Pop.)
> This aggregation is unsupported: Trunc Week Number
> This aggregation is unsupported: Variance
> This aggregation is unsupported: Variance (Pop.)
> This function is unsupported: % with parameter types 'integer, integer'
> This function is unsupported: ABS(number) with parameter types 'float'
> This function is unsupported: ABS(number) with parameter types 'integer'
> This function is unsupported: ACOS(number) with parameter types 'float'
> This function is unsupported: ASCII(string) with parameter types 'string'
> This function is unsupported: ASIN(number) with parameter types 'float'
> This function is unsupported: ATAN(number) with parameter types 'float'
> This function is unsupported: ATAN2(y number, x number) with parameter types 'float, float'
> This function is unsupported: CHAR(integer) with parameter types 'float'
> This function is unsupported: CHAR(integer) with parameter types 'integer'
> This function is unsupported: COS(angle) with parameter types 'float'
> This function is unsupported: COT(angle) with parameter types 'float'
> This function is unsupported: DATEPART_DAYOFWEEK_INTERNAL with parameter types 'date'
> This function is unsupported: DATEPART_WEEK_INTERNAL with parameter types 'date'
> This function is unsupported: DATETIME with parameter types 'integer'
> This function is unsupported: DEGREES(number) with parameter types 'float'
> This function is unsupported: EXP(number) with parameter types 'float'
> This function is unsupported: LN with parameter types 'float'
> This function is unsupported: LN(number) with parameter types 'float'
> This function is unsupported: LOG with parameter types 'float'
> This function is unsupported: LOG(number, [base]) with parameter types 'float'
> This function is unsupported: PI()
> This function is unsupported: POWER with parameter types 'float, integer'
> This function is unsupported: POWER with parameter types 'integer, integer'
> This function is unsupported: POWER(number,power) with parameter types 'float, integer'
> This function is unsupported: POWER(number,power) with parameter types 'integer, integer'
> This function is unsupported: RADIANS(number) with parameter types 'float'
> This function is unsupported: ROUND(number, [decimals]) with parameter types 'float'
> This function is unsupported: ROUND(number, [decimals]) with parameter types 'float, integer'
> This function is unsupported: SIGN(number) with parameter types 'float'
> This function is unsupported: SIN(angle) with parameter types 'float'
> This function is unsupported: SPACE with parameter types 'float'
> This function is unsupported: SPACE(number) with parameter types 'integer'
> This function is unsupported: SQRT(number) with parameter types 'float'
> This function is unsupported: SQUARE with parameter types 'float'
> This function is unsupported: TAN(angle) with parameter types 'float'
> This function is unsupported: The date part named 'week' for the date function: DATEDIFF(date_part, start_date, end_date, [start_of_week])
> This function is unsupported: The date part named 'week' for the date function: DATEDIFF(date_part, start_date, end_date, [start_of_week])
> This function is unsupported: The date part named 'week' for the date function: DATENAME(date_part, date, [start_of_week])
> This function is unsupported: The date part named 'week' for the date function: DATENAME(date_part, date, [start_of_week])
> This function is unsupported: The date part named 'week' for the date function: DATEPART(date_part, date, [start_of_week])
> This function is unsupported: The date part named 'week' for the date function: DATEPART(date_part, date, [start_of_week])
> This function is unsupported: The date part named 'weekday' for the date function: DATENAME(date_part, date, [start_of_week])
> This function is unsupported: The date part named 'weekday' for the date function: DATENAME(date_part, date, [start_of_week])
> This function is unsupported: The date part named 'weekday' for the date function: DATEPART(date_part, date, [start_of_week])
> This function is unsupported: The date part named 'weekday' for the date function: DATEPART(date_part, date, [start_of_week])
> This is unsupported: SELECT ... INTO
> This is unsupported: Temporary tables
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 7 months
[JBoss JIRA] (TEIID-3134) Impala sorting Issue
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3134?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3134:
---------------------------------------
If you do not specify an explicit null ordering (such as your example query) and the system property org.teiid.pushdownDefaultNullOrder is not set or false, then you will get the default ordering of the source, which was determined previously to be nulls high. If org.teiid.pushdownDefaultNullOrder is set to true, then you should see the Teiid default null ordering which is nulls low.
If you specify an explicit null ordering in the user query "ORDER BY StringNum NULLS FIRST asc", then you should always expect to see that ordering.
> Impala sorting Issue
> --------------------
>
> Key: TEIID-3134
> URL: https://issues.jboss.org/browse/TEIID-3134
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.7.1
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Fix For: 8.7.1, 8.9
>
> Attachments: server.log
>
>
> String sorting of impala is inconsistent with our expectations:
> Impala sorting
> ---------------------------
> SELECT BQT1.SmallA.StringNum FROM BQT1.SmallA
> Results
> 1: -1
> 2: -10
> 3: -11
> 4: -12
> 5: -13
> 6: -14
> 7: -15
> 8: -16
> 9: -17
> 10: -18
> 11: -19
> 12: -2
> 13: -20
> 14: -21
> 15: -22
> 16: -24
> 17: -3
> 18: -4
> 19: -5
> 20: -6
> 21: -8
> 22: -9
> 23: 0
> 24: 1
> 25: 10
> 26: 11
> 27: 12
> 28: 13
> 29: 14
> 30: 15
> 31: 16
> 32: 17
> 33: 18
> 34: 19
> 35: 2
> 36: 20
> 37: 21
> 38: 22
> 39: 23
> 40: 24
> 41: 3
> 42: 4
> 43: 5
> 44: 6
> 45: 7
> 46: 8
> 47: null
> 48: null
> 49: null
> 50: null
> Expected
> ---------------------------
> While we expect sorting to be consistent with other sources:
> 1: 0
> 2: 1
> 3: -1
> 4: 10
> 5: -10
> 6: 11
> 7: -11
> 8: 12
> 9: -12
> 10: 13
> 11: -13
> 12: 14
> 13: -14
> 14: 15
> 15: -15
> 16: 16
> 17: -16
> 18: 17
> 19: -17
> 20: 18
> 21: -18
> 22: 19
> 23: -19
> 24: 2
> 25: -2
> 26: 20
> 27: -20
> 28: 21
> 29: -21
> 30: 22
> 31: -22
> 32: 23
> 33: 24
> 34: -24
> 35: 3
> 36: -3
> 37: 4
> 38: -4
> 39: 5
> 40: -5
> 41: 6
> 42: -6
> 43: 7
> 44: 8
> 45: -8
> 46: -9
> 47: null
> 48: null
> 49: null
> 50: null
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 7 months
[JBoss JIRA] (TEIID-3187) Error Casting TimeStamp to Date using Impala
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3187?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3187:
---------------------------------------
Yes you are correct, while the unit tests pass there is a higher level issue with the capabilities restriction. I'll address that with this issue.
> Error Casting TimeStamp to Date using Impala
> --------------------------------------------
>
> Key: TEIID-3187
> URL: https://issues.jboss.org/browse/TEIID-3187
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.7.1
> Reporter: Van Halbert
> Assignee: Steven Hawkins
>
> With ER3 getting [1] for the conversion of a timestamp to a Date:
> convert(Source.smalla.DATEVALUE, date) AS DateValue
> [1]
> org.teiid.jdbc.TeiidSQLException: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 Source: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT DISTINCT cast(g_0.DATEVALUE AS date) AS c_0 FROM smalla g_0 ORDER BY c_0]
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135)
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:71)
> at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:667)
> at org.teiid.jdbc.StatementImpl.access$100(StatementImpl.java:63)
> at org.teiid.jdbc.StatementImpl$2.onCompletion(StatementImpl.java:515)
> at org.teiid.client.util.ResultsFuture.done(ResultsFuture.java:135)
> at org.teiid.client.util.ResultsFuture.access$200(ResultsFuture.java:40)
> at org.teiid.client.util.ResultsFuture$1.receiveResults(ResultsFuture.java:79)
> at org.teiid.net.socket.SocketServerInstanceImpl.receivedMessage(SocketServerInstanceImpl.java:264)
> at org.teiid.net.socket.SocketServerInstanceImpl.read(SocketServerInstanceImpl.java:302)
> 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:606)
> at org.teiid.net.socket.SocketServerConnectionFactory$ShutdownHandler.invoke(SocketServerConnectionFactory.java:98)
> at com.sun.proxy.$Proxy1.read(Unknown Source)
> at org.teiid.net.socket.SocketServerInstanceImpl$RemoteInvocationHandler$1.get(SocketServerInstanceImpl.java:401)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:524)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:393)
> at org.teiid.jdbc.StatementImpl.executeQuery(StatementImpl.java:327)
> at JDBCClient.execute(JDBCClient.java:80)
> at JDBCClient.main(JDBCClient.java:46)
> Caused by: org.teiid.core.TeiidProcessingException: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 Source: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT DISTINCT cast(g_0.DATEVALUE AS date) AS c_0 FROM smalla g_0 ORDER BY c_0]
> at org.teiid.dqp.internal.process.DataTierTupleSource.exceptionOccurred(DataTierTupleSource.java:381)
> at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:154)
> at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:369)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278)
> at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:136)
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151)
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:159)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:141)
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:444)
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:326)
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51)
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:254)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274)
> 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)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.teiid.core.TeiidException: 0 Remote org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT DISTINCT cast(g_0.DATEVALUE AS date) AS c_0 FROM smalla g_0 ORDER BY c_0]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:325)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58)
> ... 6 more
> Caused by: java.sql.SQLException: Remote java.sql.SQLException: AnalysisException: Invalid type cast of g_0.DATEVALUE from TIMESTAMP to DATE
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 7 months
[JBoss JIRA] (TEIID-3134) Impala sorting Issue
by Filip Nguyen (JIRA)
[ https://issues.jboss.org/browse/TEIID-3134?page=com.atlassian.jira.plugin... ]
Filip Nguyen commented on TEIID-3134:
-------------------------------------
Steven, sorry but I am not sure what should I expect now. Initially my thinking was that the null ordering must be fixed so that [1] doesn't put the nulls at the end of the result set. With ER4 it still puts the null at the end of the result set. Is that expected?
[1] SELECT DISTINCT BQT1.SmallA.StringNum FROM BQT1.SmallA ORDER BY StringNum asc
> Impala sorting Issue
> --------------------
>
> Key: TEIID-3134
> URL: https://issues.jboss.org/browse/TEIID-3134
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.7.1
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Fix For: 8.7.1, 8.9
>
> Attachments: server.log
>
>
> String sorting of impala is inconsistent with our expectations:
> Impala sorting
> ---------------------------
> SELECT BQT1.SmallA.StringNum FROM BQT1.SmallA
> Results
> 1: -1
> 2: -10
> 3: -11
> 4: -12
> 5: -13
> 6: -14
> 7: -15
> 8: -16
> 9: -17
> 10: -18
> 11: -19
> 12: -2
> 13: -20
> 14: -21
> 15: -22
> 16: -24
> 17: -3
> 18: -4
> 19: -5
> 20: -6
> 21: -8
> 22: -9
> 23: 0
> 24: 1
> 25: 10
> 26: 11
> 27: 12
> 28: 13
> 29: 14
> 30: 15
> 31: 16
> 32: 17
> 33: 18
> 34: 19
> 35: 2
> 36: 20
> 37: 21
> 38: 22
> 39: 23
> 40: 24
> 41: 3
> 42: 4
> 43: 5
> 44: 6
> 45: 7
> 46: 8
> 47: null
> 48: null
> 49: null
> 50: null
> Expected
> ---------------------------
> While we expect sorting to be consistent with other sources:
> 1: 0
> 2: 1
> 3: -1
> 4: 10
> 5: -10
> 6: 11
> 7: -11
> 8: 12
> 9: -12
> 10: 13
> 11: -13
> 12: 14
> 13: -14
> 14: 15
> 15: -15
> 16: 16
> 17: -16
> 18: 17
> 19: -17
> 20: 18
> 21: -18
> 22: 19
> 23: -19
> 24: 2
> 25: -2
> 26: 20
> 27: -20
> 28: 21
> 29: -21
> 30: 22
> 31: -22
> 32: 23
> 33: 24
> 34: -24
> 35: 3
> 36: -3
> 37: 4
> 38: -4
> 39: 5
> 40: -5
> 41: 6
> 42: -6
> 43: 7
> 44: 8
> 45: -8
> 46: -9
> 47: null
> 48: null
> 49: null
> 50: null
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 7 months
[JBoss JIRA] (TEIID-3187) Error Casting TimeStamp to Date using Impala
by Filip Nguyen (JIRA)
[ https://issues.jboss.org/browse/TEIID-3187?page=com.atlassian.jira.plugin... ]
Filip Nguyen commented on TEIID-3187:
-------------------------------------
I double checked it and I think I am really using Impala translator
> Error Casting TimeStamp to Date using Impala
> --------------------------------------------
>
> Key: TEIID-3187
> URL: https://issues.jboss.org/browse/TEIID-3187
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.7.1
> Reporter: Van Halbert
> Assignee: Steven Hawkins
>
> With ER3 getting [1] for the conversion of a timestamp to a Date:
> convert(Source.smalla.DATEVALUE, date) AS DateValue
> [1]
> org.teiid.jdbc.TeiidSQLException: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 Source: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT DISTINCT cast(g_0.DATEVALUE AS date) AS c_0 FROM smalla g_0 ORDER BY c_0]
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135)
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:71)
> at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:667)
> at org.teiid.jdbc.StatementImpl.access$100(StatementImpl.java:63)
> at org.teiid.jdbc.StatementImpl$2.onCompletion(StatementImpl.java:515)
> at org.teiid.client.util.ResultsFuture.done(ResultsFuture.java:135)
> at org.teiid.client.util.ResultsFuture.access$200(ResultsFuture.java:40)
> at org.teiid.client.util.ResultsFuture$1.receiveResults(ResultsFuture.java:79)
> at org.teiid.net.socket.SocketServerInstanceImpl.receivedMessage(SocketServerInstanceImpl.java:264)
> at org.teiid.net.socket.SocketServerInstanceImpl.read(SocketServerInstanceImpl.java:302)
> 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:606)
> at org.teiid.net.socket.SocketServerConnectionFactory$ShutdownHandler.invoke(SocketServerConnectionFactory.java:98)
> at com.sun.proxy.$Proxy1.read(Unknown Source)
> at org.teiid.net.socket.SocketServerInstanceImpl$RemoteInvocationHandler$1.get(SocketServerInstanceImpl.java:401)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:524)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:393)
> at org.teiid.jdbc.StatementImpl.executeQuery(StatementImpl.java:327)
> at JDBCClient.execute(JDBCClient.java:80)
> at JDBCClient.main(JDBCClient.java:46)
> Caused by: org.teiid.core.TeiidProcessingException: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 Source: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT DISTINCT cast(g_0.DATEVALUE AS date) AS c_0 FROM smalla g_0 ORDER BY c_0]
> at org.teiid.dqp.internal.process.DataTierTupleSource.exceptionOccurred(DataTierTupleSource.java:381)
> at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:154)
> at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:369)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278)
> at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:136)
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151)
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:159)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:141)
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:444)
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:326)
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51)
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:254)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274)
> 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)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.teiid.core.TeiidException: 0 Remote org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT DISTINCT cast(g_0.DATEVALUE AS date) AS c_0 FROM smalla g_0 ORDER BY c_0]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:325)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58)
> ... 6 more
> Caused by: java.sql.SQLException: Remote java.sql.SQLException: AnalysisException: Invalid type cast of g_0.DATEVALUE from TIMESTAMP to DATE
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 7 months
[JBoss JIRA] (TEIID-3216) Implement INSERT, UPDATE and DELETE support for google-spreadsheet connector
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3216?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3216:
---------------------------------------
> For example: I have to update 3 rows. The first and the second row is updated. Update of the third row fails. What should I do now?
It depends on the update type. If it's a batched update then you will return an update count array. If it's a single update statement, then a single update count is expected.
> Implement INSERT, UPDATE and DELETE support for google-spreadsheet connector
> ----------------------------------------------------------------------------
>
> Key: TEIID-3216
> URL: https://issues.jboss.org/browse/TEIID-3216
> Project: Teiid
> Issue Type: Task
> Components: Misc. Connectors
> Reporter: Filip Elias
> Assignee: Filip Elias
> Fix For: Open To Community
>
>
> Current plan is to use list-based feed of the Google Data API[1].
> There are three known issues:
> performance - to delete/update 100 rows Teiid must generate 100 http requests
> consistency - user wants to update 50 rows. After the 10th row is updated the connection could fail which would cause that 10 rows would be updated and 40 wouldn't.
> headers - update, delete and and insert statements will be supported only for the spreadsheets that have a header for each column (headers are in the first row of a spreadsheet)
> Select statement is implemented using Google Visualisation API, but this API doesn't support updates and doesn't return row numbers.
> [1] https://developers.google.com/google-apps/spreadsheets/
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 7 months
[JBoss JIRA] (TEIID-3216) Implement INSERT, UPDATE and DELETE support for google-spreadsheet connector
by Filip Elias (JIRA)
[ https://issues.jboss.org/browse/TEIID-3216?page=com.atlassian.jira.plugin... ]
Filip Elias commented on TEIID-3216:
------------------------------------
Hello Steven,
I am not sure whether I got your point.
For example: I have to update 3 rows. The first and the second row is updated. Update of the third row fails. What should I do now?
If I put into the update count array [1,1,-3] then the Squirrel will print: 1 row has been updated. Is this expected?
If I put into the update count array [2] then the Squirrel will print: 2 rows have been updated. It seems that only the first index of the array is relevant.
> Implement INSERT, UPDATE and DELETE support for google-spreadsheet connector
> ----------------------------------------------------------------------------
>
> Key: TEIID-3216
> URL: https://issues.jboss.org/browse/TEIID-3216
> Project: Teiid
> Issue Type: Task
> Components: Misc. Connectors
> Reporter: Filip Elias
> Assignee: Filip Elias
> Fix For: Open To Community
>
>
> Current plan is to use list-based feed of the Google Data API[1].
> There are three known issues:
> performance - to delete/update 100 rows Teiid must generate 100 http requests
> consistency - user wants to update 50 rows. After the 10th row is updated the connection could fail which would cause that 10 rows would be updated and 40 wouldn't.
> headers - update, delete and and insert statements will be supported only for the spreadsheets that have a header for each column (headers are in the first row of a spreadsheet)
> Select statement is implemented using Google Visualisation API, but this API doesn't support updates and doesn't return row numbers.
> [1] https://developers.google.com/google-apps/spreadsheets/
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 7 months
[JBoss JIRA] (TEIID-3234) better detail messages related to caching
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3234:
-------------------------------------
Summary: better detail messages related to caching
Key: TEIID-3234
URL: https://issues.jboss.org/browse/TEIID-3234
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.10
Some caching messages cover multiple cases. It would make diagnosis easier to have them separated.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 7 months