November 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIIDSB-138) Openapi metadata from odata has invalid paths

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-138?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIIDSB-138. ------------------------------------ Resolution: Done Updated the logic to pass in the the full uri which includes the context. > Openapi metadata from odata has invalid paths > --------------------------------------------- > > Key: TEIIDSB-138 > URL: https://issues.jboss.org/browse/TEIIDSB-138 > Project: Teiid Spring Boot > Issue Type: Bug > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 1.3.0 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > The uri passed into the openapihandler is relative to the context, so the basepath (v2 metadata) is given as an empty string, or the server url (v3 metadata) does not include the context. Either way the resulting doc is invalid. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-138) Openapi metadata from odata has invalid paths

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-138?page=com.atlassian.jira.plugi... ] Work on TEIIDSB-138 started by Steven Hawkins. ---------------------------------------------- > Openapi metadata from odata has invalid paths > --------------------------------------------- > > Key: TEIIDSB-138 > URL: https://issues.jboss.org/browse/TEIIDSB-138 > Project: Teiid Spring Boot > Issue Type: Bug > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 1.3.0 > > > The uri passed into the openapihandler is relative to the context, so the basepath (v2 metadata) is given as an empty string, or the server url (v3 metadata) does not include the context. Either way the resulting doc is invalid. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-138) Openapi metadata from odata has invalid paths

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-138?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIIDSB-138: ----------------------------------- Original Estimate: 2 hours Remaining Estimate: 2 hours Estimated Difficulty: Low > Openapi metadata from odata has invalid paths > --------------------------------------------- > > Key: TEIIDSB-138 > URL: https://issues.jboss.org/browse/TEIIDSB-138 > Project: Teiid Spring Boot > Issue Type: Bug > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 1.3.0 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > The uri passed into the openapihandler is relative to the context, so the basepath (v2 metadata) is given as an empty string, or the server url (v3 metadata) does not include the context. Either way the resulting doc is invalid. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5853) Solr Connector builder url null

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5853?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5853. ----------------------------------- Fix Version/s: 13.0 12.2.2 12.3.1 Resolution: Done Thanks for bringing this to our attention. > Solr Connector builder url null > ------------------------------- > > Key: TEIID-5853 > URL: https://issues.jboss.org/browse/TEIID-5853 > Project: Teiid > Issue Type: Bug > Components: Connector API > Affects Versions: 12.3.1 > Reporter: german tejero > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0, 12.2.2, 12.3.1 > > > Solr JCA connector does not pass the configured url -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-139) Remove the usage of dummy create foreign data wrapper statements

by Steven Hawkins (Jira)

