January 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3764) HBase - Phoenix driver does not support UNION

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3764?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3764. --------------------------------- > HBase - Phoenix driver does not support UNION > --------------------------------------------- > > Key: TEIID-3764 > URL: https://issues.jboss.org/browse/TEIID-3764 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1.6_2 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.12.1, 8.13 > > > Phoenix JDBC driver does not support UNION statement, only UNION ALL. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3752) Remove the assignToModel admin method

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3752?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3752. --------------------------------- > Remove the assignToModel admin method > ------------------------------------- > > Key: TEIID-3752 > URL: https://issues.jboss.org/browse/TEIID-3752 > Project: Teiid > Issue Type: Quality Risk > Components: AdminApi > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > TEIID-2527 deprecated assignToModel, it should not be removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3770) HBase - table's alias (... AS ...) is not "visible" in SELECT caluse in IN predicate

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3770?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3770. --------------------------------- > HBase - table's alias (... AS ...) is not "visible" in SELECT caluse in IN predicate > ------------------------------------------------------------------------------------ > > Key: TEIID-3770 > URL: https://issues.jboss.org/browse/TEIID-3770 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1.6_2 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.12.1, 8.13 > > > Query: > SELECT INTKEY, BIGDECIMALVALUE FROM BQT1.SMALLA AS A WHERE BIGDECIMALVALUE *IN (SELECT MAX(BIGDECIMALVALUE) FROM BQT1.SMALLA AS B WHERE _A_.INTKEY = B.INTKEY)* ORDER BY INTKEY > It seems like bug in Phoenix driver. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3785) PostgreSQL - Large Objects may not be used in auto-commit mode.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3785?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3785. --------------------------------- > PostgreSQL - Large Objects may not be used in auto-commit mode. > --------------------------------------------------------------- > > Key: TEIID-3785 > URL: https://issues.jboss.org/browse/TEIID-3785 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.11.3, 8.11.5 > Reporter: Tom Arnold > Assignee: Steven Hawkins > Fix For: 8.12.1, 8.13 > > Attachments: cola_markets.sql, cola_mkt.gif, Spatial-vdb.xml > > > Using Teiid 8.11.5 with PostgreSQL 9.4 and PostGIS. Doing a simple query with a spatial filter causes this stacktrace in the log. > {code} > select mkt_id from cola_markets where st_intersects(shape, st_geomfromtext('point(9 8)')); > {code} > {code} > 20:29:06,694 WARN [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue72) uL81ZQ6FDlJL Connector worker process failed for atomic-request=uL81ZQ6FDlJL.22.0.8: org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: ['javax.sql.rowset.serial.SerialBlob@223261cf'] SQL: SELECT g_0."mkt_id" FROM "public"."cola_markets" AS g_0 WHERE st_intersects(g_0."shape", st_geomfromwkb(?, 0)) = TRUE] > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) [translator-jdbc-8.11.5.jar:8.11.5] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:341) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_79] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_79] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_79] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_79] > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) > at com.sun.proxy.$Proxy46.execute(Unknown Source) > 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) [rt.jar:1.7.0_79] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) > 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_79] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_79] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79] > Caused by: org.postgresql.util.PSQLException: Large Objects may not be used in auto-commit mode. > at org.postgresql.largeobject.LargeObjectManager.createLO(LargeObjectManager.java:239) > at org.postgresql.largeobject.LargeObjectManager.createLO(LargeObjectManager.java:226) > at org.postgresql.jdbc2.AbstractJdbc2Statement.setBlob(AbstractJdbc2Statement.java:3048) > at org.postgresql.jdbc2.AbstractJdbc2Statement.setObject(AbstractJdbc2Statement.java:1836) > at org.postgresql.jdbc3.AbstractJdbc3Statement.setObject(AbstractJdbc3Statement.java:1481) > at org.postgresql.jdbc3g.AbstractJdbc3gStatement.setObject(AbstractJdbc3gStatement.java:46) > at org.postgresql.jdbc4.AbstractJdbc4Statement.setObject(AbstractJdbc4Statement.java:70) > at org.postgresql.jdbc2.AbstractJdbc2Statement.setObject(AbstractJdbc2Statement.java:1868) > at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.setObject(WrappedPreparedStatement.java:957) > at org.teiid.translator.jdbc.JDBCExecutionFactory.bindValue(JDBCExecutionFactory.java:936) [translator-jdbc-8.11.5.jar:8.11.5] > at org.teiid.translator.jdbc.JDBCBaseExecution.bind(JDBCBaseExecution.java:107) [translator-jdbc-8.11.5.jar:8.11.5] > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:122) [translator-jdbc-8.11.5.jar:8.11.5] > ... 18 more > 20:29:06,720 WARN [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue73) uL81ZQ6FDlJL TEIID30020 Processing exception for request uL81ZQ6FDlJL.22 'TEIID30504 postgres: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: ['javax.sql.rowset.serial.SerialBlob@223261cf'] SQL: SELECT g_0."mkt_id" FROM "public"."cola_markets" AS g_0 WHERE st_intersects(g_0."shape", st_geomfromwkb(?, 0)) = TRUE]'. Originally TeiidProcessingException 'Large Objects may not be used in auto-commit mode.' LargeObjectManager.java:239. Enable more detailed logging to see the entire stacktrace. > {code} > It looks like the issue is binding the WKB blob. Overriding the PostgreSQL translator and setting {{useStreamsForLobs()}} to {{true}} seems to fix the issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3937) Multiplying two columns in CASE statement overrides pushdown (Impala)

