March 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4028) adding salesforce-34 resource adapter does not work through the cli

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4028?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-4028: ------------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) Ramesh, is there a container enhancement that will be needed here as well? > adding salesforce-34 resource adapter does not work through the cli > ------------------------------------------------------------------- > > Key: TEIID-4028 > URL: https://issues.jboss.org/browse/TEIID-4028 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.12.5 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > > The console reports that slot is not a recognized property for resource-adapter add. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4048) OData - update of clob value using HTTP method PATCH does not set correct value of the column

by Juraj Duráni (JIRA)

Juraj Duráni created TEIID-4048: ----------------------------------- Summary: OData - update of clob value using HTTP method PATCH does not set correct value of the column Key: TEIID-4048 URL: https://issues.jboss.org/browse/TEIID-4048 Project: Teiid Issue Type: Sub-task Components: OData Reporter: Juraj Duráni Assignee: Ramesh Reddy This affects both XML and JSON format. *URL:* http://localhost:8080/odata4/olingo_basic/Source/PatchTable(2) *Entity:* {code:xml} <?xml version='1.0' encoding='UTF-8'?> <entry xmlns="http://www.w3.org/2005/Atom" xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:m="http://docs.oasis-open.org/odata/ns/metadata" xmlns:d="http://docs.oasis-open.org/odata/ns/data" xmlns:gml="http://www.opengis.net/gml" xmlns:georss="http://www.georss.org/georss"> <category scheme="http://docs.oasis-open.org/odata/ns/scheme" /> <content type="application/xml"> <m:properties> <d:intnum m:type="Int32">4</d:intnum> <d:stringval>4</d:stringval> <d:timestampval m:type="DateTimeOffset">2004-01-01T00:00:04Z</d:timestampval> <d:clobval m:type="Binary">Y2xvYl92YWx1ZV8wMDAwNA==</d:clobval> </m:properties> </content> </entry> {code} *Result of GET:* {code:xml} <d:clobval m:type="Binary">NjM2YzZmNjI1Zjc2NjE2Yzc1NjU1ZjMwMzAzMDMwMzU=</d:clobval> {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3647) Create native connector to interact with HDFS as a datasource

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3647?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-3647: ------------------------------------- Assignee: (was: Steven Hawkins) > Create native connector to interact with HDFS as a datasource > ------------------------------------------------------------- > > Key: TEIID-3647 > URL: https://issues.jboss.org/browse/TEIID-3647 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Van Halbert > Fix For: 9.x > > > Would like to have native connector > To interact with HDFS as a datasource from a DV perspective there are at least two options: > 1 - HttpFS > 2 - WebHDFS > Both options seems to be in practise very slow. I heard 2x slower. > It would be nice if we can create a native HDFS connector. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 commented on TEIID-4024: --------------------------------------- With the fix I still see bad behavior some of the time on the deploy side. Perhaps this is not something we can reliably address. This is somewhat related to MSC-142 and MSC-139 - there may be a need to back port some of those changes. > 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 > 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 (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4047) OData - $top with negative value return status code 500

by Juraj Duráni (JIRA)

Juraj Duráni created TEIID-4047: ----------------------------------- Summary: OData - $top with negative value return status code 500 Key: TEIID-4047 URL: https://issues.jboss.org/browse/TEIID-4047 Project: Teiid Issue Type: Sub-task Components: OData Reporter: Juraj Duráni Assignee: Ramesh Reddy OData request with query option $top with negative value returns status code 500. The root cause is SQLException. OData service should check passed value and return e.g. 400 instead. *URL:* http://localhost:8080/odata4/olingo_basic/Source/Customers/?$top=-1 See http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-pr... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4046) OData - $skip is beeing ignored

by Juraj Duráni (JIRA)

Juraj Duráni created TEIID-4046: ----------------------------------- Summary: OData - $skip is beeing ignored Key: TEIID-4046 URL: https://issues.jboss.org/browse/TEIID-4046 Project: Teiid Issue Type: Sub-task Components: OData Reporter: Juraj Duráni Assignee: Ramesh Reddy Query option $skip should accept non-negative integers but this option seems to be ignored by Teiid. Note, negative integer should cause error (i.e status code 400). http://localhost:8080/odata4/olingo_basic/Source/Customers/?$skip=3 See http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-pr... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4045) OData throws unknown error if $select is applied to expanded entity

by Juraj Duráni (JIRA)

Juraj Duráni created TEIID-4045: ----------------------------------- Summary: OData throws unknown error if $select is applied to expanded entity Key: TEIID-4045 URL: https://issues.jboss.org/browse/TEIID-4045 Project: Teiid Issue Type: Sub-task Components: OData Reporter: Juraj Duráni Assignee: Ramesh Reddy *URL:* http://localhost:8080/odata4/olingo_basic/Source/Customers/?$expand=Order... *Result:* OData Library: An exception without message text was thrown. *Status code:* 500 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4044) OData ignores entities with empty list of related entities if $filter is applied to expanded entities

by Juraj Duráni (JIRA)

Juraj Duráni created TEIID-4044: ----------------------------------- Summary: OData ignores entities with empty list of related entities if $filter is applied to expanded entities Key: TEIID-4044 URL: https://issues.jboss.org/browse/TEIID-4044 Project: Teiid Issue Type: Sub-task Components: OData Reporter: Juraj Duráni Assignee: Ramesh Reddy If user want to apply filter for related entities, OData service should return all entities, not only those with non-empty collection of related entities. *Example:* *URL:* http://localhost:8080/odata4/olingo_basic/Source/Customers/?$expand=Order... *Result:* OData returns only 2 customers (both have at least one order with place "town") *Expectation:* OData should return all 4 customers (two of them should have empty list of orders) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4043) If some functionality is not supported then OData should return status code 501 instead of 500

by Juraj Duráni (JIRA)

Juraj Duráni created TEIID-4043: ----------------------------------- Summary: If some functionality is not supported then OData should return status code 501 instead of 500 Key: TEIID-4043 URL: https://issues.jboss.org/browse/TEIID-4043 Project: Teiid Issue Type: Sub-task Components: OData Reporter: Juraj Duráni Assignee: Ramesh Reddy *URLs:* - http://localhost:8080/odata4/olingo_basic/Source/Customers/?$expand=Order... - http://localhost:8080/odata4/olingo_basic/Source/Customers/?$expand=Order... - http://localhost:8080/odata4/olingo_basic/Source/Customers/?$expand=Order... - http://localhost:8080/odata4/olingo_basic/Source/Customers/?$expand=Order...", GET); None of these options is implemented, but OData service for every request returns status code 500. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4042) OData returns status code 200 insteda of 204 if there are no expanded entities

by Juraj Duráni (JIRA)

Juraj Duráni created TEIID-4042: ----------------------------------- Summary: OData returns status code 200 insteda of 204 if there are no expanded entities Key: TEIID-4042 URL: https://issues.jboss.org/browse/TEIID-4042 Project: Teiid Issue Type: Sub-task Components: OData Reporter: Juraj Duráni Assignee: Ramesh Reddy *URL:* http://localhost:8080/odata4/olingo_basic/Source/Customers(4)/Orders_FK0 *Returned status code:* 200 *Expected:* 204 and empty body See http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-pr... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2016