Steven Hawkins created TEIIDSB-139: -------------------------------------- Summary: Remove the usage of dummy create foreign data wrapper statements Key: TEIIDSB-139 URL: https://issues.jboss.org/browse/TEIIDSB-139 Project: Teiid Spring Boot Issue Type: Task Reporter: Steven Hawkins Assignee: Ramesh Reddy Fix For: 1.3.0 With the upgrade to Teiid 13 we should remove create foreign data wrapper statements that do not define a type as they are redundant. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5850) DDL server and foreign data wrapper handling is unclear

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5850?focusedWorklogId=12448107&page... ] Steven Hawkins logged work on TEIID-5850: ----------------------------------------- Author: Steven Hawkins Created on: 21/Nov/19 4:20 PM Start Date: 21/Nov/19 4:19 PM Worklog Time Spent: 4 hours Issue Time Tracking ------------------- Remaining Estimate: 2 hours (was: 6 hours) Time Spent: 4 hours Worklog Id: (was: 12448107) > DDL server and foreign data wrapper handling is unclear > ------------------------------------------------------- > > Key: TEIID-5850 > URL: https://issues.jboss.org/browse/TEIID-5850 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > Original Estimate: 6 hours > Time Spent: 4 hours > Remaining Estimate: 2 hours > > CREATE server statements in DDL are effectively ignored in the conversion to runtime state - they are simply validated. Similarly a CREATE foreign data wrapper statement that does not specify a type is ignored. > Attempting to do something like: > {code} > CREATE FOREIGN DATA WRAPPER salesforce; > CREATE SERVER salesforce FOREIGN DATA WRAPPER salesforce OPTIONS ("resource-name" 'salesforce', supportsOrderBy true); > {code} > or > {code} > CREATE FOREIGN DATA WRAPPER salesforce OPTIONS (supportsOrderBy true); > CREATE SERVER salesforce FOREIGN DATA WRAPPER salesforce OPTIONS ("resource-name" 'salesforce'); > {code} > will not result in supportsOrderBy being set on the translator. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5850) DDL server and foreign data wrapper handling is unclear

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5850?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5850: ---------------------------------- Issue Type: Quality Risk (was: Bug) Priority: Major (was: Critical) > DDL server and foreign data wrapper handling is unclear > ------------------------------------------------------- > > Key: TEIID-5850 > URL: https://issues.jboss.org/browse/TEIID-5850 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > Original Estimate: 6 hours > Remaining Estimate: 6 hours > > CREATE server statements in DDL are effectively ignored in the conversion to runtime state - they are simply validated. Similarly a CREATE foreign data wrapper statement that does not specify a type is ignored. > Attempting to do something like: > {code} > CREATE FOREIGN DATA WRAPPER salesforce; > CREATE SERVER salesforce FOREIGN DATA WRAPPER salesforce OPTIONS ("resource-name" 'salesforce', supportsOrderBy true); > {code} > or > {code} > CREATE FOREIGN DATA WRAPPER salesforce OPTIONS (supportsOrderBy true); > CREATE SERVER salesforce FOREIGN DATA WRAPPER salesforce OPTIONS ("resource-name" 'salesforce'); > {code} > will not result in supportsOrderBy being set on the translator. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5850) DDL server and foreign data wrapper handling is unclear

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5850?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5850. ----------------------------------- Fix Version/s: (was: 12.2.2) (was: 12.3.1) Resolution: Done Since there was some documentation on the override, this is not as critical as it initially seemed. However we should not require dummy create foreign data wrapper statements, so the code is now tolerant to that. Docs have been updated to reflect this. > DDL server and foreign data wrapper handling is unclear > ------------------------------------------------------- > > Key: TEIID-5850 > URL: https://issues.jboss.org/browse/TEIID-5850 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 13.0 > > Original Estimate: 6 hours > Remaining Estimate: 6 hours > > CREATE server statements in DDL are effectively ignored in the conversion to runtime state - they are simply validated. Similarly a CREATE foreign data wrapper statement that does not specify a type is ignored. > Attempting to do something like: > {code} > CREATE FOREIGN DATA WRAPPER salesforce; > CREATE SERVER salesforce FOREIGN DATA WRAPPER salesforce OPTIONS ("resource-name" 'salesforce', supportsOrderBy true); > {code} > or > {code} > CREATE FOREIGN DATA WRAPPER salesforce OPTIONS (supportsOrderBy true); > CREATE SERVER salesforce FOREIGN DATA WRAPPER salesforce OPTIONS ("resource-name" 'salesforce'); > {code} > will not result in supportsOrderBy being set on the translator. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5854) Remove SYS.getXMLSchemas

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5854?focusedWorklogId=12448106&page... ] Steven Hawkins logged work on TEIID-5854: ----------------------------------------- Author: Steven Hawkins Created on: 21/Nov/19 3:56 PM Start Date: 21/Nov/19 3:56 PM Worklog Time Spent: 1 hour Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 1 hour) Time Spent: 1 hour Worklog Id: (was: 12448106) > Remove SYS.getXMLSchemas > ------------------------ > > Key: TEIID-5854 > URL: https://issues.jboss.org/browse/TEIID-5854 > Project: Teiid > Issue Type: Task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > Original Estimate: 1 hour > Time Spent: 1 hour > Remaining Estimate: 0 minutes > > The deprecated procedure can safely be removed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5854) Remove SYS.getXMLSchemas

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5854?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5854. ----------------------------------- Resolution: Done Updated the code and the docs to remove the procedure. > Remove SYS.getXMLSchemas > ------------------------ > > Key: TEIID-5854 > URL: https://issues.jboss.org/browse/TEIID-5854 > Project: Teiid > Issue Type: Task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The deprecated procedure can safely be removed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2019