December 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5559) odata4 NPE when accessing VDB including FK relationship across models

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5559?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5559: --------------------------------------- This does appear allowable in odata - however our code structure makes it quite difficult. > odata4 NPE when accessing VDB including FK relationship across models > --------------------------------------------------------------------- > > Key: TEIID-5559 > URL: https://issues.jboss.org/browse/TEIID-5559 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12.16.6_4 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Priority: Major > > Receive error [2] when attempting to access table that utilizes a foreign key to another model with URL like [1]. access to the other model (that the foreign key references) works correctly. > [1] http://127.0.0.1:8080/odata4/fktest/fkmodel/ > [2] > JBWEB000309: type JBWEB000066: Exception report > JBWEB000068: message > JBWEB000069: description JBWEB000145: The server encountered an internal error that prevented it from fulfilling this request. > JBWEB000070: exception > org.teiid.core.TeiidRuntimeException > org.teiid.olingo.service.ODataSchemaBuilder.buildMetadata(ODataSchemaBuilder.java:58) > org.teiid.olingo.service.OlingoBridge.getHandler(OlingoBridge.java:54) > org.teiid.olingo.web.ODataFilter.internalDoFilter(ODataFilter.java:228) > org.teiid.olingo.web.ODataFilter.doFilter(ODataFilter.java:100) > org.teiid.olingo.web.CorsFilter.doFilter(CorsFilter.java:80) > JBWEB000071: root cause > java.lang.NullPointerException > org.teiid.olingo.service.ODataSchemaBuilder.addReverseNavigation(ODataSchemaBuilder.java:308) > org.teiid.olingo.service.ODataSchemaBuilder.buildNavigationProperties(ODataSchemaBuilder.java:251) > org.teiid.olingo.service.ODataSchemaBuilder.buildEntityTypes(ODataSchemaBuilder.java:144) > org.teiid.olingo.service.ODataSchemaBuilder.buildMetadata(ODataSchemaBuilder.java:54) > org.teiid.olingo.service.OlingoBridge.getHandler(OlingoBridge.java:54) > org.teiid.olingo.web.ODataFilter.internalDoFilter(ODataFilter.java:228) > org.teiid.olingo.web.ODataFilter.doFilter(ODataFilter.java:100) > org.teiid.olingo.web.CorsFilter.doFilter(CorsFilter.java:80) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5559) odata4 NPE when accessing VDB including FK relationship across models

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5559?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5559: --------------------------------------- This still occurs on master. I'm not sure if it's allowable in odata/olingo. > odata4 NPE when accessing VDB including FK relationship across models > --------------------------------------------------------------------- > > Key: TEIID-5559 > URL: https://issues.jboss.org/browse/TEIID-5559 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12.16.6_4 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Priority: Major > > Receive error [2] when attempting to access table that utilizes a foreign key to another model with URL like [1]. access to the other model (that the foreign key references) works correctly. > [1] http://127.0.0.1:8080/odata4/fktest/fkmodel/ > [2] > JBWEB000309: type JBWEB000066: Exception report > JBWEB000068: message > JBWEB000069: description JBWEB000145: The server encountered an internal error that prevented it from fulfilling this request. > JBWEB000070: exception > org.teiid.core.TeiidRuntimeException > org.teiid.olingo.service.ODataSchemaBuilder.buildMetadata(ODataSchemaBuilder.java:58) > org.teiid.olingo.service.OlingoBridge.getHandler(OlingoBridge.java:54) > org.teiid.olingo.web.ODataFilter.internalDoFilter(ODataFilter.java:228) > org.teiid.olingo.web.ODataFilter.doFilter(ODataFilter.java:100) > org.teiid.olingo.web.CorsFilter.doFilter(CorsFilter.java:80) > JBWEB000071: root cause > java.lang.NullPointerException > org.teiid.olingo.service.ODataSchemaBuilder.addReverseNavigation(ODataSchemaBuilder.java:308) > org.teiid.olingo.service.ODataSchemaBuilder.buildNavigationProperties(ODataSchemaBuilder.java:251) > org.teiid.olingo.service.ODataSchemaBuilder.buildEntityTypes(ODataSchemaBuilder.java:144) > org.teiid.olingo.service.ODataSchemaBuilder.buildMetadata(ODataSchemaBuilder.java:54) > org.teiid.olingo.service.OlingoBridge.getHandler(OlingoBridge.java:54) > org.teiid.olingo.web.ODataFilter.internalDoFilter(ODataFilter.java:228) > org.teiid.olingo.web.ODataFilter.doFilter(ODataFilter.java:100) > org.teiid.olingo.web.CorsFilter.doFilter(CorsFilter.java:80) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5560) Make Spring Boot port of Teiid library to support VDB deployment

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIID-5560: ----------------------------------- Summary: Make Spring Boot port of Teiid library to support VDB deployment Key: TEIID-5560 URL: https://issues.jboss.org/browse/TEIID-5560 Project: Teiid Issue Type: Feature Request Components: spring-boot Reporter: Ramesh Reddy Assignee: Ramesh Reddy Spring Boot majorly focuses on the JPA style programming for data virtualization where it gives developers the ability to define the Entity model whereby the VDB internals required are automatically generated deployed. In addition to the above, this library also should provide ways to deploy an existing VDB as Thorntail/WildFly does. There should be a process defined to take VDB and create an immutable process with it. It is expected to be used in the generation of OpenShift images for Teiid. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 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 commented on TEIID-5557: --------------------------------------- Importing from a single schema would remove the need for the useFullSchemaName property and restrict the notion of useQualifiedName and useCatalogName to only the name in source. useCatalogName would be rarely needed and useQualifedName would only be set to false in circumstances where the source schema name may change - some multi-source scenarios, or in circumstances where the schema changes between environments. > 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: 12.x, 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.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5558) Clarify jdbc name related import properties

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5558?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5558: ---------------------------------- Fix Version/s: 12.0 > Clarify jdbc name related import properties > ------------------------------------------- > > Key: TEIID-5558 > URL: https://issues.jboss.org/browse/TEIID-5558 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0 > > > useFullSchemaName is not well named and leads to confusion with useQualifiedName -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5558) Clarify jdbc name related import properties

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5558?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5558. ----------------------------------- Resolution: Done Given we will work towards TEIID-5557, I changed this into just a documentation update that clarifies when to set properties. The doc for use procedure specific name was removed as that property to my knowledge is not useful. > Clarify jdbc name related import properties > ------------------------------------------- > > Key: TEIID-5558 > URL: https://issues.jboss.org/browse/TEIID-5558 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > > useFullSchemaName is not well named and leads to confusion with useQualifiedName -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5558) Clarify jdbc name related import properties

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5558?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5558: ---------------------------------- Summary: Clarify jdbc name related import properties (was: Create a better property for useFullSchemaName) > Clarify jdbc name related import properties > ------------------------------------------- > > Key: TEIID-5558 > URL: https://issues.jboss.org/browse/TEIID-5558 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > > useFullSchemaName is not well named and leads to confusion with useQualifiedName -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5559) odata4 NPE when accessing VDB including FK relationship across models

