April 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5712) Hidden metadata is inconsistent over pg

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5712?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5712: ---------------------------------- Fix Version/s: 11.2.3 12.0.2 12.1.1 > Hidden metadata is inconsistent over pg > --------------------------------------- > > Key: TEIID-5712 > URL: https://issues.jboss.org/browse/TEIID-5712 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 10.1.1, 10.2 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2, 11.2.3, 12.0.2, 12.1.1 > > > With TEIID-5533 the materialization of pg_attribute will expose all columns to any user. With TEIID-5236 the lazy materialization of pg_index and TEIID-5696 pg_proc will cache the results only for the initial user. > The materialization needs to be performed in a safer way to preserve the hidden metadata. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5712) Hidden metadata is inconsistent over pg

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5712?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5712. ----------------------------------- Resolution: Done Removed the pg_catalog materializations that could be on metadata that has visibility considerations. > Hidden metadata is inconsistent over pg > --------------------------------------- > > Key: TEIID-5712 > URL: https://issues.jboss.org/browse/TEIID-5712 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 10.1.1, 10.2 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2 > > > With TEIID-5533 the materialization of pg_attribute will expose all columns to any user. With TEIID-5236 the lazy materialization of pg_index and TEIID-5696 pg_proc will cache the results only for the initial user. > The materialization needs to be performed in a safer way to preserve the hidden metadata. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4251) Built in support for Postgres DB as materialization target

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-4251?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4251: ------------------------------------- > The only thing we could do is have a single pg instance have multiple databases - which is not something the default install is setup to do. This is the setting I am thinking of, I believe we have root pg credentials to create more databases. We have to check out the PG's operator, it may have something there? Or should become a task in our operator somehow? > What do you mean by implicitly trusted over service? I was meaning no security, as it is intracluster and trust the client app. But trusting over the certificate is the correct way. > Built in support for Postgres DB as materialization target > ---------------------------------------------------------- > > Key: TEIID-4251 > URL: https://issues.jboss.org/browse/TEIID-4251 > Project: Teiid > Issue Type: Sub-task > Components: Server > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2 > > > If Postgres database is available along with install or assumed that it is available, then some of the materialization task can be automated, like > - Creation of a common STATUS table > - Creation of the materilization targets (create views on dbms) > - On load, on undeploy and load scripts for all the materialization views > We need to device a way this to be pluggable, such that based on success of this, we can provide additional support for other sources. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5712) Hidden metadata is inconsistent over pg

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5712?page=com.atlassian.jira.plugin... ] Work on TEIID-5712 started by Steven Hawkins. --------------------------------------------- > Hidden metadata is inconsistent over pg > --------------------------------------- > > Key: TEIID-5712 > URL: https://issues.jboss.org/browse/TEIID-5712 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 10.1.1, 10.2 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2 > > > With TEIID-5533 the materialization of pg_attribute will expose all columns to any user. With TEIID-5236 the lazy materialization of pg_index and TEIID-5696 pg_proc will cache the results only for the initial user. > The materialization needs to be performed in a safer way to preserve the hidden metadata. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5712) Hidden metadata is inconsistent over pg

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5712: ------------------------------------- Summary: Hidden metadata is inconsistent over pg Key: TEIID-5712 URL: https://issues.jboss.org/browse/TEIID-5712 Project: Teiid Issue Type: Bug Components: ODBC Affects Versions: 10.2, 10.1.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 12.2 With TEIID-5533 the materialization of pg_attribute will expose all columns to any user. With TEIID-5236 the lazy materialization of pg_index and TEIID-5696 pg_proc will cache the results only for the initial user. The materialization needs to be performed in a safer way to preserve the hidden metadata. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5711) isolate references to JEE concerns, such as jca

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5711: ------------------------------------- Summary: isolate references to JEE concerns, such as jca Key: TEIID-5711 URL: https://issues.jboss.org/browse/TEIID-5711 Project: Teiid Issue Type: Sub-task Components: Documentation Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 12.2 We refer to JCA resource adapters even in the reference guide. This and other JEE concepts should be isolated to the wildfly docs. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5710) Create remaining spring docs

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5710: ------------------------------------- Summary: Create remaining spring docs Key: TEIID-5710 URL: https://issues.jboss.org/browse/TEIID-5710 Project: Teiid Issue Type: Sub-task Components: Documentation Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 12.2 Presuming that the embedded, dev, and security docs will all be available as part of their respective code (javadocs and examples), that leaves admin, caching, and client-dev as the remaining books that need a spring specific spin. Most of the admin guide is not applicable - but we do need to capture somewhere all of the information related to system/env properties Most of the caching guide is TBD - but the sections on result set and other caching are still applicable. Most of the client guide is applicable to spring. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5709) Consistent character handling beyond bmp

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5709: ------------------------------------- Summary: Consistent character handling beyond bmp Key: TEIID-5709 URL: https://issues.jboss.org/browse/TEIID-5709 Project: Teiid Issue Type: Bug Components: Server Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 12.2 There are many places in the code that only consider each 16 bit character when we should consult the full code point. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4251) Built in support for Postgres DB as materialization target

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-4251?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4251: --------------------------------------- > fdw settings are not per pg database? or their fdw settings are global? See the sql above. The settings are per server: CREATE SERVER teiid_server FOREIGN DATA WRAPPER postgres_fdw OPTIONS (host 'TEIID_SERVICE_HOST', port 'TEIID_SERVICE_PORT', dbname 'VDB'); -- note, this performs no initial validation CREATE USER MAPPING FOR pg_user SERVER teiid_server OPTIONS (user 'TEIID_SECRET_USER', password 'TEIID_SECRET_PASSWORD'); > My only concern is the proliferation of a number of pg instances in a given cluster. The only thing we could do is have a single pg instance have multiple databases - which is not something the default install is setup to do. > Maybe we can put in an assumption/limitation over the schema names and find a way to warn or fail? Without a patch of the pg fdw there's nothing we can do. The logic expects the local schema name to be the same at remote. > I agree that we start with the snapshot refresh, when we are ready to work with CDC we can revisit choices available. With pg managed materialization there are no additional choices as of yet. It's only a full refresh - that can be manual, timed, or if we retain a status table based upon some update threshold. > As per the connectivity from PG to Teiid, can it not be implicitly trusted over service? if not yes a certificate based auth need to be devised. That may be useful in general with any other jdbc/odbc client from the within the cluster. What do you mean by implicitly trusted over service? I'm saying that boils down to client ip or certificate (either of which would need additional logic). > Built in support for Postgres DB as materialization target > ---------------------------------------------------------- > > Key: TEIID-4251 > URL: https://issues.jboss.org/browse/TEIID-4251 > Project: Teiid > Issue Type: Sub-task > Components: Server > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2 > > > If Postgres database is available along with install or assumed that it is available, then some of the materialization task can be automated, like > - Creation of a common STATUS table > - Creation of the materilization targets (create views on dbms) > - On load, on undeploy and load scripts for all the materialization views > We need to device a way this to be pluggable, such that based on success of this, we can provide additional support for other sources. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4251) Built in support for Postgres DB as materialization target

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-4251?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4251: ------------------------------------- > The biggest multi-tenet issue using the direct pg fdw integration is the imported schema name limitation fdw settings are not per pg database? or their fdw settings are global? My only concern is the proliferation of a number of pg instances in a given cluster. Maybe we can put in an assumption/limitation over the schema names and find a way to warn or fail? I agree that we start with the snapshot refresh, when we are ready to work with CDC we can revisit choices available. As per the connectivity from PG to Teiid, can it not be implicitly trusted over service? if not yes a certificate based auth need to be devised. That may be useful in general with any other jdbc/odbc client from the within the cluster. > Built in support for Postgres DB as materialization target > ---------------------------------------------------------- > > Key: TEIID-4251 > URL: https://issues.jboss.org/browse/TEIID-4251 > Project: Teiid > Issue Type: Sub-task > Components: Server > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2 > > > If Postgres database is available along with install or assumed that it is available, then some of the materialization task can be automated, like > - Creation of a common STATUS table > - Creation of the materilization targets (create views on dbms) > - On load, on undeploy and load scripts for all the materialization views > We need to device a way this to be pluggable, such that based on success of this, we can provide additional support for other sources. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2019