December 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3817) HANA FLOOR and CELING functions not applicable to boolean

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3817?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3817. --------------------------------- > HANA FLOOR and CELING functions not applicable to boolean > --------------------------------------------------------- > > Key: TEIID-3817 > URL: https://issues.jboss.org/browse/TEIID-3817 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1.6_2 > Reporter: Jan Stastny > Assignee: Steven Hawkins > Fix For: 8.12.2, 8.13 > > > SAP HANA doesn't support FLOOR and CEILING functions for BOOLEAN type. > Compared to postgresql, which also has BOOLEAN data type, it seems inconsistent. > When querying postgres directly: > {code:sql} > SELECT CEILING(BooleanValue) FROM BQT1.SmallA > {code} > is not valid query. > But through Teiid, it returns double values corresponding to the boolean value provided: > 0.0 for CEILING(false) > 1.0 for CELING(true) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4067) OData - service returns generic EAP page in case of 404

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4067?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-4067. --------------------------------- > OData - service returns generic EAP page in case of 404 > ------------------------------------------------------- > > Key: TEIID-4067 > URL: https://issues.jboss.org/browse/TEIID-4067 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Juraj Duráni > Assignee: Ramesh Reddy > Labels: Alpha3 > Fix For: 9.0, 8.12.5 > > > In general, if resource is not found service should return 404. But Teiid returns generic EAP error page, which is neither in ATOM nor in JSON format (regardless that status code is correct). Therefore, OData client cannot read and parse the response as OData error. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4123) Issues with odbc metadata

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4123?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-4123. --------------------------------- > Issues with odbc metadata > ------------------------- > > Key: TEIID-4123 > URL: https://issues.jboss.org/browse/TEIID-4123 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.13.4 > > > The values that we are sending the client for atttypmod in the column when using cursoring results in the pg odbc client reissuing the column metadata query for most column types. Since the column metadata query is not that performant - TEIID-4122 - this results in significant overhead for wide selects. > We also don't have a pg_type entry for varbinary and may need to add more array types. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4005) Allow dependent join row value to be split

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4005?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-4005. --------------------------------- > Allow dependent join row value to be split > ------------------------------------------ > > Key: TEIID-4005 > URL: https://issues.jboss.org/browse/TEIID-4005 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 8.7.4.6_2 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.7.5.6_2 > > > For some queries having a dependent join row value that spans multiple target tables should be split among those targets. > For example rather than: > (g_0.e1, g_1.e2) IN (<dependent values>)) > Use the pre 8.7 form: > (g_0.e1 IN (<dependent values>)) AND (g_1.e2 IN (<dependent values>)) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4098) Always preserve columns order in google spreadsheets models

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4098?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-4098. --------------------------------- > Always preserve columns order in google spreadsheets models > ----------------------------------------------------------- > > Key: TEIID-4098 > URL: https://issues.jboss.org/browse/TEIID-4098 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Affects Versions: 8.7 > Reporter: Marco Ardito > Assignee: Steven Hawkins > Priority: Minor > Fix For: 9.0, 8.12.5, 8.13.3 > > > I recently started using google spreadsheet datasources, and noticed that - at least sometime - the DDL model created by teiid has all columns but in a different (sort of random) order. This happened in particular using a google spreadsheet generated (linked to) google form, see forum reference attached. > Google form allows users to fill a lot of fields, which are collected as record columns in the google spreadsheet, then teiid makes that data available for integration with other sources - which is awesome, btw. > Creating a view in the VDB works anyway, since the query selects column "letters" like SELECT A,B,C and the right columns are selected, but having the model completely different from the source is weird and makes it difficult to work with it directly, if needed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3962) remove invalid character handling from Teiid odata4 logic

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3962?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3962. --------------------------------- > remove invalid character handling from Teiid odata4 logic > --------------------------------------------------------- > > Key: TEIID-3962 > URL: https://issues.jboss.org/browse/TEIID-3962 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 9.0, 8.12.5 > > > Since we now have a better influence over the odata framework, we should remove the replacement character logic from Teiid and let that be handled by the serializers - as the current handling is intended for XML but will affect both JSON and XML results. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3885) Redshift - conversion to time does not work

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3885?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3885. --------------------------------- > Redshift - conversion to time does not work > ------------------------------------------- > > Key: TEIID-3885 > URL: https://issues.jboss.org/browse/TEIID-3885 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.12.3 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.13, 8.12.4 > > > Conversion to TIME data type does not work for Redshift (using postgresql translator). > E.g.: SELECT CONVERT(timestampvalue, time) FROM Source.SmallA > Result: > {code:text} > 14:08:36,300 DEBUG [org.teiid.CONNECTOR] (Worker12_QueryProcessorQueue158) Source-specific command: SELECT cast(date_trunc('second', g_0.timevalue) AS time) FROM smalla AS g_0 > 14:08:36,481 WARN [org.teiid.CONNECTOR] (Worker12_QueryProcessorQueue158) Connector worker process failed for atomic-request=ajCOQrzOcEmF.3.0.36: org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT cast(date_trunc('second', g_0.timevalue) AS time) FROM smalla AS g_0] > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) [translator-jdbc-8.12.3.redhat-1.jar:8.12.3.redhat-1] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:349) > at sun.reflect.GeneratedMethodAccessor189.invoke(Unknown Source) [:1.8.0_40] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_40] > at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_40] > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) > at com.sun.proxy.$Proxy124.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:266) [rt.jar:1.8.0_40] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) > 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:1142) [rt.jar:1.8.0_40] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_40] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_40] > Caused by: org.postgresql.util.PSQLException: ERROR: Specified types or functions (one per INFO message) not supported on Redshift tables. > at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2157) > at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1886) > at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255) > at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:555) > at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:417) > at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:302) > 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.3.redhat-1.jar:8.12.3.redhat-1] > ... 17 more > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4024) Server fails to shutdown if vdb with REST service generation is deployed

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4024?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-4024. --------------------------------- > Server fails to shutdown if vdb with REST service generation is deployed > ------------------------------------------------------------------------ > > Key: TEIID-4024 > URL: https://issues.jboss.org/browse/TEIID-4024 > Project: Teiid > Issue Type: Bug > Components: VDB > Affects Versions: 8.12.5 > Environment: DV 6.3 ER1 > Reporter: Filip Elias > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.13.3 > > Attachments: nosource-vdb.xml, server_trace.log > > > DV sometimes won't stop if vdb with REST service generation is deployed. > Server log is in the attachment. > When the server is killed and started again, it will stop correctly. > The issue is random. Server fails to stop in 50% of cases. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4118) Temp capabilities for null ordering not correct if default is changed

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4118?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-4118. --------------------------------- > Temp capabilities for null ordering not correct if default is changed > --------------------------------------------------------------------- > > Key: TEIID-4118 > URL: https://issues.jboss.org/browse/TEIID-4118 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.10 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.0, 8.12.5, 8.13.4 > > > TEIID-2243 allowed the default sort order to be determined by a system property, but the temp capabilities always report low as the default ordering - this results in unexpected results if the default order is set to something other than low and an order by is issued with nulls low. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3983) External Materialization MATVIEW_ONERROR_ACTION WAIT problem

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3983?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3983. --------------------------------- > External Materialization MATVIEW_ONERROR_ACTION WAIT problem > ------------------------------------------------------------ > > Key: TEIID-3983 > URL: https://issues.jboss.org/browse/TEIID-3983 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12.5 > Reporter: Jan Stastny > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.13.2 > > > When using "teiid_rel:MATVIEW_ONERROR_ACTION" 'WAIT' option in materialized view definition, there's problem with blocked request. > The blocked request is the one, that triggered the materialized view's loading (first query on the defined materialized view). After such request, one can observe, that the query execution doesn't end, but hangs. > Meanwhile while examining the contents of 'status' table in the underlying database, the LoadNumber column's value increases regularly according to the defined ttl. Moreover the 'LOADSTATE' column changes from LOADING to LOADED in similar manner. The materialized table is populated with correct data. From this I assume, materialization is set up correctly. > During the wait, when logging set to DEBUG, there appears regularly, apart from the logs about refreshing the mat view, this entry: > {code:plain} > [32m09:14:52,151 DEBUG [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2695) Request Thread 87XzBpSzkyk4.0 with state PROCESSING > [32m09:14:52,151 DEBUG [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2695) Request Thread 87XzBpSzkyk4.0 - processor blocked > {code} > The log appears in 'ttl' determined intervals, each time after materialized table loading related entries. > The thread mentioned is the one created after the original query execution was initiated. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2017