October 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5557) Restrict imports to a single schema

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5557?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5557. ----------------------------------- Resolution: Done The default for useFullSchemaName is now false and to import from multiple foreign schema you generally need to set useFullSchemaName to true. There's a env/system property for backwards compatibility, but in general this will force people to set the schemaName or schemaPattern. > Restrict imports to a single schema > ----------------------------------- > > Key: TEIID-5557 > URL: https://issues.jboss.org/browse/TEIID-5557 > Project: Teiid > Issue Type: Quality Risk > Components: Connector API > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > To better align with SQL/MED and to simplify legacy import properties it would be best to restrict foreign imports to a single schema. This will remove quite a bit of confusion around potential duplicate object names. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5740) Create tables/procedures for query plans and vdb info

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5740?page=com.atlassian.jira.plugin... ] Work on TEIID-5740 started by Steven Hawkins. --------------------------------------------- > Create tables/procedures for query plans and vdb info > ----------------------------------------------------- > > Key: TEIID-5740 > URL: https://issues.jboss.org/browse/TEIID-5740 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > We need another mechanism for viewing plans - either a procedure or a table. We also have a lot of vdb information that is not exposed via system metadata. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 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... ] Work on TEIID-5753 started by Steven Hawkins. --------------------------------------------- > 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5813) Using the PG protocol the Virtual View schema items are not visible

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5813?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5813: ------------------------------------- `\dS` showed all. I did not looked at the difference before. Thanks for the clarification. > Using the PG protocol the Virtual View schema items are not visible > ------------------------------------------------------------------- > > Key: TEIID-5813 > URL: https://issues.jboss.org/browse/TEIID-5813 > Project: Teiid > Issue Type: Bug > Components: ODBC, Query Engine > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > > When using PSQL client against Teiid deployed VDB, the metadata does not show the tables/views that are defined under a virtual schema. The physical or foreign types are visible correctly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5813) Using the PG protocol the Virtual View schema items are not visible

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5813?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5813: --------------------------------------- > with latest deployment on OpenShift I tried `\dt` I still did not see Views in the result \dt is for tables - Note "WHERE c.relkind IN ('r','')" - it's only possible to list the ordinary tables. There are erroneous values in the case expression. > Using the PG protocol the Virtual View schema items are not visible > ------------------------------------------------------------------- > > Key: TEIID-5813 > URL: https://issues.jboss.org/browse/TEIID-5813 > Project: Teiid > Issue Type: Bug > Components: ODBC, Query Engine > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > > When using PSQL client against Teiid deployed VDB, the metadata does not show the tables/views that are defined under a virtual schema. The physical or foreign types are visible correctly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5813) Using the PG protocol the Virtual View schema items are not visible

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5813?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5813: ------------------------------------- with latest deployment on OpenShift I tried `\dt` I still did not see Views in the result. The query being sent is {code} SELECT n.nspname as "Schema", c.relname as "Name", CASE c.relkind WHEN 'r' THEN 'table' WHEN 'v' THEN 'view' WHEN 'm' THEN 'materialized view' WHEN 'i' THEN 'index' WHEN 'S' THEN 'sequence' WHEN 's' THEN 'special' WHEN 'f' THEN 'foreign table' END as "Type", pg_catalog.pg_get_userbyid(c.relowner) as "Owner" FROM pg_catalog.pg_class c LEFT JOIN pg_catalog.pg_namespace n ON n.oid = c.relnamespace WHERE c.relkind IN ('r','') AND n.nspname <> 'pg_catalog' AND n.nspname <> 'information_schema' AND n.nspname NOT LIKE_REGEX '^pg_toast' AND pg_catalog.pg_table_is_visible(c.oid) ORDER BY 1,2 {code} > Using the PG protocol the Virtual View schema items are not visible > ------------------------------------------------------------------- > > Key: TEIID-5813 > URL: https://issues.jboss.org/browse/TEIID-5813 > Project: Teiid > Issue Type: Bug > Components: ODBC, Query Engine > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > > When using PSQL client against Teiid deployed VDB, the metadata does not show the tables/views that are defined under a virtual schema. The physical or foreign types are visible correctly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5565) Drop client and other support for 1.6

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5565?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5565. ----------------------------------- Resolution: Done Updated the poms and the docs to drop 1.6 compatibility in the JDBC client. > Drop client and other support for 1.6 > ------------------------------------- > > Key: TEIID-5565 > URL: https://issues.jboss.org/browse/TEIID-5565 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Driver > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > Compatibility of the client/core code will need to be moved up to Java 8, while the project as a whole can move forward to Java 11. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5557) Restrict imports to a single schema

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5557?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5557: ---------------------------------- Fix Version/s: (was: 13.x) > Restrict imports to a single schema > ----------------------------------- > > Key: TEIID-5557 > URL: https://issues.jboss.org/browse/TEIID-5557 > Project: Teiid > Issue Type: Quality Risk > Components: Connector API > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > To better align with SQL/MED and to simplify legacy import properties it would be best to restrict foreign imports to a single schema. This will remove quite a bit of confusion around potential duplicate object names. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-121) cpu utilization on 100% when generate openapi doc by metadata

