May 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3471) unable to consume odata service deployed in teiid

by Ron Sigal (JIRA)

[ https://issues.jboss.org/browse/TEIID-3471?page=com.atlassian.jira.plugin... ] Ron Sigal commented on TEIID-3471: ---------------------------------- Thank you, Ramesh. > unable to consume odata service deployed in teiid > ------------------------------------------------- > > Key: TEIID-3471 > URL: https://issues.jboss.org/browse/TEIID-3471 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Labels: CR1 > Fix For: 8.11 > > Attachments: deployment-exception.txt, MyVDB-vdb.xml, standalone-snippet.xml > > > I am unable to consume odata service created in teiid. > Steps to reproduce and files are attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3471) unable to consume odata service deployed in teiid

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3471?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3471: ------------------------------------- [~ron_sigal] Here it is https://issues.jboss.org/browse/RESTEASY-1175 > unable to consume odata service deployed in teiid > ------------------------------------------------- > > Key: TEIID-3471 > URL: https://issues.jboss.org/browse/TEIID-3471 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Labels: CR1 > Fix For: 8.11 > > Attachments: deployment-exception.txt, MyVDB-vdb.xml, standalone-snippet.xml > > > I am unable to consume odata service created in teiid. > Steps to reproduce and files are attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3471) unable to consume odata service deployed in teiid

by Ron Sigal (JIRA)

[ https://issues.jboss.org/browse/TEIID-3471?page=com.atlassian.jira.plugin... ] Ron Sigal commented on TEIID-3471: ---------------------------------- Hey Ramesh, yes, please create a JIRA. Thanks. > unable to consume odata service deployed in teiid > ------------------------------------------------- > > Key: TEIID-3471 > URL: https://issues.jboss.org/browse/TEIID-3471 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Labels: CR1 > Fix For: 8.11 > > Attachments: deployment-exception.txt, MyVDB-vdb.xml, standalone-snippet.xml > > > I am unable to consume odata service created in teiid. > Steps to reproduce and files are attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3471) unable to consume odata service deployed in teiid

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3471?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3471: ------------------------------------- [~ron_sigal] Previously I did not have control over the library we were using, now that we have forked the library we have more flexibility to make changes. So, in effect we fixed our problem to work with deficiency in the RestEasy library, but I believe that the issue still needs to be fixed in the RestEasy library so that it does not affect in general in other similar scenarios. BTW, I tested the same in other frameworks like CXF and Jersy and they seem to work fine without specifying the "charset=utf-8" from client. If you want I can add JIRA to RestEasy, let me know. > unable to consume odata service deployed in teiid > ------------------------------------------------- > > Key: TEIID-3471 > URL: https://issues.jboss.org/browse/TEIID-3471 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Labels: CR1 > Fix For: 8.11 > > Attachments: deployment-exception.txt, MyVDB-vdb.xml, standalone-snippet.xml > > > I am unable to consume odata service created in teiid. > Steps to reproduce and files are attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3471) unable to consume odata service deployed in teiid

by Ron Sigal (JIRA)

[ https://issues.jboss.org/browse/TEIID-3471?page=com.atlassian.jira.plugin... ] Ron Sigal commented on TEIID-3471: ---------------------------------- re: "updated the OReva to 0.8.3, to accept the header 'application/xml' in addition to 'application/xml;charset=utf-8' so that when a REST client issues just with accepts header 'application/xml' it is not going to fail anymore." Ramesh, are you satisfied with Resteasy as it is, then? > unable to consume odata service deployed in teiid > ------------------------------------------------- > > Key: TEIID-3471 > URL: https://issues.jboss.org/browse/TEIID-3471 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Labels: CR1 > Fix For: 8.11 > > Attachments: deployment-exception.txt, MyVDB-vdb.xml, standalone-snippet.xml > > > I am unable to consume odata service created in teiid. > Steps to reproduce and files are attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3166) Allow allowDiskUse setting in MongoDB translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3166?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3166. --------------------------------- Fix Version/s: 8.11 Resolution: Done There is no regression, the way it was designed previously was the default version of the MongoDB is set to 2.4, and useDisk option is defined to work with version 2.6. If you need to use it you need to define a translator override property "DatabaseVersion" to "2.6", and that will use the useDisk feature. But as part of this defect, now I moved the default version of the MongoDB to 2.6, so one does not have to define the "DatabaseVersion" property to use the "useDisk" feature. Also, I made sure that this will work even for future updates of MongoDB versions that are >= 2.6. This also exposed a error in $near and $nearSphere methods not supporting the "$minDistance" parameter when used with 2.6 version. I fixed to code, such that Teiid will generate right query based on 2.4 or >= 2.6 versions. > Allow allowDiskUse setting in MongoDB translator > ------------------------------------------------ > > Key: TEIID-3166 > URL: https://issues.jboss.org/browse/TEIID-3166 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Harrison Gentry > Assignee: Ramesh Reddy > Priority: Minor > Labels: CR1 > Fix For: 8.11, 8.9 > > > When querying a MongoDB, steps of computation are limited to 100MiB. Querying large databases can easily exceed this limit, so usually allowDiskUse:true is passed in the aggregate query: > http://docs.mongodb.org/manual/reference/command/aggregate/ > In Teiid, however, there is currently no way to specify this with SQL. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3471) unable to consume odata service deployed in teiid

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIID-3471?page=com.atlassian.jira.plugin... ] Mark Drilling commented on TEIID-3471: -------------------------------------- I would vote yes on 6.2... > unable to consume odata service deployed in teiid > ------------------------------------------------- > > Key: TEIID-3471 > URL: https://issues.jboss.org/browse/TEIID-3471 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Labels: CR1 > Fix For: 8.11 > > Attachments: deployment-exception.txt, MyVDB-vdb.xml, standalone-snippet.xml > > > I am unable to consume odata service created in teiid. > Steps to reproduce and files are attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3471) unable to consume odata service deployed in teiid

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3471?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3471: ------------------------------------- Aslo this is good candidate to take to 6.2? Should we do that? > unable to consume odata service deployed in teiid > ------------------------------------------------- > > Key: TEIID-3471 > URL: https://issues.jboss.org/browse/TEIID-3471 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Labels: CR1 > Fix For: 8.11 > > Attachments: deployment-exception.txt, MyVDB-vdb.xml, standalone-snippet.xml > > > I am unable to consume odata service created in teiid. > Steps to reproduce and files are attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3471) unable to consume odata service deployed in teiid

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3471?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3471. --------------------------------- Labels: CR1 (was: ) Fix Version/s: 8.11 Resolution: Done updated the OReva to 0.8.3, to accept the header 'application/xml' in addition to 'application/xml;charset=utf-8' so that when a REST client issues just with accepts header 'application/xml' it is not going to fail anymore. > unable to consume odata service deployed in teiid > ------------------------------------------------- > > Key: TEIID-3471 > URL: https://issues.jboss.org/browse/TEIID-3471 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Labels: CR1 > Fix For: 8.11 > > Attachments: deployment-exception.txt, MyVDB-vdb.xml, standalone-snippet.xml > > > I am unable to consume odata service created in teiid. > Steps to reproduce and files are attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3436) Add array type support to the odata translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3436?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3436: ------------------------------------- Sort of IMO. You can import fine now. So, select/GET entity should work as defined by its metadata. But support for create, update entities based on Array is still missing. I see there is general lack of support in parsing of the input data from the client. May be that is been done in V3 code base donation OReva has. Depending on how much we want to support this, we can keep this open for V2 or V3. Otherwise we can close and generally support the create/update with arrays starting form V4? > Add array type support to the odata translator > ---------------------------------------------- > > Key: TEIID-3436 > URL: https://issues.jboss.org/browse/TEIID-3436 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Steven Hawkins > > Arrays of basic types in odata responses should be convertible into a runtime array type. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

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