January 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3918) HIVE translator does not support direct query procedure

by jie tao (JIRA)

jie tao created TEIID-3918: ------------------------------ Summary: HIVE translator does not support direct query procedure Key: TEIID-3918 URL: https://issues.jboss.org/browse/TEIID-3918 Project: Teiid Issue Type: Feature Request Reporter: jie tao Assignee: Steven Hawkins I used EXEC native (sqlstring) to let my query be executed directly on my Hive without Teiid's modification of my query. This works with MySQL. For HIVE I got: "org.teiid.jdbc.TeiidSQLException: TEIID30504 Hive13: TEIID24000 This EXEC native('select a.game, a.lang, get_json_object(a.json, \"$.product\") from test.event_log a') command not supported. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3917) Allow partial projection of window functions

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3917: ------------------------------------- Summary: Allow partial projection of window functions Key: TEIID-3917 URL: https://issues.jboss.org/browse/TEIID-3917 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.0 Currently the pushProjection check in RuleAssignOutputElements does not consider projected columns from a node that has window functions. This should be relaxed so that more can be pushed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3906) OData v4 - definition of OData-Isolation header is either being ignored or is not implemented correctly

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-3906?page=com.atlassian.jira.plugin... ] Juraj Duráni updated TEIID-3906: -------------------------------- Summary: OData v4 - definition of OData-Isolation header is either being ignored or is not implemented correctly (was: OData v4 - definition of OData-Isolation header is either being ignored or is not implemented corectly) > OData v4 - definition of OData-Isolation header is either being ignored or is not implemented correctly > ------------------------------------------------------------------------------------------------------- > > Key: TEIID-3906 > URL: https://issues.jboss.org/browse/TEIID-3906 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12.3 > Environment: Teiid - OData v4 > Reporter: Juraj Duráni > Assignee: Ramesh Reddy > > Teiid does not process header *OData-Isolation: snapshot* defined in request correctly. > * if service (Teiid) does not support this option it must return error 412 > * if Teiid does supports this option then it is not processed correctly, because modifications made during request are visbile > 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)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3916) Support SAML security on OData interface using Keycloak

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-3916: ----------------------------------- Summary: Support SAML security on OData interface using Keycloak Key: TEIID-3916 URL: https://issues.jboss.org/browse/TEIID-3916 Project: Teiid Issue Type: Feature Request Components: OData Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.13, 8.12.5 Support SAML based authentication using the Keycloak. The previous approach defined was using the Picketlink in the documentation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3909) Add support for odata geospatial handling

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3909?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3909: --------------------------------------- This isn't as simple as it first seems. The base Edm.Geometry type is not usable - you have to map to a more specific geometry type (their Geospatial object model is hierarchical, but not their type model). We also need to convert the geometry values to the object model values there is no logic around using a well known format. > Add support for odata geospatial handling > ----------------------------------------- > > Key: TEIID-3909 > URL: https://issues.jboss.org/browse/TEIID-3909 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > We should use the Edm.Geometry type for the Teiid geometry type (we can also use system metadata to see if it's appropriate to use a geometry subtype) along with any geospatial operations that odata and Teiid support. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3906) OData v4 - definition of OData-Isolation header is either being ignored or is not implemented corectly

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3906?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-3906: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > OData v4 - definition of OData-Isolation header is either being ignored or is not implemented corectly > ------------------------------------------------------------------------------------------------------ > > Key: TEIID-3906 > URL: https://issues.jboss.org/browse/TEIID-3906 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12.3 > Environment: Teiid - OData v4 > Reporter: Juraj Duráni > Assignee: Ramesh Reddy > > Teiid does not process header *OData-Isolation: snapshot* defined in request correctly. > * if service (Teiid) does not support this option it must return error 412 > * if Teiid does supports this option then it is not processed correctly, because modifications made during request are visbile > 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)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3914) Datetime values not properly encoded in OData4 entity identifiers

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3914?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3914: ---------------------------------- Attachment: TEIID-3914.diff Attaching a partial patch against master built on TEIID-3912. But it looks like this should generally be handled on the odata side (and ideally EntityCollectionResponse would just reuse the EntityResponse.buildLocation call). > Datetime values not properly encoded in OData4 entity identifiers > ----------------------------------------------------------------- > > Key: TEIID-3914 > URL: https://issues.jboss.org/browse/TEIID-3914 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12.4 > Reporter: Simon Evenepoel > Assignee: Steven Hawkins > Labels: odata, > Attachments: TEIID-3914.diff > > > When the primary key of an OData entry consists of a timestamp or datetime value an odata get request returns the following error message: > java.net.URISyntaxException: Illegal character in scheme name at index n: tablename(partofkey='keyvalue',datepartofkey=2016-01-13 11:25:03.884) > For more information visit this thread on the user forums in which [~shawkins] said: > _"Actually there is an issue with our handling of building the entity id to go into the response. We are not properly encoding datatime values.''_ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3914) Datetime values not properly encoded in OData4 entity identifiers

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3914?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-3914: ------------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > Datetime values not properly encoded in OData4 entity identifiers > ----------------------------------------------------------------- > > Key: TEIID-3914 > URL: https://issues.jboss.org/browse/TEIID-3914 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12.4 > Reporter: Simon Evenepoel > Assignee: Ramesh Reddy > Labels: odata, > Attachments: TEIID-3914.diff > > > When the primary key of an OData entry consists of a timestamp or datetime value an odata get request returns the following error message: > java.net.URISyntaxException: Illegal character in scheme name at index n: tablename(partofkey='keyvalue',datepartofkey=2016-01-13 11:25:03.884) > For more information visit this thread on the user forums in which [~shawkins] said: > _"Actually there is an issue with our handling of building the entity id to go into the response. We are not properly encoding datatime values.''_ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3915) OlingoBridge should be concurrent

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3915?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3915. ----------------------------------- Resolution: Done Switched to a concurrenthashmap > OlingoBridge should be concurrent > --------------------------------- > > Key: TEIID-3915 > URL: https://issues.jboss.org/browse/TEIID-3915 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.13, 8.12.5 > > > The map in olingobridge needs to be safe for concurrent access. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3913?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-3913: -------------------------------- Fix Version/s: 8.13 > 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.13, 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)

8 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2016