by Don Krapohl (JIRA)

[ https://issues.jboss.org/browse/TEIID-3937?page=com.atlassian.jira.plugin... ] Don Krapohl commented on TEIID-3937: ------------------------------------ Added detail. Summary: Impala translator Can cast all to double and output as double and the formula pushes down. If output is DECIMAL or BIGDECIMAL doesn't matter whether you cast or not, it doesn't send it down. Our example has two BIGDECIMAL and one BIGINT source columns. > Multiplying two columns in CASE statement overrides pushdown (Impala) > --------------------------------------------------------------------- > > Key: TEIID-3937 > URL: https://issues.jboss.org/browse/TEIID-3937 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.12.4 > Environment: Ubuntu Trusty > Reporter: Don Krapohl > Assignee: Steven Hawkins > > In the Impala translator, pushdown doesn't happen when two columns are multiplied in the THEN portion of a CASE statement with bigdecimal data type. > //this should push down but does not > CASE WHEN column1 IS NOT NULL > THEN column1 * column2 > ELSE column3 END > //but you can multiply the columns by a constant and it will push down > CASE WHEN column1 IS NOT NULL > THEN column1 * 34567 > ELSE column3 END > //or > CASE WHEN column1 IS NOT NULL > THEN 34567 * column2 > ELSE column3 END > //or casting to consistent datatypes with BIGDECIMAL output > CASE WHEN column1 IS NOT NULL > THEN cast(column1 as BIGDECIMAL ) * cast(column2 as BIGDECIMAL ) > ELSE cast(column3 as BIGDECIMAL ) END > //BUT output it as double with the cast statement above changed and it does push down (so floating point works) > CASE WHEN column1 IS NOT NULL > THEN cast(column1 as double ) * cast(column2 as double) > ELSE cast(column3 as double) END > Source data types: > Column1 is BIGDECIMAL > Column2 is BIGINT/LONG > Column3 is BIGDECIMAL > Output column is BIGDECIMAL -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3937) Multiplying two columns in CASE statement overrides pushdown (Impala)

by Don Krapohl (JIRA)

[ https://issues.jboss.org/browse/TEIID-3937?page=com.atlassian.jira.plugin... ] Don Krapohl updated TEIID-3937: ------------------------------- Description: In the Impala translator, pushdown doesn't happen when two columns are multiplied in the THEN portion of a CASE statement with bigdecimal data type. //this should push down but does not CASE WHEN column1 IS NOT NULL THEN column1 * column2 ELSE column3 END //but you can multiply the columns by a constant and it will push down CASE WHEN column1 IS NOT NULL THEN column1 * 34567 ELSE column3 END //or CASE WHEN column1 IS NOT NULL THEN 34567 * column2 ELSE column3 END //or casting to consistent datatypes with BIGDECIMAL output CASE WHEN column1 IS NOT NULL THEN cast(column1 as BIGDECIMAL ) * cast(column2 as BIGDECIMAL ) ELSE cast(column3 as BIGDECIMAL ) END //BUT output it as double with the cast statement above changed and it does push down (so floating point works) CASE WHEN column1 IS NOT NULL THEN cast(column1 as double ) * cast(column2 as double) ELSE cast(column3 as double) END Source data types: Column1 is BIGDECIMAL Column2 is BIGINT/LONG Column3 is BIGDECIMAL Output column is BIGDECIMAL was: Pushdown doesn't happen when two columns are multiplied in the THEN portion of a CASE statement with bigdecimal data type. //this should push down but does not CASE WHEN column1 IS NOT NULL THEN column1 * column2 ELSE column3 END //but you can multiply the columns by a constant and it will push down CASE WHEN column1 IS NOT NULL THEN column1 * 34567 ELSE column3 END //or CASE WHEN column1 IS NOT NULL THEN 34567 * column2 ELSE column3 END We're ouputting as bigdecimal so that may be a factor in the decision to push down as double datatype does work. > Multiplying two columns in CASE statement overrides pushdown (Impala) > --------------------------------------------------------------------- > > Key: TEIID-3937 > URL: https://issues.jboss.org/browse/TEIID-3937 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.12.4 > Environment: Ubuntu Trusty > Reporter: Don Krapohl > Assignee: Steven Hawkins > > In the Impala translator, pushdown doesn't happen when two columns are multiplied in the THEN portion of a CASE statement with bigdecimal data type. > //this should push down but does not > CASE WHEN column1 IS NOT NULL > THEN column1 * column2 > ELSE column3 END > //but you can multiply the columns by a constant and it will push down > CASE WHEN column1 IS NOT NULL > THEN column1 * 34567 > ELSE column3 END > //or > CASE WHEN column1 IS NOT NULL > THEN 34567 * column2 > ELSE column3 END > //or casting to consistent datatypes with BIGDECIMAL output > CASE WHEN column1 IS NOT NULL > THEN cast(column1 as BIGDECIMAL ) * cast(column2 as BIGDECIMAL ) > ELSE cast(column3 as BIGDECIMAL ) END > //BUT output it as double with the cast statement above changed and it does push down (so floating point works) > CASE WHEN column1 IS NOT NULL > THEN cast(column1 as double ) * cast(column2 as double) > ELSE cast(column3 as double) END > Source data types: > Column1 is BIGDECIMAL > Column2 is BIGINT/LONG > Column3 is BIGDECIMAL > Output column is BIGDECIMAL -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3937) Multiplying two columns in CASE statement overrides pushdown (Impala)

by Don Krapohl (JIRA)

[ https://issues.jboss.org/browse/TEIID-3937?page=com.atlassian.jira.plugin... ] Don Krapohl updated TEIID-3937: ------------------------------- Summary: Multiplying two columns in CASE statement overrides pushdown (Impala) (was: Multiplying two columns in CASE statement overrides pushdown) > Multiplying two columns in CASE statement overrides pushdown (Impala) > --------------------------------------------------------------------- > > Key: TEIID-3937 > URL: https://issues.jboss.org/browse/TEIID-3937 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.12.4 > Environment: Ubuntu Trusty > Reporter: Don Krapohl > Assignee: Steven Hawkins > > Pushdown doesn't happen when two columns are multiplied in the THEN portion of a CASE statement with bigdecimal data type. > //this should push down but does not > CASE WHEN column1 IS NOT NULL > THEN column1 * column2 > ELSE column3 END > //but you can multiply the columns by a constant and it will push down > CASE WHEN column1 IS NOT NULL > THEN column1 * 34567 > ELSE column3 END > //or > CASE WHEN column1 IS NOT NULL > THEN 34567 * column2 > ELSE column3 END > We're ouputting as bigdecimal so that may be a factor in the decision to push down as double datatype does work. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3923) Remove databasetimezone property from odata4 translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3923?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3923: --------------------------------------- Logged the date/time issue as TEIID-3938 to be tracked separately. > Remove databasetimezone property from odata4 translator > ------------------------------------------------------- > > Key: TEIID-3923 > URL: https://issues.jboss.org/browse/TEIID-3923 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.13 > > > The databasetimezone execution property is not used - and not needed since all date/time information needs to be in gmt or with an explicit timezone. > This is a candidate for 8.12.5 as well. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3938) EdmDate and EdmTimeOfDay output in local timezone

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3938: ------------------------------------- Summary: EdmDate and EdmTimeOfDay output in local timezone Key: TEIID-3938 URL: https://issues.jboss.org/browse/TEIID-3938 Project: Teiid Issue Type: Bug Components: Misc. Connectors Reporter: Steven Hawkins Assignee: Steven Hawkins EdmDate and EdmTimeOfDay both assume GMT for incoming string values - however when the convert from Java objects to string they use the local/default Calendar. So when Teiid is on a server not in GMT date and time value sent via the odata4 translator will likely be wrong. Ramesh: I have posted a question to the Olingo development group here http://markmail.org/search/list:org.apache.olingo.dev#query:list%3Aorg.ap... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3231) Enable setting on MongoDB translator for controlling timezone setting for Date and Timestamp columns

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3231?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3231: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1167321|https://bugzilla.redhat.com/show_bug.cgi?id=1167321] from NEW to CLOSED > Enable setting on MongoDB translator for controlling timezone setting for Date and Timestamp columns > ---------------------------------------------------------------------------------------------------- > > Key: TEIID-3231 > URL: https://issues.jboss.org/browse/TEIID-3231 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Van Halbert > > Timezone of DV server has influence on Date and Timestamp columns in some data sources -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2016