February 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5751) Please add optimization support for foreign keys in materialized tables

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5751?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5751: ---------------------------------- Original Estimate: 2 hours, 30 minutes Remaining Estimate: 2 hours, 30 minutes > Please add optimization support for foreign keys in materialized tables > ----------------------------------------------------------------------- > > Key: TEIID-5751 > URL: https://issues.redhat.com/browse/TEIID-5751 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 12.2 > Reporter: Christoph John > Assignee: Steven Hawkins > Priority: Minor > Fix For: 13.1 > > Original Estimate: 2 hours, 30 minutes > Remaining Estimate: 2 hours, 30 minutes > > The issues came up in the following discussion > https://developer.jboss.org/message/989502#989502 > > 1a) Are the constraints (indexes, foreign keys) now used to optimize queries in materialized tables or not? > > Pk, Unique Key, and Indexes on the view will result in the creation of an index on the materialization target table and are fully utilized in planning decisions. Things are a little more complicated with foreign keys. {color:red}Currently they are not propagated onto the generated materialization target table metadata, so they are only considered in pre-planner activities, such as rewrite, before the view reference is replaced with the materialization target - but there aren't meaningful optimizations being made at that time based upon foreign key. There are couple of narrow situations where that information would be useful{color}, so it probably should be added. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5751) Please add optimization support for foreign keys in materialized tables

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5751?focusedWorklogId=12450343&pag... ] Steven Hawkins logged work on TEIID-5751: ----------------------------------------- Author: Steven Hawkins Created on: 27/Feb/20 5:11 PM Start Date: 27/Feb/20 5:11 PM Worklog Time Spent: 2 hours Issue Time Tracking ------------------- Remaining Estimate: 30 minutes (was: 2 hours, 30 minutes) Time Spent: 2 hours Worklog Id: (was: 12450343) > Please add optimization support for foreign keys in materialized tables > ----------------------------------------------------------------------- > > Key: TEIID-5751 > URL: https://issues.redhat.com/browse/TEIID-5751 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 12.2 > Reporter: Christoph John > Assignee: Steven Hawkins > Priority: Minor > Fix For: 13.1 > > Original Estimate: 2 hours, 30 minutes > Time Spent: 2 hours > Remaining Estimate: 30 minutes > > The issues came up in the following discussion > https://developer.jboss.org/message/989502#989502 > > 1a) Are the constraints (indexes, foreign keys) now used to optimize queries in materialized tables or not? > > Pk, Unique Key, and Indexes on the view will result in the creation of an index on the materialization target table and are fully utilized in planning decisions. Things are a little more complicated with foreign keys. {color:red}Currently they are not propagated onto the generated materialization target table metadata, so they are only considered in pre-planner activities, such as rewrite, before the view reference is replaced with the materialization target - but there aren't meaningful optimizations being made at that time based upon foreign key. There are couple of narrow situations where that information would be useful{color}, so it probably should be added. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5751) Please add optimization support for foreign keys in materialized tables

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5751?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-5751. ----------------------------------- Resolution: Done Added propagation of foreign keys from the materialized view to the internal materialization target. This does not yet address foreign keys from other tables to the materialization table - but that is a larger change. In either case it will be pretty narrow how this is used - for example in initial costing (before mat view load). > Please add optimization support for foreign keys in materialized tables > ----------------------------------------------------------------------- > > Key: TEIID-5751 > URL: https://issues.redhat.com/browse/TEIID-5751 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 12.2 > Reporter: Christoph John > Assignee: Steven Hawkins > Priority: Minor > Fix For: 13.1 > > > The issues came up in the following discussion > https://developer.jboss.org/message/989502#989502 > > 1a) Are the constraints (indexes, foreign keys) now used to optimize queries in materialized tables or not? > > Pk, Unique Key, and Indexes on the view will result in the creation of an index on the materialization target table and are fully utilized in planning decisions. Things are a little more complicated with foreign keys. {color:red}Currently they are not propagated onto the generated materialization target table metadata, so they are only considered in pre-planner activities, such as rewrite, before the view reference is replaced with the materialization target - but there aren't meaningful optimizations being made at that time based upon foreign key. There are couple of narrow situations where that information would be useful{color}, so it probably should be added. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5611) Add support for SCRAM-SHA-256

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5611?page=com.atlassian.jira.plugi... ] Work on TEIID-5611 started by Steven Hawkins. --------------------------------------------- > Add support for SCRAM-SHA-256 > ----------------------------- > > Key: TEIID-5611 > URL: https://issues.redhat.com/browse/TEIID-5611 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.1 > > > MongoDB has added support for a new security type, which needs additional support in the resource adapter. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5780) Support certificate based authentication into Teiid pg

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5780?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5780: ---------------------------------- Fix Version/s: 13.2 (was: 13.1) > Support certificate based authentication into Teiid pg > ------------------------------------------------------ > > Key: TEIID-5780 > URL: https://issues.redhat.com/browse/TEIID-5780 > Project: Teiid > Issue Type: Sub-task > Components: ODBC > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.2 > > Original Estimate: 2 days > Time Spent: 6 hours > Remaining Estimate: 1 day, 2 hours > > To support the pg connection into Teiid we will do something like: > - require a pg secure port using the service signing certificate: TEIIDSB-90 TEIIDSB-92 > -- one clarification is that we must document how to make the pg cert dominant if both pg and jdbc secure are used > TODO: > - configure the pg instance to have a service signing certificate and trust the Teiid service signing certificate. If that trust seems too difficult we can just configure the connection to trust all. > - configure the pg connection to Teiid to use the pg service signing certificate as the client certificate > - trust the pg service signing certificate at the teiid service - we need hostname validation to be enabled and the Teiid server to map the service host name to an authenticated user (this could possibly be generalized via keycloak support to more users). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5762) Update security configuration to elytron

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5762?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5762: ---------------------------------- Fix Version/s: 13.2 13.2 (was: 13.1) > Update security configuration to elytron > ---------------------------------------- > > Key: TEIID-5762 > URL: https://issues.redhat.com/browse/TEIID-5762 > Project: Teiid > Issue Type: Sub-task > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.2 > > > The Teiid configuration is based upon an out-dated version of the wildfly config. It should be brought up-to-date. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5736) General odata function mapping

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5736?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5736: ---------------------------------- Fix Version/s: 13.2 13.2 (was: 13.1) > General odata function mapping > ------------------------------ > > Key: TEIID-5736 > URL: https://issues.redhat.com/browse/TEIID-5736 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Priority: Major > Fix For: 13.2 > > > We are currently mapping procedures and functions defined by ddl to odata functions/actions. The latter is due that the function is represented in our system metadata as a procedure. We need to decide if all functions should be mapped. There's also the notion of a composable function that could be helpful. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5495) Add support for graphql sources

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5495?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5495: ---------------------------------- Fix Version/s: 13.2 13.2 (was: 13.1) > Add support for graphql sources > ------------------------------- > > Key: TEIID-5495 > URL: https://issues.redhat.com/browse/TEIID-5495 > Project: Teiid > Issue Type: Feature Request > Components: Connector API > Reporter: Steven Hawkins > Priority: Major > Fix For: 13.2 > > > We should create translator support for graphql, which will also help us evaluate supporting graphql as a front end as well. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5509) Ensure compatibility with vert.x postgresql client

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5509?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5509: ---------------------------------- Fix Version/s: 13.2 13.2 (was: 13.1) > Ensure compatibility with vert.x postgresql client > -------------------------------------------------- > > Key: TEIID-5509 > URL: https://issues.redhat.com/browse/TEIID-5509 > Project: Teiid > Issue Type: Task > Components: ODBC > Reporter: Steven Hawkins > Priority: Major > Fix For: 13.2 > > > Vert.x has support for a async/reactive pg client. We should ensure that works with our pg protocol. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5873) OData mapping issue with mongodb

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5873?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5873: ---------------------------------- Fix Version/s: 13.2 13.2 (was: 13.1) > OData mapping issue with mongodb > --------------------------------- > > Key: TEIID-5873 > URL: https://issues.redhat.com/browse/TEIID-5873 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors, OData > Affects Versions: 13.0.1 > Reporter: Chee Kin Lim > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.2 > > > Given the following document in MongoDB matrix_variable collection: > { > "_id" : ObjectId("5b2367c9c9e77c0007ca0111"), > "createdOn" : ISODate("2018-06-15T07:16:25.459Z"), > "modifiedOn" : ISODate("2018-07-02T02:04:16.661Z"), > "variableId" : "183cf101d2334ac09bd0db9aee96081f", > "name" : "lfzq_test", > "description" : "", > "lastModifiedUserEmail" : "admin1(a)abc.com", > "headerRow" : { > "rowId" : "0b002942a5b4424f98fcc270af0290c3", > "values" : [ > "name", > "value" > ], > "isEncrypted" : [ > false, > true > ] > }, > "rows" : [ > { > "rowId" : "940467f9bb724d1688086baeec05049b", > "values" : [ > "lfzq123q", > "751c634ca5e24102a00800b386955a5c" > ] > } > ], > "deleted" : false > } > The "headerRow" property is exposed as separate entity type in OData schema, but not "rows" property. > I found the following entity types with odata/$metadata: > <EntityType Name="headerRow">...</EntityType> > <EntityType Name="matrix_variable">...</EntityType> > Github repo to showcase the issue: > https://github.com/limcheekin/teiid-spring-boot-mongodb-odata > Related StackOverflow post: > https://stackoverflow.com/a/59385181/303211 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2020