October 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIIDSB-132) Add translator support for Amazon RedShift

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-132?page=com.atlassian.jira.plugi... ] Ramesh Reddy resolved TEIIDSB-132. ---------------------------------- Resolution: Done > Add translator support for Amazon RedShift > ------------------------------------------ > > Key: TEIIDSB-132 > URL: https://issues.jboss.org/browse/TEIIDSB-132 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 1.3.0 > > > Add Amazon RedShift translator support to the Teiid Spring Boot -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-132) Add translator support for Amazon RedShift

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-132?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIIDSB-132: --------------------------------- Git Pull Request: https://github.com/teiid/teiid-spring-boot/pull/137 > Add translator support for Amazon RedShift > ------------------------------------------ > > Key: TEIIDSB-132 > URL: https://issues.jboss.org/browse/TEIIDSB-132 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 1.3.0 > > > Add Amazon RedShift translator support to the Teiid Spring Boot -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-132) Add translator support for Amazon RedShift

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-132?page=com.atlassian.jira.plugi... ] Ramesh Reddy commented on TEIIDSB-132: -------------------------------------- Also Adding * ACTIAN * EXASOL * HBASE * REDSHIFT * SAPIQ * UCANACCESS Ignored JDBC translators * mm * Access * intersystemscache * modeshape > Add translator support for Amazon RedShift > ------------------------------------------ > > Key: TEIIDSB-132 > URL: https://issues.jboss.org/browse/TEIIDSB-132 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 1.3.0 > > > Add Amazon RedShift translator support to the Teiid Spring Boot -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5833) Update extension metadata uri's

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5833?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5833: ------------------------------------- +1, I am only concerned about examples out there and any vdb conversion utils. The later one we can fix, would be right time to fix in the major revision. > Update extension metadata uri's > ------------------------------- > > Key: TEIID-5833 > URL: https://issues.jboss.org/browse/TEIID-5833 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > There are a lot of long/old extension metadata uris - including the odata one which still references teiid designer. We should see about making these simpler - perhaps even dropping the notion of fqn vs prefix altogether so that we just deal with the raw prefixes. > The only issue with changes is when the extension properties are left fully qualified in the metadata. We'd need to lookup under both the old and new versions. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5492) Upgrade to Infinispan 9.4

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5492?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5492: ---------------------------------- Fix Version/s: 13.0 (was: 13.x) > Upgrade to Infinispan 9.4 > ------------------------- > > Key: TEIID-5492 > URL: https://issues.jboss.org/browse/TEIID-5492 > Project: Teiid > Issue Type: Task > Components: JDG Connector > Reporter: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > To address at least one outstanding issue we need to further upgrade to 9.4. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5449) Infinispan: Update Infinispan translator to 9.3 version

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5449?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5449. ----------------------------------- Fix Version/s: (was: 13.0) Resolution: Out of Date > Infinispan: Update Infinispan translator to 9.3 version > ------------------------------------------------------- > > Key: TEIID-5449 > URL: https://issues.jboss.org/browse/TEIID-5449 > Project: Teiid > Issue Type: Bug > Components: Infinispan > Affects Versions: 11.0 > Reporter: Ramesh Reddy > Priority: Major > > Two changes observed > - The new cache create API changed, the old has been deprecated > - cache.get(key) now became Async operation, that means Thread Based serialization context no longer works. This needs to be removed, but there seem to be no better alternatives to support the Async threads. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5449) Infinispan: Update Infinispan translator to 9.3 version

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5449?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5449: ---------------------------------- Fix Version/s: 13.0 (was: 13.x) > Infinispan: Update Infinispan translator to 9.3 version > ------------------------------------------------------- > > Key: TEIID-5449 > URL: https://issues.jboss.org/browse/TEIID-5449 > Project: Teiid > Issue Type: Bug > Components: Infinispan > Affects Versions: 11.0 > Reporter: Ramesh Reddy > Priority: Major > Fix For: 13.0 > > > Two changes observed > - The new cache create API changed, the old has been deprecated > - cache.get(key) now became Async operation, that means Thread Based serialization context no longer works. This needs to be removed, but there seem to be no better alternatives to support the Async threads. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5833) Update extension metadata uri's

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5833?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5833: --------------------------------------- [~blafond1] [~rareddy] any qualms with moving away from the notion of a uri for the fully qualified name of an extension property? Seems like we can get just as much mileage out of just the prefix concept. > Update extension metadata uri's > ------------------------------- > > Key: TEIID-5833 > URL: https://issues.jboss.org/browse/TEIID-5833 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > There are a lot of long/old extension metadata uris - including the odata one which still references teiid designer. We should see about making these simpler - perhaps even dropping the notion of fqn vs prefix altogether so that we just deal with the raw prefixes. > The only issue with changes is when the extension properties are left fully qualified in the metadata. We'd need to lookup under both the old and new versions. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5753) Please add extension metadata support to allow for an invisibility option on single foreign tables/views for odata layer

by Christoph John (Jira)

[ https://issues.jboss.org/browse/TEIID-5753?page=com.atlassian.jira.plugin... ] Christoph John commented on TEIID-5753: --------------------------------------- Hello Steven, thanks a lot ! > Please add extension metadata support to allow for an invisibility option on single foreign tables/views for odata layer > ------------------------------------------------------------------------------------------------------------------------ > > Key: TEIID-5753 > URL: https://issues.jboss.org/browse/TEIID-5753 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Christoph John > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > The issue arose from the discussion at > https://developer.jboss.org/message/989502#989502 > > Every tables and view I specify is becoming visible in the odata service. Of course I can use GRANT to resctrict access, however, it would be more nice to not export the tables in the odata layer in the first place. Would it be possible to add some kind of per table/view INVISIBLE OPTION for odata, or could I reach the same result in a different way and how would this look like? -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5753) Please add extension metadata support to allow for an invisibility option on single foreign tables/views for odata layer

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5753?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5753. ----------------------------------- Resolution: Done Added handling for the teiid_odata:visible extension metadata property and added a doc note in the main odata docs (which are actually in the client dev guide). > Please add extension metadata support to allow for an invisibility option on single foreign tables/views for odata layer > ------------------------------------------------------------------------------------------------------------------------ > > Key: TEIID-5753 > URL: https://issues.jboss.org/browse/TEIID-5753 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Christoph John > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > The issue arose from the discussion at > https://developer.jboss.org/message/989502#989502 > > Every tables and view I specify is becoming visible in the odata service. Of course I can use GRANT to resctrict access, however, it would be more nice to not export the tables in the odata layer in the first place. Would it be possible to add some kind of per table/view INVISIBLE OPTION for odata, or could I reach the same result in a different way and how would this look like? -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2019