January 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3912) Centralize type handling for odata4

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3912?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3912: ------------------------------------- No LitralParser not needed, I used that before I wrote the parseLiteral method. >I don't think we need a separate module, just let the translator depend upon the Teiid odata module. This is what I wanted to avoid. The Olingo libraries give the clean separation. I do not mind we write another small module for the common code. > Centralize type handling for odata4 > ----------------------------------- > > Key: TEIID-3912 > URL: https://issues.jboss.org/browse/TEIID-3912 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > There is similar type handling logic in both the server odata4 and translator odata4 modules. This should be combined to remove duplication. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3912) Centralize type handling for odata4

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3912?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3912: --------------------------------------- Also is the LiteralParser class needed? > Centralize type handling for odata4 > ----------------------------------- > > Key: TEIID-3912 > URL: https://issues.jboss.org/browse/TEIID-3912 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > There is similar type handling logic in both the server odata4 and translator odata4 modules. This should be combined to remove duplication. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3912) Centralize type handling for odata4

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3912?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3912: --------------------------------------- > I think I did not wanted to create a Olingo common project module in the code base thus the extra class. I don't think we need a separate module, just let the translator depend upon the Teiid odata module. > If they are same, I would have take another look. Yes the module.xml files are identical and in the kit there are no jars in the client common module. > Centralize type handling for odata4 > ----------------------------------- > > Key: TEIID-3912 > URL: https://issues.jboss.org/browse/TEIID-3912 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > There is similar type handling logic in both the server odata4 and translator odata4 modules. This should be combined to remove duplication. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3912) Centralize type handling for odata4

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3912?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3912: ------------------------------------- I think I did not wanted to create a Olingo common project module in the code base thus the extra class. "Client common" and "common" should be little different not same. Olingo has same named classes in the client as well as in server libraries which makes confusing to work. If they are same, I would have take another look. > Centralize type handling for odata4 > ----------------------------------- > > Key: TEIID-3912 > URL: https://issues.jboss.org/browse/TEIID-3912 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > There is similar type handling logic in both the server odata4 and translator odata4 modules. This should be combined to remove duplication. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3912) Centralize type handling for odata4

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3912?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3912: --------------------------------------- What is the benefit in the separation? > Also I think the client has different dependency structure on the Olingo The translator has a org/apache/olingo/client/common module that is identical to the server org/apache/olingo/common module - it even in the module.xml declares itself as the org.apache.olingo.common module. It seems like the duplicate module in the translator could be removed. Beyond that the odata client and server modules are different, but that would remain even if translator referenced the server odata module. > Centralize type handling for odata4 > ----------------------------------- > > Key: TEIID-3912 > URL: https://issues.jboss.org/browse/TEIID-3912 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > There is similar type handling logic in both the server odata4 and translator odata4 modules. This should be combined to remove duplication. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3913) Support OAuth security on OData interface using Keycloak

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-3913: ----------------------------------- Summary: Support OAuth security on OData interface using Keycloak Key: TEIID-3913 URL: https://issues.jboss.org/browse/TEIID-3913 Project: Teiid Issue Type: Feature Request Components: OData Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.12.5 Provide OAuth based security on Teiid's OData interface using Keycloak technology. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3912) Centralize type handling for odata4

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3912?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3912: ------------------------------------- I wanted to keep the dependency separate between translator and server module. Also I think the client has different dependency structure on the Olingo > Centralize type handling for odata4 > ----------------------------------- > > Key: TEIID-3912 > URL: https://issues.jboss.org/browse/TEIID-3912 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > There is similar type handling logic in both the server odata4 and translator odata4 modules. This should be combined to remove duplication. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3912) Centralize type handling for odata4

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3912: ------------------------------------- Summary: Centralize type handling for odata4 Key: TEIID-3912 URL: https://issues.jboss.org/browse/TEIID-3912 Project: Teiid Issue Type: Quality Risk Components: OData Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.0 There is similar type handling logic in both the server odata4 and translator odata4 modules. This should be combined to remove duplication. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3760) endswith defined with wrong return type

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3760?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3760: --------------------------------- Fix Version/s: (was: 8.7.2.6_2) > endswith defined with wrong return type > --------------------------------------- > > Key: TEIID-3760 > URL: https://issues.jboss.org/browse/TEIID-3760 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.3 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12.1, 8.13, 8.7.6 > > > The ends with function is marked as returning string instead of boolean. Also there is inconsistent accounting for parameter ordering in the odata logic. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

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

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3436?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3436: --------------------------------- Fix Version/s: (was: 8.7.2.6_2) > OData V2: 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 > Assignee: Ramesh Reddy > Fix For: 8.12.1, 8.13, 8.7.6 > > > Arrays of basic types in odata responses should be convertible into a runtime array type. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 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 January 2016