April 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4156) Odata - incorrect count if header odata.maxpagesize is defined

by Juraj Duráni (JIRA)

Juraj Duráni created TEIID-4156: ----------------------------------- Summary: Odata - incorrect count if header odata.maxpagesize is defined Key: TEIID-4156 URL: https://issues.jboss.org/browse/TEIID-4156 Project: Teiid Issue Type: Sub-task Components: OData Affects Versions: 8.12.x Reporter: Juraj Duráni Assignee: Ramesh Reddy HTTP: GET http://localhost:8080/odata4/olingo_basic/Source/SimpleTableView?$count=t... lt 5 Header: Prefer: odata.maxpagesize=2 Actual result: <m:count>3</m:count> Expected result: <m:count>4</m:count> Additional note: Teiid returns 2 entities. ---------------------------- HTTP: GET http://localhost:8080/odata4/olingo_basic/Source/SimpleTableView?$count=true Header: Prefer: odata.maxpagesize=10 Actual result: <m:count>10</m:count> Expected result: <m:count>11</m:count> ---------------------------- Moreover, when I invoke another request for next results (including skiptoken), Teiid returns different count. HTTP: GET http://localhost:8080/odata4/olingo_basic/Source/SimpleTableView?$count=t... Actual result: <m:count>1</m:count> Expected result: <m:count>11</m:count> -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4155) Explore the possibility to use JBeret as materialization schedular

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-4155: ----------------------------------- Summary: Explore the possibility to use JBeret as materialization schedular Key: TEIID-4155 URL: https://issues.jboss.org/browse/TEIID-4155 Project: Teiid Issue Type: Enhancement Components: Server Reporter: Ramesh Reddy Right now the managed external materialization uses the our own very basic job scheduler, it would be nice if we can use JBeret batch processing system to automatically create jobs based on the materialization extension properties. JBeret is JSR-352, looks simple enough to integrate. The advantages for us would be - a standard scheduler, which will also work in "embedded" as this supposed to work in Java SE - Gives CLI based management - may be better metrics on time taken and error management -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4146) Using JDG Library Mode, unable to perform insert (

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4146?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4146. ----------------------------------- Fix Version/s: 9.0 8.12.5 Resolution: Done Merged the pull request and updated master as well. > Using JDG Library Mode, unable to perform insert ( > -------------------------------------------------- > > Key: TEIID-4146 > URL: https://issues.jboss.org/browse/TEIID-4146 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.5 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Critical > Fix For: 9.0, 8.12.5 > > > Trying to run the JDG local cache quickstart, get the following error when trying to perform an insert: > 15:09:34,027 WARN [org.teiid.PROCESSOR] (Worker1_QueryProcessorQueue12) TEIID30020 Processing exception for request O25SlCY41bD5.6 'TEIID30492 Element StockCache.Stock.StockObject of StockCache.Stock is neither nullable nor has a default value. A value must be specified in the insert.'. Originally QueryValidatorException Request.java:330. Enable more detailed logging to see the entire stacktrace. > The issue is because the StockObject column is set to be NullType.unknown, instead of NullType.Nullable. This is because the metadata processor in the translator-object is setting it incorrectly. > Workaround: > - Using Teiid Designer to import the source model and change the null type. > - use dynamic vdb and define the DDL metadata to set the null type. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4122) Improve performance of odbc client column metadata query

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4122?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4122. ----------------------------------- Fix Version/s: 9.0 (was: 9.1) Resolution: Done With more investigation the changes here are: add some more compliance around command complete and counts add a specific query override for the column metadata that avoids several joins and the overhead of the pg_attribute table allow materialization to take place proactively > Improve performance of odbc client column metadata query > -------------------------------------------------------- > > Key: TEIID-4122 > URL: https://issues.jboss.org/browse/TEIID-4122 > Project: Teiid > Issue Type: Quality Risk > Components: ODBC > Reporter: Steven Hawkins > Fix For: 9.0 > > > With cursoring, the client issues: > select n.nspname, c.relname, a.attname, a.atttypid, t.typname, a.attnum, a.attlen, a.atttypmod, a.attnotnull, c.relhasrules, c.relkind, c.oid, pg_get_expr(d.adbin, d.adrelid), case t.typtype when 'd' then t.typbasetype else 0 end, t.typtypmod, c.relhasoids from (((pg_catalog.pg_class c inner join pg_catalog.pg_namespace n on n.oid = c.relnamespace and c.oid = <table oid>) inner join pg_catalog.pg_attribute a on (not a.attisdropped) and a.attnum > 0 and a.attrelid = c.oid) inner join pg_catalog.pg_type t on t.oid = a.atttypid) left outer join pg_attrdef d on a.atthasdef and d.adrelid = a.attrelid and d.adnum = a.attnum order by n.nspname, c.relname, attnum > We should ensure that this is being planned optimally. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4154) Remove the dynamic vdb terminology

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4154?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4154: --------------------------------------- The code already is free of the dynamic vdb term. The doc set has also been updated. Quickstarts and other docs will need to be updated as well. > Remove the dynamic vdb terminology > ---------------------------------- > > Key: TEIID-4154 > URL: https://issues.jboss.org/browse/TEIID-4154 > Project: Teiid > Issue Type: Quality Risk > Components: Documentation > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > We should remove/deprecate the dynamic term and instead reference native metadata import and ddl - soon tooling will provide vdbs defined with ddl and the dynamic differentiation won't be needed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4154) Remove the dynamic vdb terminology

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4154: ------------------------------------- Summary: Remove the dynamic vdb terminology Key: TEIID-4154 URL: https://issues.jboss.org/browse/TEIID-4154 Project: Teiid Issue Type: Quality Risk Components: Documentation Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.0 We should remove/deprecate the dynamic term and instead reference native metadata import and ddl - soon tooling will provide vdbs defined with ddl and the dynamic differentiation won't be needed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4153) OLAPExecutionFactory Exception Unwrapping Results

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIID-4153?page=com.atlassian.jira.plugin... ] Ted Jones edited comment on TEIID-4153 at 4/20/16 12:59 PM: ------------------------------------------------------------ I just tried this again and it worked. I think the import was using the VDB source instead of the BW source. Chalk this one up to user error. was (Author: tejones): I just tried this again this again and it worked. I think the import was using the VDB source instead of the BW source. > OLAPExecutionFactory Exception Unwrapping Results > ------------------------------------------------- > > Key: TEIID-4153 > URL: https://issues.jboss.org/browse/TEIID-4153 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.13.3 > Reporter: Ted Jones > Assignee: Steven Hawkins > Attachments: query plan and stack trace 2.txt > > > When executing an MDX query against SAP BW (a BEx query), the following exception occurs: > 11:49:32,573 WARN [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue1) Connector worker process failed for atomic-request=9WKT1UuAq4j/.0.3.0: org.teiid.translator.TranslatorException: Not a wrapper for: org.olap4j.OlapWrapper > at org.teiid.translator.olap.OlapExecutionFactory.unwrap(OlapExecutionFactory.java:77) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4153) OLAPExecutionFactory Exception Unwrapping Results

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIID-4153?page=com.atlassian.jira.plugin... ] Ted Jones resolved TEIID-4153. ------------------------------ Resolution: Cannot Reproduce Bug I just tried this again this again and it worked. I think the import was using the VDB source instead of the BW source. > OLAPExecutionFactory Exception Unwrapping Results > ------------------------------------------------- > > Key: TEIID-4153 > URL: https://issues.jboss.org/browse/TEIID-4153 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.13.3 > Reporter: Ted Jones > Assignee: Steven Hawkins > Attachments: query plan and stack trace 2.txt > > > When executing an MDX query against SAP BW (a BEx query), the following exception occurs: > 11:49:32,573 WARN [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue1) Connector worker process failed for atomic-request=9WKT1UuAq4j/.0.3.0: org.teiid.translator.TranslatorException: Not a wrapper for: org.olap4j.OlapWrapper > at org.teiid.translator.olap.OlapExecutionFactory.unwrap(OlapExecutionFactory.java:77) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4153) OLAPExecutionFactory Exception Unwrapping Results

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4153?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4153: --------------------------------------- Ramesh, do you mean the JDBC4Olap driver? It doesn't implement the olap4j interfaces at all - it would require substantial translator rework. > OLAPExecutionFactory Exception Unwrapping Results > ------------------------------------------------- > > Key: TEIID-4153 > URL: https://issues.jboss.org/browse/TEIID-4153 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.13.3 > Reporter: Ted Jones > Assignee: Steven Hawkins > Attachments: query plan and stack trace 2.txt > > > When executing an MDX query against SAP BW (a BEx query), the following exception occurs: > 11:49:32,573 WARN [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue1) Connector worker process failed for atomic-request=9WKT1UuAq4j/.0.3.0: org.teiid.translator.TranslatorException: Not a wrapper for: org.olap4j.OlapWrapper > at org.teiid.translator.olap.OlapExecutionFactory.unwrap(OlapExecutionFactory.java:77) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4153) OLAPExecutionFactory Exception Unwrapping Results

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4153?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4153: ------------------------------------- It looked like when XMLA driver is used it not used OlapWrapper class. It uses JDBC4 wrapper, and unwraps OlapConnection > OLAPExecutionFactory Exception Unwrapping Results > ------------------------------------------------- > > Key: TEIID-4153 > URL: https://issues.jboss.org/browse/TEIID-4153 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.13.3 > Reporter: Ted Jones > Assignee: Steven Hawkins > Attachments: query plan and stack trace 2.txt > > > When executing an MDX query against SAP BW (a BEx query), the following exception occurs: > 11:49:32,573 WARN [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue1) Connector worker process failed for atomic-request=9WKT1UuAq4j/.0.3.0: org.teiid.translator.TranslatorException: Not a wrapper for: org.olap4j.OlapWrapper > at org.teiid.translator.olap.OlapExecutionFactory.unwrap(OlapExecutionFactory.java:77) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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