January 2016 - teiid-issues - Jboss List Archives

[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: 9.0 > 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, 9.0, 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-3925) Rename infinispan translators / resources adapters to align with running library mode versus access remote cache

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3925?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3925: ------------------------------------ Yes, I've got the 8.12 changes coming real soon, which will include the refactoring. > Rename infinispan translators / resources adapters to align with running library mode versus access remote cache > ---------------------------------------------------------------------------------------------------------------- > > Key: TEIID-3925 > URL: https://issues.jboss.org/browse/TEIID-3925 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Minor > > Currently, the infinispan translators and resource adapters are named: > - translator-infinispan-cache (infinispan-cache) / connector-infinispan.6 > - translator-infinispan-dsl (infinispan-cache-dsl) / connector-infinispan-dsl > Suggested rename to be done in version 9 to align with infinispan 7: > - translator-infinispan-library-mode (infinispan-library-mode) / connector-infinispan-library-mode.7 > - translator-infinispan-remote-cache (infinispan-remote-cache / connector-infinispan-remote-cache.7 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3925) Rename infinispan translators / resources adapters to align with running library mode versus access remote cache

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3925?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3925: --------------------------------------- This needs to have some 8.12 changes pulled forward first correct? Can you submit a pull request for this? > Rename infinispan translators / resources adapters to align with running library mode versus access remote cache > ---------------------------------------------------------------------------------------------------------------- > > Key: TEIID-3925 > URL: https://issues.jboss.org/browse/TEIID-3925 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Minor > > Currently, the infinispan translators and resource adapters are named: > - translator-infinispan-cache (infinispan-cache) / connector-infinispan.6 > - translator-infinispan-dsl (infinispan-cache-dsl) / connector-infinispan-dsl > Suggested rename to be done in version 9 to align with infinispan 7: > - translator-infinispan-library-mode (infinispan-library-mode) / connector-infinispan-library-mode.7 > - translator-infinispan-remote-cache (infinispan-remote-cache / connector-infinispan-remote-cache.7 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3925) Rename infinispan translators / resources adapters to align with running library mode versus access remote cache

by Van Halbert (JIRA)

Van Halbert created TEIID-3925: ---------------------------------- Summary: Rename infinispan translators / resources adapters to align with running library mode versus access remote cache Key: TEIID-3925 URL: https://issues.jboss.org/browse/TEIID-3925 Project: Teiid Issue Type: Enhancement Components: Misc. Connectors Affects Versions: 9.x Reporter: Van Halbert Assignee: Steven Hawkins Priority: Minor Currently, the infinispan translators and resource adapters are named: - translator-infinispan-cache (infinispan-cache) / connector-infinispan.6 - translator-infinispan-dsl (infinispan-cache-dsl) / connector-infinispan-dsl Suggested rename to be done in version 9 to align with infinispan 7: - translator-infinispan-library-mode (infinispan-library-mode) / connector-infinispan-library-mode.7 - translator-infinispan-remote-cache (infinispan-remote-cache / connector-infinispan-remote-cache.7 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3918?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3918: ------------------------------------- I think so. Hive driver should be able to handle it > 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)

10 years, 2 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3918?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3918: --------------------------------------- Ramesh, It looks like we should just allow the default JDBC direct procedure logic here correct? > 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)

10 years, 2 months

1
0
0 / 0

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3914?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3914: ------------------------------------- >11:01:29,560 ERROR [io.undertow.request] (default task-2) UT005023: Exception handling request to /odata4/Loopy.1/MarketData/$metadata: java.lang.LinkageError: >org/apache/olingo/server/core/responses/MetadataResponse Ok, this means the in-place replacement of classes will not work, I have to find an alternate way to deliver as patch to Olingo modules then. This is what I was concerned about at the beginning. I will add as patch file to the Olingo module that includes the source java file that contains the changes. > 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)

10 years, 2 months

1
0
0 / 0

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3914?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3914: ------------------------------------- I am looking at at their latest code, they changed parser code and removed antlr dependency, I should have realized you are looking at the current version. But even there I did not see before but they are decoding the whole path at the beginning, so there is no reason for them to be using the "fromUriLiteral" in that case.. arrrg. I will revert the changes. > 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)

10 years, 2 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 commented on TEIID-3914: --------------------------------------- > which seems like they are NOT decoding them during parsing Yes they are decoded. If you alter the test case as shown you'll see UriParameterImpl.setText being called with the decoded text. That in turn will cause an exception during the UriValidator.validate when the value is decoded again by EdmString. > 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)

10 years, 2 months

1
0
0 / 0

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3914?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3914: ------------------------------------- The real question is if the Olingo parser when it parses also decodes the parameters and key-predicates or not, which seems like they are NOT decoding them during parsing, but using the fromUriLiteral. see ParserHelper.parseFunctionParameters and ParserHelper.parseKeyPredicate, but at the same time they are decoding the query options. so, little confusing. The one thing working is they only used "fromUriLiteral" for key-predicates. So, I will ask them > 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)

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