August 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4376) EXECUTE IMMEDIATE should accept clob

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4376?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4376. ----------------------------------- Resolution: Done Updated to accept a clob, but with a length restriction as we don't want to introduce memory issues on long clobs. The max length is 2^18 characters and could be made into a configuration parameter if needed. > EXECUTE IMMEDIATE should accept clob > ------------------------------------ > > Key: TEIID-4376 > URL: https://issues.jboss.org/browse/TEIID-4376 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1 > > > Restricting execute immediate to string prevents longer queries from executing. This should be relaxed to clob, since we don't have an intermediate character type. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4377) Blob/clob start index message incorrect

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4377?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4377. ----------------------------------- Resolution: Done Corrected the message. > Blob/clob start index message incorrect > --------------------------------------- > > Key: TEIID-4377 > URL: https://issues.jboss.org/browse/TEIID-4377 > Project: Teiid > Issue Type: Bug > Components: Common > Affects Versions: 7.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1 > > > The clob/blob message when the start is less than 1 mentions that it's a column index, which is incorrect. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4377) Blob/clob start index message incorrect

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4377: ------------------------------------- Summary: Blob/clob start index message incorrect Key: TEIID-4377 URL: https://issues.jboss.org/browse/TEIID-4377 Project: Teiid Issue Type: Bug Components: Common Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.1 The clob/blob message when the start is less than 1 mentions that it's a column index, which is incorrect. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4376) EXECUTE IMMEDIATE should accept clob

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4376: ------------------------------------- Summary: EXECUTE IMMEDIATE should accept clob Key: TEIID-4376 URL: https://issues.jboss.org/browse/TEIID-4376 Project: Teiid Issue Type: Sub-task Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.1 Restricting execute immediate to string prevents longer queries from executing. This should be relaxed to clob, since we don't have an intermediate character type. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4372) Impala AVG returns double when bigdecimal is expected

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4372?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4372. ----------------------------------- Resolution: Done Added a general attempt to getObject if the specific getter fails. > Impala AVG returns double when bigdecimal is expected > ----------------------------------------------------- > > Key: TEIID-4372 > URL: https://issues.jboss.org/browse/TEIID-4372 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 9.0.3 > > > Impala will return double for avg(int) for example, and the driver will fail to convert when getBigDecimal is called. We need to workaround this. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4227) Impala Translator - Support Multiple Count Distinct with Group By

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4227?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4227. ----------------------------------- Resolution: Done Took the approach of inhibiting pushdown when multiple distinct aggregates are used with a group by. > Impala Translator - Support Multiple Count Distinct with Group By > ----------------------------------------------------------------- > > Key: TEIID-4227 > URL: https://issues.jboss.org/browse/TEIID-4227 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.13.3 > Reporter: Scott Wallace > Assignee: Steven Hawkins > Fix For: 9.1 > > > This is somewhat related to TEIID-3743, which added support of multiple count distinct metrics. We have a requirement to allow multiple count distinct metrics grouped by common attributes. > Currently, we get a failure as follows: > {noformat}org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.core.TeiidProcessingException: TEIID30504 vw_impression_click_transaction_process_date_detail: 500051 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0.process_date_key, SUM(g_0.num_clicks), SUM(g_0.num_impressions), COUNT(DISTINCT g_0.orderid), COUNT(DISTINCT g_0.`hash_tid`), SUM(g_0.sales) FROM detail.vw_impression_click_transaction_process_date_detail g_0 WHERE g_0.process_date_key >= '2016-05-22' AND g_0.process_date_key < '2016-05-23' AND g_0.advertiser_key = 12345 GROUP BY g_0.process_date_key] > {noformat} > To allow this request to succeed, we could have translator write that Impala query as: > {noformat} > select nvl(v1.c1,v2.c1), nvl(v1.c2,v1.c2), nvl(v1.c3,v1.c3), v1.c4, v2.c5, nvl(v1.c6,v1.c6) from ( > SELECT g_0.process_date_key as c1, > SUM(g_0.num_clicks) as c2, > SUM(g_0.num_impressions) as c3, > COUNT(DISTINCT g_0.orderid) as c4, > SUM(g_0.sales) as c6 > FROM detail.vw_impression_click_transaction_process_date_detail g_0 > WHERE g_0.process_date_key >= '2016-05-22' > AND g_0.process_date_key < '2016-05-23' > AND g_0.advertiser_key = 12345 > GROUP BY g_0.process_date_key > ) v1 inner join > ( > SELECT g_0.process_date_key as c1, > SUM(g_0.num_clicks) as c2, > SUM(g_0.num_impressions) as c3, > COUNT(DISTINCT g_0.`hash_tid`) as c5, > SUM(g_0.sales) as c6 > FROM detail.vw_impression_click_transaction_process_date_detail g_0 > WHERE g_0.process_date_key >= '2016-05-22' > AND g_0.process_date_key < '2016-05-23' > AND g_0.advertiser_key = 12345 > GROUP BY g_0.process_date_key > ) v2 on v1.c1 = v2.c1; > {noformat} > FYI [~shawkins] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4375) Allow bind values to be used for limit/offset in pushdown queries

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4375: ------------------------------------- Summary: Allow bind values to be used for limit/offset in pushdown queries Key: TEIID-4375 URL: https://issues.jboss.org/browse/TEIID-4375 Project: Teiid Issue Type: Quality Risk Components: JDBC Connector Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.2 We always put the literal values of the limit clause into the source query, but for sources that support it, it would be better to use a bind value. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4021) MSSQL Pagination

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4021?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4021. ----------------------------------- Resolution: Done Added offset support to sql server and derby. SQL Server 2012 and later will use the more standard offset / fetch next syntax. SQL Server 2008 will use the rownumber function with inline views. > MSSQL Pagination > ---------------- > > Key: TEIID-4021 > URL: https://issues.jboss.org/browse/TEIID-4021 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Reporter: Mark Tawk > Assignee: Steven Hawkins > Fix For: 9.1 > > > I'm using Teiid 8.11.3 with mssql translator. > I have a huge table over sql server 2008 on which i'm applying pagination. > I noticed slowliness in the query execution over this table at each time I increase the pagination. > I monitored the JDBC queries execute by teiid and found out that it is using top n according to the limit used into the query. > For example: > in teiid : Select * from mytable LIMIT 90 , 10 > is translated in JDBC: select top 100 from mytable > Since my table contains millions of records, when fetching the last page, the executed jdbc query is retrieving the whole table top n, to return in result the last 10 records. And the execution is taking too much time. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4374) Procedure missing for an OData metadata request to a Swagger VDB

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4374?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-4374: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > Procedure missing for an OData metadata request to a Swagger VDB > ---------------------------------------------------------------- > > Key: TEIID-4374 > URL: https://issues.jboss.org/browse/TEIID-4374 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 9.0, 9.0.1, 9.0.2 > Environment: Windows 10 Pro x64 > Java 8 > Reporter: Van Dillon > Assignee: Ramesh Reddy > Attachments: resource-adapter-rhq.xml, rhq-metadata.xml, rhq-vdb.xml, swagger.json > > > When a REST PUT path defined in Swagger has a path parameter and a body it does not appear in OData metadata. > See the attached swagger.json for an example. The operation 'executeOperation' does not appear in OData metadata. > The code that determines if a procedure is allowed is in: > org.teiid.olingo.service.ODataSchemaBuilder.allowedProcedure() > The comment seems to indicate that as long as there is only a single LOB, multiple 'in' parameters are allowed. But the actual code does not allow any other 'in' parameters if there is a LOB parameter. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4374) Procedure missing for an OData metadata request to a Swagger VDB

by Van Dillon (JIRA)

Van Dillon created TEIID-4374: --------------------------------- Summary: Procedure missing for an OData metadata request to a Swagger VDB Key: TEIID-4374 URL: https://issues.jboss.org/browse/TEIID-4374 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 9.0.2, 9.0.1, 9.0 Environment: Windows 10 Pro x64 Java 8 Reporter: Van Dillon Assignee: Steven Hawkins Attachments: resource-adapter-rhq.xml, rhq-metadata.xml, rhq-vdb.xml, swagger.json When a REST PUT path defined in Swagger has a path parameter and a body it does not appear in OData metadata. See the attached swagger.json for an example. The operation 'executeOperation' does not appear in OData metadata. The code that determines if a procedure is allowed is in: org.teiid.olingo.service.ODataSchemaBuilder.allowedProcedure() The comment seems to indicate that as long as there is only a single LOB, multiple 'in' parameters are allowed. But the actual code does not allow any other 'in' parameters if there is a LOB parameter. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 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 August 2016