by Renat Eskenin (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-121?page=com.atlassian.jira.plugi... ] Renat Eskenin commented on TEIIDSB-121: --------------------------------------- 605kb Edm has 20000 strings typical propery <Property Name="system_modstamp" Type="Edm.DateTimeOffset" Nullable="false" DefaultValue="" Precision="6"> <Annotation Term="teiid.NAMEINSOURCE"> <String>"system_modstamp"</String> </Annotation> <Annotation Term="teiid.UPDATABLE"> <Bool>true</Bool> </Annotation> <Annotation Term="teiid.SIGNED"> <Bool>false</Bool> </Annotation> </Property> Many <EntitySet Name="fund" EntityType="vertica.af_fund"> <NavigationPropertyBinding Path="C_FOREIGN" Target="user"/> <NavigationPropertyBinding Path="C_FOREIGN_1" Target="user"/> <NavigationPropertyBinding Path="C_FOREIGN_2" Target="budget"/> <NavigationPropertyBinding Path="C_FOREIGN_3" Target="campaign_funds"/> <NavigationPropertyBinding Path="C_FOREIGN_4" Target="fund_request"/> </EntitySet> and many <NavigationProperty Name="account_C_FOREIGN_12" Type="Collection(vertica.account)"></NavigationProperty> Its all possible information...sorry. > cpu utilization on 100% when generate openapi doc by metadata > ------------------------------------------------------------- > > Key: TEIIDSB-121 > URL: https://issues.jboss.org/browse/TEIIDSB-121 > Project: Teiid Spring Boot > Issue Type: Bug > Components: datasource, OData > Affects Versions: 1.2.0 > Reporter: Renat Eskenin > Assignee: Steven Hawkins > Priority: Major > > When i get request as > http://localhost:8080/odata/swagger.json or http://localhost:8080/odata/datasource/Account/swagger.json or http://localhost:8080/odata/datasource/swagger.json > cpu utilization 100% and i do not get any response. > We have 2 bad approach: > 1. In org.teiid.olingo.web.OpenApiHandler:151 teiid create tmp file in filesystem. > Its bad because in Docker k8s systems applications can't create any files in FS. > 2. In org.apache.xalan.transformer.TransformerImpl:709 we get system freeze (CPU utilization 100% infinite) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-121) cpu utilization on 100% when generate openapi doc by metadata

by Renat Eskenin (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-121?page=com.atlassian.jira.plugi... ] Renat Eskenin commented on TEIIDSB-121: --------------------------------------- 1. 30MB is our external CMS db schema (full) 2. Sorry but i can't open our db schema (650kb) Its vertica db schema, may be it can help > cpu utilization on 100% when generate openapi doc by metadata > ------------------------------------------------------------- > > Key: TEIIDSB-121 > URL: https://issues.jboss.org/browse/TEIIDSB-121 > Project: Teiid Spring Boot > Issue Type: Bug > Components: datasource, OData > Affects Versions: 1.2.0 > Reporter: Renat Eskenin > Assignee: Steven Hawkins > Priority: Major > > When i get request as > http://localhost:8080/odata/swagger.json or http://localhost:8080/odata/datasource/Account/swagger.json or http://localhost:8080/odata/datasource/swagger.json > cpu utilization 100% and i do not get any response. > We have 2 bad approach: > 1. In org.teiid.olingo.web.OpenApiHandler:151 teiid create tmp file in filesystem. > Its bad because in Docker k8s systems applications can't create any files in FS. > 2. In org.apache.xalan.transformer.TransformerImpl:709 we get system freeze (CPU utilization 100% infinite) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 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