October 2019 - teiid-issues - Jboss List Archives

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

6 years, 5 months

1
0
0 / 0

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

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIIDSB-132: ------------------------------------ Summary: 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 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)

6 years, 5 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 commented on TEIID-5753: --------------------------------------- I've decided to go the route of extension metadata for now. OData is different than jdbc/pg with regards to metadata as it is not user specific, so adding a general property for individually hiding is warranted. > 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)

6 years, 5 months

1
0
0 / 0

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

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5833: ------------------------------------- Summary: 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 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)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-129) allow connection to mongodb cluster on atlas (cloud.mongodb.com)

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-129?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIIDSB-129. ------------------------------------ Resolution: Done Added a uri property to the spring boot side. > allow connection to mongodb cluster on atlas (cloud.mongodb.com) > ---------------------------------------------------------------- > > Key: TEIIDSB-129 > URL: https://issues.jboss.org/browse/TEIIDSB-129 > Project: Teiid Spring Boot > Issue Type: Bug > Components: datasource > Reporter: Marco Ardito > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.3.0 > > > The issue is that teiid mongodb connector expects connection parameters based on the " Standard Connection String Format" instead of the "DNS Seedlist Connection Format", as defined in [https://docs.mongodb.com/manual/reference/connection-string|https://docs....] > _ > "In addition to the standard connection format, MongoDB supports a DNS-constructed seed list. Using DNS to construct the available servers list allows more flexibility of deployment and the ability to change the servers in rotation without reconfiguring clients."_ > The following is a typical connection string for a DNS seedlist connection string: > mongodb+srv://server.example.com/ > and: > * a port number is not needed > * a different prefix is used, instead of mongodb:// => mongodb+srv:// > I have a "free tier" cluster instance on cloud.mongodb,com (aka Atlas), which is limited in size and resources but should be functionally identical to a full sized paid cluster on the same platform, and it does not expire. A free tier can be activated here > [https://www.mongodb.com/cloud/atlas#atlas-form-container|https://www.mong...] > I tried with both the mongodb command line client and with the GUI tool Compass (https://www.mongodb.com/products/compass) which has a community edition > and this different syntax works perfectly, while it is not supported by the current teiid connector, it seems > there is a way to use the "old" syntax, prefixed by "mongodb:// " with server and port, to those Atlas clusters, but it is cumbersome, as it needs the user to specify more parameters, as "replicaSet" and "readPreference", at least. See https://docs.mongodb.com/manual/reference/connection-string > With those additional settings I was able to connect with the Compass GUI tool, but not with the latest command line client (4.2), and anyway the teiid connector seems to not support those additional parameters,, I tried to add them as DS properties but always failed -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5822) Move off of gitbook

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5822?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5822: --------------------------------------- The structure of the source will change a good bit. We effectively have two books now - one for wildfly and one for spring. However we are able to do this because of gitbook templating: {code}{% if book.targetWildfly %}{code} - which is not directly supported nor do I see a similar templating mechanism for antora. In looks like you could try to add a nunjunks processing stage to the build process to evaluate those blocks, but I'd rather not go down that path. For a given book you create a site file that defines what is being built: site.yml - composed of components (can be local or remote/git) The components are composed of modules - at least a ROOT, possibly more. Assuming an entire wildfly component: wildfly/antora.yml wildfly/modules/ROOT/nav.adoc wildfly/modules/ROOT/assets wildfly/modules/ROOT/pages/blah.adoc wildfly/modules/ROOT/examples/foo.ddl wildfly/modules/name/... We can make each of the guides a module or each of the guides a component. As a component we can pull each of them in individually into a the site file that defines the overall book - but we at least have to override the nav structure to do that. > Move off of gitbook > ------------------- > > Key: TEIID-5822 > URL: https://issues.jboss.org/browse/TEIID-5822 > Project: Teiid > Issue Type: Task > Components: Documentation > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.x > > > The gitbook cli tools are now deprecated. An update to the pdf logic has caused the travis builds to break - we need to use an old node js version because the gitbook stuff uses old constructs, but that means an older distribution - which calibre does not support anymore. For now I can look at customizing the calibre install, but longer term we need to get off of gitbook publishing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5822) Move off of gitbook

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5822?page=com.atlassian.jira.plugin... ] Work on TEIID-5822 started by Steven Hawkins. --------------------------------------------- > Move off of gitbook > ------------------- > > Key: TEIID-5822 > URL: https://issues.jboss.org/browse/TEIID-5822 > Project: Teiid > Issue Type: Task > Components: Documentation > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.x > > > The gitbook cli tools are now deprecated. An update to the pdf logic has caused the travis builds to break - we need to use an old node js version because the gitbook stuff uses old constructs, but that means an older distribution - which calibre does not support anymore. For now I can look at customizing the calibre install, but longer term we need to get off of gitbook publishing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5822) Move off of gitbook

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5822?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5822: --------------------------------------- I've run through their demo and have started down the path of https://gist.github.com/Mogztter/4d0cafa59bec82c6ec890f62d495ef31 The plan would probably be to pull 12.x + off of gitbook, but leave the older branches as they will be read-only. > Move off of gitbook > ------------------- > > Key: TEIID-5822 > URL: https://issues.jboss.org/browse/TEIID-5822 > Project: Teiid > Issue Type: Task > Components: Documentation > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.x > > > The gitbook cli tools are now deprecated. An update to the pdf logic has caused the travis builds to break - we need to use an old node js version because the gitbook stuff uses old constructs, but that means an older distribution - which calibre does not support anymore. For now I can look at customizing the calibre install, but longer term we need to get off of gitbook publishing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-131) vdb-code-generator does not honor the VDB defined thorough imports

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIIDSB-131: ------------------------------------ Summary: vdb-code-generator does not honor the VDB defined thorough imports Key: TEIIDSB-131 URL: https://issues.jboss.org/browse/TEIIDSB-131 Project: Teiid Spring Boot Issue Type: Bug Components: core Affects Versions: 1.2.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 1.3.0 When using `vdb-code-generator` plugin to read a VDB file using the dependency mechanism, it always fails due to error in code. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5822) Move off of gitbook

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5822?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5822: ------------------------------------- +1 > Move off of gitbook > ------------------- > > Key: TEIID-5822 > URL: https://issues.jboss.org/browse/TEIID-5822 > Project: Teiid > Issue Type: Task > Components: Documentation > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.x > > > The gitbook cli tools are now deprecated. An update to the pdf logic has caused the travis builds to break - we need to use an old node js version because the gitbook stuff uses old constructs, but that means an older distribution - which calibre does not support anymore. For now I can look at customizing the calibre install, but longer term we need to get off of gitbook publishing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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 October 2019