December 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4498) Generalize subquery batch processing

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-4498?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4498: --------------------------------------- The first issue with select subquery handling is that when subquery unnest defaults to true, we can plan a join plan. If it's false there isn't the later handling of the subquery - which is in RuleMergeCriteria for where subqueries. > Generalize subquery batch processing > ------------------------------------ > > Key: TEIID-4498 > URL: https://issues.jboss.org/browse/TEIID-4498 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0 > > > For subqueries that cannot be unnested, but can be modified to project their correlation, we should have at least batch processing rather than the row by row default. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

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

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5509?page=com.atlassian.jira.plugin... ] Work on TEIID-5509 stopped by Steven Hawkins. --------------------------------------------- > Ensure compatibility with vert.x postgresql client > -------------------------------------------------- > > Key: TEIID-5509 > URL: https://issues.jboss.org/browse/TEIID-5509 > Project: Teiid > Issue Type: Task > Components: ODBC > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > 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.12.1#712002)

7 years, 4 months

1
0
0 / 0

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

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5509?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5509: ---------------------------------- Fix Version/s: 12.1 (was: 12.0) Moving to 12.1. The async driver is based upon a project that is no longer maintained. It's not clear if this will be a supported connection path. > Ensure compatibility with vert.x postgresql client > -------------------------------------------------- > > Key: TEIID-5509 > URL: https://issues.jboss.org/browse/TEIID-5509 > Project: Teiid > Issue Type: Task > Components: ODBC > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > 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.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5508) Add community docs around openshift usage

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5508?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5508: ---------------------------------- Fix Version/s: 12.1 (was: 12.0) Priority: Minor (was: Major) Affects: Documentation (Ref Guide, User Guide, etc.) Pulling out of 12.0 as it's a low priority to articulate our non-product, non-syndesis openshift positioning. > Add community docs around openshift usage > ----------------------------------------- > > Key: TEIID-5508 > URL: https://issues.jboss.org/browse/TEIID-5508 > Project: Teiid > Issue Type: Quality Risk > Components: Documentation > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 12.1 > > > We should expand upon docker dealing with running Teiid in a container to reference more about running in openshift - in particular how that affects cluster, load balancing, what health checks can be used, etc. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-219) Add a way to limit or suppress queries that exceed a threshold Cost-Based Optimizer value

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-219?page=com.atlassian.jira.plugin.... ] Work on TEIID-219 started by Steven Hawkins. -------------------------------------------- > Add a way to limit or suppress queries that exceed a threshold Cost-Based Optimizer value > ----------------------------------------------------------------------------------------- > > Key: TEIID-219 > URL: https://issues.jboss.org/browse/TEIID-219 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Server > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0 > > > Client requesting an ability to impose a limit on, or suppress, any query that exceeds a cost estimate value specified by the user/administrator. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5555) Create OpenAPI (swagger) metadata document based on OData

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5555?page=com.atlassian.jira.plugin... ] Ramesh Reddy edited comment on TEIID-5555 at 12/6/18 12:11 PM: --------------------------------------------------------------- Yes, it is put out by one of the TC guys. It may have an earlier version that supports 2.0 (does not look like he did tag before cutting over to 3.0). The reason to go after 2.0 is the current support of swagger in 3scale is 2.0, which is supposed to move to 3.0 in the next couple of quarters I believe. was (Author: rareddy): Yes, it is put out by one of the TC guys. It may have an earlier version that supports 2.0. The reason to go after 2.0 is the current support of swagger in 3scale is 2.0, which is supposed to move to 3.0 in the next couple of quarters I believe. > Create OpenAPI (swagger) metadata document based on OData > --------------------------------------------------------- > > Key: TEIID-5555 > URL: https://issues.jboss.org/browse/TEIID-5555 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 12.1, 11.2.2 > > > Automatically generate Swagger metadata document based on OData metadata such the tools like 3Scale can understand the metadata through existing plugins until OData specific plugin is generated. Only swagger 2.0 document is considered for now. 3.0 support is not considered. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5562) Move the Teiid BOM from project-integration-bom into the Teiid project

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5562?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5562. ----------------------------------- Resolution: Done Marking as resolved. We'll update to 11.2.x when Van completes the backport. > Move the Teiid BOM from project-integration-bom into the Teiid project > ---------------------------------------------------------------------- > > Key: TEIID-5562 > URL: https://issues.jboss.org/browse/TEIID-5562 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Affects Versions: 12.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > Fix For: 12.0 > > > The project-integration-bom project usefulness never materialized, so the teiid bom will be moved back into the Teiid project to simplify dependency. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5555) Create OpenAPI (swagger) metadata document based on OData

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5555?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5555: ------------------------------------- Yes, it is put out by one of the TC guys. It may have an earlier version that supports 2.0. The reason to go after 2.0 is the current support of swagger in 3scale is 2.0, which is supposed to move to 3.0 in the next couple of quarters I believe. > Create OpenAPI (swagger) metadata document based on OData > --------------------------------------------------------- > > Key: TEIID-5555 > URL: https://issues.jboss.org/browse/TEIID-5555 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 12.1, 11.2.2 > > > Automatically generate Swagger metadata document based on OData metadata such the tools like 3Scale can understand the metadata through existing plugins until OData specific plugin is generated. Only swagger 2.0 document is considered for now. 3.0 support is not considered. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5555) Create OpenAPI (swagger) metadata document based on OData

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5555?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5555: --------------------------------------- https://github.com/oasis-tcs/odata-openapi looks to be the most promising starting point. It's for openapi 3 - is there a reason you want 2.0 support? This work seems to account for most of my concerns. It generates explicit paths to two entity levels and shows all possible odata url parameters for each path. It also shows the full result entity, such that usage of expand would be accounted for. $expand though seems limited - as the openapi does not seem to describe using query options in parens in the expand e.g. {code}$expand=*($levels=1){code} So it's very verbose, but does a reasonable job of representing the api. > Create OpenAPI (swagger) metadata document based on OData > --------------------------------------------------------- > > Key: TEIID-5555 > URL: https://issues.jboss.org/browse/TEIID-5555 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 12.1, 11.2.2 > > > Automatically generate Swagger metadata document based on OData metadata such the tools like 3Scale can understand the metadata through existing plugins until OData specific plugin is generated. Only swagger 2.0 document is considered for now. 3.0 support is not considered. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5562) Move the Teiid BOM from project-integration-bom into the Teiid project

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5562?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-5562: ------------------------------------ Getting off of the project-integration-repo was the main goal with this first step. The next will be to back port to 11 > Move the Teiid BOM from project-integration-bom into the Teiid project > ---------------------------------------------------------------------- > > Key: TEIID-5562 > URL: https://issues.jboss.org/browse/TEIID-5562 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Affects Versions: 12.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > Fix For: 12.0 > > > The project-integration-bom project usefulness never materialized, so the teiid bom will be moved back into the Teiid project to simplify dependency. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 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 December 2018