by Marc Shirley (Jira)

Marc Shirley created TEIID-5559: ----------------------------------- Summary: odata4 NPE when accessing VDB including FK relationship across models Key: TEIID-5559 URL: https://issues.jboss.org/browse/TEIID-5559 Project: Teiid Issue Type: Bug Components: OData Affects Versions: 8.12.16.6_4 Reporter: Marc Shirley Assignee: Steven Hawkins Receive error [2] when attempting to access table that utilizes a foreign key to another model with URL like [1]. access to the other model (that the foreign key references) works correctly. [1] http://127.0.0.1:8080/odata4/fktest/fkmodel/ [2] JBWEB000309: type JBWEB000066: Exception report JBWEB000068: message JBWEB000069: description JBWEB000145: The server encountered an internal error that prevented it from fulfilling this request. JBWEB000070: exception org.teiid.core.TeiidRuntimeException org.teiid.olingo.service.ODataSchemaBuilder.buildMetadata(ODataSchemaBuilder.java:58) org.teiid.olingo.service.OlingoBridge.getHandler(OlingoBridge.java:54) org.teiid.olingo.web.ODataFilter.internalDoFilter(ODataFilter.java:228) org.teiid.olingo.web.ODataFilter.doFilter(ODataFilter.java:100) org.teiid.olingo.web.CorsFilter.doFilter(CorsFilter.java:80) JBWEB000071: root cause java.lang.NullPointerException org.teiid.olingo.service.ODataSchemaBuilder.addReverseNavigation(ODataSchemaBuilder.java:308) org.teiid.olingo.service.ODataSchemaBuilder.buildNavigationProperties(ODataSchemaBuilder.java:251) org.teiid.olingo.service.ODataSchemaBuilder.buildEntityTypes(ODataSchemaBuilder.java:144) org.teiid.olingo.service.ODataSchemaBuilder.buildMetadata(ODataSchemaBuilder.java:54) org.teiid.olingo.service.OlingoBridge.getHandler(OlingoBridge.java:54) org.teiid.olingo.web.ODataFilter.internalDoFilter(ODataFilter.java:228) org.teiid.olingo.web.ODataFilter.doFilter(ODataFilter.java:100) org.teiid.olingo.web.CorsFilter.doFilter(CorsFilter.java:80) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5558) Create a better property for useFullSchemaName

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5558: ------------------------------------- Summary: Create a better property for useFullSchemaName Key: TEIID-5558 URL: https://issues.jboss.org/browse/TEIID-5558 Project: Teiid Issue Type: Quality Risk Components: JDBC Connector Reporter: Steven Hawkins Assignee: Steven Hawkins useFullSchemaName is not well named and leads to confusion with useQualifiedName -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

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

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5557: ------------------------------------- Summary: 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 Fix For: 13.0, 12.x 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.12.1#712002)

5 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2018