January 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3559) Refactor Object and Infinispan translator / connectors

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3559?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3559: ------------------------------- Git Pull Request: https://github.com/teiid/teiid/pull/531, https://github.com/teiid/teiid/pull/588 (was: https://github.com/teiid/teiid/pull/531) > Refactor Object and Infinispan translator / connectors > ------------------------------------------------------ > > Key: TEIID-3559 > URL: https://issues.jboss.org/browse/TEIID-3559 > Project: Teiid > Issue Type: Task > Components: Misc. Connectors > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Optional > > Now that JDG has reworked its remote-cache and changed (reduced) what dependencies its exposed, there's now more common code between the object/infinispan-cache translator/connector and the infinispan-cache-dsl translator/connector. I think refactoring can eliminate issues with support and ensure common behavior across all the code. > Where is common code seen: > - searching (i.e., DSLSearch) > - updates (InfinispanUpdateExecution) > - ClassRegistry > (for starters) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3871) moving documentation from confluence to gitbook

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3871?page=com.atlassian.jira.plugin... ] Kylin Soong commented on TEIID-3871: ------------------------------------ [~shawkins], can you set confluence doc(9.0 version [1]) to read only, I have finished migration all of them. [1] https://docs.jboss.org/author/display/TEIID/Home > moving documentation from confluence to gitbook > ------------------------------------------------- > > Key: TEIID-3871 > URL: https://issues.jboss.org/browse/TEIID-3871 > Project: Teiid > Issue Type: Task > Components: Documentation > Affects Versions: 9.x > Reporter: Kylin Soong > Assignee: Kylin Soong > Fix For: 9.x > > > From Teiid DV 7 F2F Notes, > " In the Teiid 9.x timeframe we should look toward moving everything to gitbook / markdown. We should start by migrating the documentation and solicit help with the website if possible." > This issue will address this. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3871) moving documentation from confluence to gitbook

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3871?page=com.atlassian.jira.plugin... ] Kylin Soong edited comment on TEIID-3871 at 1/23/16 3:56 AM: ------------------------------------------------------------- h2. Quick Overview Quick overview: [https://teiid.gitbooks.io/documents/content/index.html] Sources Content link: [https://github.com/teiid/teiid-documents] h2.Document Migration Status ||Name||Status||link|| |Embedded Guide |Done |[https://www.gitbook.com/book/teiid/embedded-guide/details] | |Security Guide |Done |[https://www.gitbook.com/book/teiid/security-guide/details] | |Caching Guide |Done |[https://www.gitbook.com/book/teiid/caching-guide/details] | |Administrator's Guide |Done |[https://www.gitbook.com/book/teiid/administrator-s-guide/details] | |Client Developer's Guide |Done |[https://www.gitbook.com/book/teiid/client-developer-guide/details] | |Developer's Guide |Done |[https://www.gitbook.com/book/teiid/developer-s-guide/details] | |Reference Guide |Done |[https://www.gitbook.com/book/teiid/reference-guide/details] | {color:#d04437}*Note that*{color}: Once a doc in '*Done*' status, please update doc via submit to Github, rather than edit Conference pages. was (Author: kylin): h2. Quick Overview Quick overview: [https://teiid.gitbooks.io/documents/content/index.html] Sources Content link: [https://github.com/teiid/teiid-documents] h2.Document Migration Status ||Name||Status||link|| |Embedded Guide |Done |[https://www.gitbook.com/book/teiid/embedded-guide/details] | |Security Guide |Done |[https://www.gitbook.com/book/teiid/security-guide/details] | |Caching Guide |Done |[https://www.gitbook.com/book/teiid/caching-guide/details] | |Administrator's Guide |Done |[https://www.gitbook.com/book/teiid/administrator-s-guide/details] | |Client Developer's Guide |Done |[https://www.gitbook.com/book/teiid/client-developer-guide/details] | |Developer's Guide |Done |[https://www.gitbook.com/book/teiid/developer-s-guide/details] | |Reference Guide |Pending |[https://www.gitbook.com/book/teiid/reference-guide/details] | {color:#d04437}*Note that*{color}: Once a doc in '*Done*' status, please update doc via submit to Github, rather than edit Conference pages. > moving documentation from confluence to gitbook > ------------------------------------------------- > > Key: TEIID-3871 > URL: https://issues.jboss.org/browse/TEIID-3871 > Project: Teiid > Issue Type: Task > Components: Documentation > Affects Versions: 9.x > Reporter: Kylin Soong > Assignee: Kylin Soong > Fix For: 9.x > > > From Teiid DV 7 F2F Notes, > " In the Teiid 9.x timeframe we should look toward moving everything to gitbook / markdown. We should start by migrating the documentation and solicit help with the website if possible." > This issue will address this. -- 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 Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3906?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3906: ------------------------------------- Added jira https://issues.apache.org/jira/browse/OLINGO-855 > 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-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 reopened TEIID-3914: --------------------------------- Still pending for 8.12.x > 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, > Fix For: 8.13, 9.0, 8.12.5 > > 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 Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3914?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3914. --------------------------------- Fix Version/s: 8.13 9.0 8.12.5 Resolution: Done Done > 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, > Fix For: 8.13, 9.0, 8.12.5 > > 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-3834) Error during (re) adding connection factory using CLI

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3834?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-3834: -------------------------------- Fix Version/s: 9.0 (was: 8.13) > Error during (re) adding connection factory using CLI > ----------------------------------------------------- > > Key: TEIID-3834 > URL: https://issues.jboss.org/browse/TEIID-3834 > Project: Teiid > Issue Type: Sub-task > Components: Server > Affects Versions: 8.13 > Reporter: Kylin Soong > Assignee: Ramesh Reddy > Fix For: 9.0 > > > enable datasource command > {code} > /subsystem=datasources/data-source=h2:enable > {code} > seems redundant, cause datasource add already enable it, so if execute setup.cli > {code} > ./bin/jboss-cli.sh --connect --file=setup.cli > {code} > will cause a eror > {code} > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source-config.h2 is already registered", > "rolled-back" => true > } > 14:35:55,436 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 9) WFLYCTL0013: Operation ("enable") failed - address: ([ > ("subsystem" => "datasources"), > ("data-source" => "h2") > ]): org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source-config.h2 is already registered > at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) > {code} -- 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)

[ https://issues.jboss.org/browse/TEIID-3916?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-3916: -------------------------------- Component/s: Documentation > 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: Documentation, 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-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 resolved TEIID-3913. --------------------------------- Resolution: Done Pending pulling the document into GitBooks and 8.13 this is done. I will move the docs when I work on SAML case. > 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)

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: 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)

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