October 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3783) Error when limit/sort is pushed above a window function

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3783: ------------------------------------- Summary: Error when limit/sort is pushed above a window function Key: TEIID-3783 URL: https://issues.jboss.org/browse/TEIID-3783 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.12 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.12.1, 8.13 TEIID-3568 introduced a regression by pushing a sort over a project node, but not accounting for aliases. This can be reproduced with a query such as: select column_a, column_b from (select sum(column_a) over (partition by key_column) as column_a, key_column from a ) a left outer join ( select sum(column_b) over (partition by key_column) as column_b, key_column from b) b on a.key_column = b.key_column order by column_a desc limit 10 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3759) Missing Apache Olingo dependency in Teiid 8.12.0.Final

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3759?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3759. --------------------------------- Fix Version/s: 8.12.1 (was: 8.12.x) Resolution: Done Corrected the dependecy such that "odata-commons-api" will be picked up for the embedded kit. Note that "jdbc" and "ws" translators are also dependencies for this translator to be used > Missing Apache Olingo dependency in Teiid 8.12.0.Final > ------------------------------------------------------ > > Key: TEIID-3759 > URL: https://issues.jboss.org/browse/TEIID-3759 > Project: Teiid > Issue Type: Quality Risk > Components: Embedded, OData > Affects Versions: 8.12 > Reporter: Gary Gregory > Assignee: Ramesh Reddy > Fix For: 8.12.1 > > > I think Teiid might have a missing Apache Olingo dependency: > {noformat} > java.lang.NoClassDefFoundError: org/apache/olingo/commons/api/edm/provider/CsdlBindingTarget > at org.teiid.translator.odata4.ODataExecutionFactory.getMetadataProcessor(ODataExecutionFactory.java:140) > at org.teiid.deployers.TranslatorUtil.buildTranslatorProperties(TranslatorUtil.java:280) > at org.teiid.deployers.TranslatorUtil.buildTranslatorMetadata(TranslatorUtil.java:252) > ... > Caused by: java.lang.ClassNotFoundException: org.apache.olingo.commons.api.edm.provider.CsdlBindingTarget > at java.net.URLClassLoader$1.run(URLClassLoader.java:366) > at java.net.URLClassLoader$1.run(URLClassLoader.java:355) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:354) > at java.lang.ClassLoader.loadClass(ClassLoader.java:425) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) > at java.lang.ClassLoader.loadClass(ClassLoader.java:358) > ... 35 more > {noformat} > There is no Apache Olingo in {{optional/odata}} or {{lib/optional/odata4}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3759) Missing Apache Olingo dependency in Teiid 8.12.0.Final

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3759?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-3759: -------------------------------- Issue Type: Quality Risk (was: Enhancement) > Missing Apache Olingo dependency in Teiid 8.12.0.Final > ------------------------------------------------------ > > Key: TEIID-3759 > URL: https://issues.jboss.org/browse/TEIID-3759 > Project: Teiid > Issue Type: Quality Risk > Components: Embedded, OData > Affects Versions: 8.12 > Reporter: Gary Gregory > Assignee: Ramesh Reddy > Fix For: 8.12.x > > > I think Teiid might have a missing Apache Olingo dependency: > {noformat} > java.lang.NoClassDefFoundError: org/apache/olingo/commons/api/edm/provider/CsdlBindingTarget > at org.teiid.translator.odata4.ODataExecutionFactory.getMetadataProcessor(ODataExecutionFactory.java:140) > at org.teiid.deployers.TranslatorUtil.buildTranslatorProperties(TranslatorUtil.java:280) > at org.teiid.deployers.TranslatorUtil.buildTranslatorMetadata(TranslatorUtil.java:252) > ... > Caused by: java.lang.ClassNotFoundException: org.apache.olingo.commons.api.edm.provider.CsdlBindingTarget > at java.net.URLClassLoader$1.run(URLClassLoader.java:366) > at java.net.URLClassLoader$1.run(URLClassLoader.java:355) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:354) > at java.lang.ClassLoader.loadClass(ClassLoader.java:425) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) > at java.lang.ClassLoader.loadClass(ClassLoader.java:358) > ... 35 more > {noformat} > There is no Apache Olingo in {{optional/odata}} or {{lib/optional/odata4}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3686) OData DELETE nonexisting row - wrong response code

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3686?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3686: ------------------------------------------------ Jan Stastny <jstastny(a)redhat.com> changed the Status of [bug 1261027|https://bugzilla.redhat.com/show_bug.cgi?id=1261027] from ON_QA to VERIFIED > OData DELETE nonexisting row - wrong response code > -------------------------------------------------- > > Key: TEIID-3686 > URL: https://issues.jboss.org/browse/TEIID-3686 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7.1.6_2 > Reporter: Michal Sanitrak > Assignee: Ramesh Reddy > Labels: CR1 > Fix For: 8.12 > > > I deployed VDB that can be accessed with OData. When I perform DELETE request to remove row for first time response code is 200 OK (maybe it should be 204) but when I repeat the same DELETE request and tried to delete already deleted entry, response is again 200 OK, but it should be 404 Not Found. Same thing happens even I when tried to delete entry with id that doesn't exist at all. > Only indication of this problem is in the server log: > {code:plain}INFO [org.teiid.ODATA] (http-/127.0.0.1:8080-1) no entity to delete in = BooksMySQL.BOOKS with key= ('1') > {code} > I think that response code for deleting row that doesn't exist should be different than 200 OK. > For example the service at odata.org returns following content with response code 404 Not Found: > {code:xml} > <?xml version="1.0" encoding="utf-8" standalone="yes"?> > <error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"> > <code></code> > <message xml:lang="en-US">Resource not found for the segment 'Products'.</message> > </error> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3782) OData V4: Support system options over the operation based collections

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-3782: ----------------------------------- Summary: OData V4: Support system options over the operation based collections Key: TEIID-3782 URL: https://issues.jboss.org/browse/TEIID-3782 Project: Teiid Issue Type: Bug Components: OData Affects Versions: 8.11 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.12.x Currently the system options like $top, $skip, $filter are not supported on results returned from Functions/Actions. Per OData specification this should be supported. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3039) OData V2: Add support for odata expand

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3039?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3039. --------------------------------- Resolution: Done Did not use the XML document modeling, but I used the similar technique as used in V4. Added the basic one level support for $expand. So user would be able to do http://localhost:8080/odata/vdb/Customer?$expand=Orders but this can NOT support http://localhost:8080/odata/vdb/Customer?$expand=Orders,OrderLines http://localhost:8080/odata/vdb/Customer?$expand=Orders/OrderLines Based on the need we can further evaluate expanding, but this should cover most of the use cases. One caveat is, when using the $expand, the option $inlinecount=allpages will not work, as it not simple row count any more and it has performance implications to compute that field. So the code is set to ignore the option it in that situation. > OData V2: Add support for odata expand > -------------------------------------- > > Key: TEIID-3039 > URL: https://issues.jboss.org/browse/TEIID-3039 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 8.12.1 > > > We should add support for odata expand. This can be done with logic similar to the xml document model. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3761) OData V2: The property based response and Function based responses are incorrect per specification

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3761?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3761. --------------------------------- Resolution: Done The return of the property based response was set to "entity" based response, which is in-correct per the OData specification. Corrected the code return either property or raw property in case of $value > OData V2: The property based response and Function based responses are incorrect per specification > -------------------------------------------------------------------------------------------------- > > Key: TEIID-3761 > URL: https://issues.jboss.org/browse/TEIID-3761 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.4 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.12.1 > > > The property request like > {code} > http://localhost:8080/odata/vdb/table/property > http://localhost:8080/odata/vdb/table/property/$value > {code} > needs to return a property based response, instead they are returning the "entity" based response. > The function with simple scalar return, should return just simple data > {code} > http://localhost:8080/odata/vdb/func?param=value > {code} > instead it returning the collection based data -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3762) OData V2: $value on property is not supported

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3762?page=com.atlassian.jira.plugin... ] Ramesh Reddy edited comment on TEIID-3762 at 10/21/15 4:34 PM: --------------------------------------------------------------- Needed to add RAW property support to OReva (0.8.10), along with correcting the TEIID-3761 the raw property value can be returned to calling user. was (Author: rareddy): Need to add RAW property support to OReva, along with correcting the TEIID-3761 the raw property value can be returned to calling user. > OData V2: $value on property is not supported > --------------------------------------------- > > Key: TEIID-3762 > URL: https://issues.jboss.org/browse/TEIID-3762 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.4 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.12.1 > > > A raw property value can be retrieved using the $value segment, like > {code} > http://localhost:8080/odata/vdb/table/property/$value > {code} > This should be suported, or should throw a proper error -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3762) OData V2: $value on property is not supported

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3762?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3762. --------------------------------- Fix Version/s: 8.12.1 Resolution: Done Need to add RAW property support to OReva, along with correcting the TEIID-3761 the raw property value can be returned to calling user. > OData V2: $value on property is not supported > --------------------------------------------- > > Key: TEIID-3762 > URL: https://issues.jboss.org/browse/TEIID-3762 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.4 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.12.1 > > > A raw property value can be retrieved using the $value segment, like > {code} > http://localhost:8080/odata/vdb/table/property/$value > {code} > This should be suported, or should throw a proper error -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3757) OData V2: $top doesn't work with virtual procedures

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3757?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3757. --------------------------------- Fix Version/s: 8.12.1 Resolution: Done Added support all the System Query Options $top, $skip, $filter, $orderby, $select The implementation of code using the inline views over the procedure execution and then applying the rest of the options on top exactly similar to that of executing the entity based requests. > OData V2: $top doesn't work with virtual procedures > --------------------------------------------------- > > Key: TEIID-3757 > URL: https://issues.jboss.org/browse/TEIID-3757 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7.1.6_2 > Reporter: Debbie Steigner > Assignee: Ramesh Reddy > Fix For: 8.12.1 > > Attachments: odat.vdb > > > When using OData to query a virtual procedure with a input parameter $top gets ignored: > http://127.0.0.1:8080/odata/odat/proctest?string_in='30'&$top=5 > Returns all the rows. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 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 October 2015