March 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIIDSB-179) Alter / drop will not work with vdb plugin

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-179?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-179: --------------------------------- Description: The parsing of the VDB file needs to be done sequentially one statement at a time so that we can inline the VDB-Import in the order they are defined, and this also sequences any IMPORT FOREIGN SCHEMA statements in the order they are expected. (was: If you use an alter / drop in the vdb.ddl the result will be an illegalstateexception: {code} Caused by: java.lang.IllegalStateException: TransformationMetadata not yet available at org.teiid.maven.VdbMojoTest.test(VdbMojoTest.java:53) {code}) > Alter / drop will not work with vdb plugin > ------------------------------------------ > > Key: TEIIDSB-179 > URL: https://issues.redhat.com/browse/TEIIDSB-179 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: core > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > > The parsing of the VDB file needs to be done sequentially one statement at a time so that we can inline the VDB-Import in the order they are defined, and this also sequences any IMPORT FOREIGN SCHEMA statements in the order they are expected. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-179) Alter / drop will not work with vdb plugin

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIIDSB-179: ------------------------------------ Summary: Alter / drop will not work with vdb plugin Key: TEIIDSB-179 URL: https://issues.redhat.com/browse/TEIIDSB-179 Project: Teiid Spring Boot Issue Type: Quality Risk Components: core Reporter: Steven Hawkins Assignee: Ramesh Reddy Fix For: 1.4.0 If you use an alter / drop in the vdb.ddl the result will be an illegalstateexception: {code} Caused by: java.lang.IllegalStateException: TransformationMetadata not yet available at org.teiid.maven.VdbMojoTest.test(VdbMojoTest.java:53) {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-179) Alter / drop will not work with vdb plugin

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-179?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-179: --------------------------------- Story Points: (was: 1) > Alter / drop will not work with vdb plugin > ------------------------------------------ > > Key: TEIIDSB-179 > URL: https://issues.redhat.com/browse/TEIIDSB-179 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: core > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > > If you use an alter / drop in the vdb.ddl the result will be an illegalstateexception: > {code} > Caused by: java.lang.IllegalStateException: TransformationMetadata not yet available > at org.teiid.maven.VdbMojoTest.test(VdbMojoTest.java:53) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-179) Alter / drop will not work with vdb plugin

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-179?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-179: --------------------------------- Issue Type: Enhancement (was: Quality Risk) > Alter / drop will not work with vdb plugin > ------------------------------------------ > > Key: TEIIDSB-179 > URL: https://issues.redhat.com/browse/TEIIDSB-179 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: core > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > > If you use an alter / drop in the vdb.ddl the result will be an illegalstateexception: > {code} > Caused by: java.lang.IllegalStateException: TransformationMetadata not yet available > at org.teiid.maven.VdbMojoTest.test(VdbMojoTest.java:53) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-179) Alter / drop will not work with vdb plugin

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-179?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-179: --------------------------------- Fix Version/s: (was: 1.4.0) > Alter / drop will not work with vdb plugin > ------------------------------------------ > > Key: TEIIDSB-179 > URL: https://issues.redhat.com/browse/TEIIDSB-179 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: core > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > > If you use an alter / drop in the vdb.ddl the result will be an illegalstateexception: > {code} > Caused by: java.lang.IllegalStateException: TransformationMetadata not yet available > at org.teiid.maven.VdbMojoTest.test(VdbMojoTest.java:53) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-178) Accommodate the changes required for translator name change from Swagger to OpenAPI

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-178?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-178: --------------------------------- Original Estimate: 0 minutes Story Points: 1 > Accommodate the changes required for translator name change from Swagger to OpenAPI > ----------------------------------------------------------------------------------- > > Key: TEIIDSB-178 > URL: https://issues.redhat.com/browse/TEIIDSB-178 > Project: Teiid Spring Boot > Issue Type: Bug > Components: core > Affects Versions: 1.3.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.4.0 > > Original Estimate: 0 minutes > Time Spent: 6 hours > Remaining Estimate: 0 minutes > > The dependency is listed as translator-swagger, we should use "translator-openapi" -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-152) Alter / drop will not work with vdb plugin

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-152?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-152: --------------------------------- Story Points: 1 > Alter / drop will not work with vdb plugin > ------------------------------------------ > > Key: TEIIDSB-152 > URL: https://issues.redhat.com/browse/TEIIDSB-152 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: core > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.4.0 > > > If you use an alter / drop in the vdb.ddl the result will be an illegalstateexception: > {code} > Caused by: java.lang.IllegalStateException: TransformationMetadata not yet available > at org.teiid.maven.VdbMojoTest.test(VdbMojoTest.java:53) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-51) Define expectations for runtime metadata

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-51?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIIDSB-51: -------------------------------- Story Points: 1 > Define expectations for runtime metadata > ---------------------------------------- > > Key: TEIIDSB-51 > URL: https://issues.redhat.com/browse/TEIIDSB-51 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: documentation > Reporter: Steven Hawkins > Priority: Major > Fix For: 1.4.0 > > > At a high level there are potentially three modes for our ddl: > 1. Interactive - there was some work toward this, but it needed to only be a "developer mode" as it would reload the vdb on each metadata change. There is a lot about the transactionality of DDL updates that our current simplistic metadata model does not support, which makes this hard to fully implement. We haven't talked about this much in relation to Teiid Spring Boot, but ideally there should be a way for developers to test incremental changes without full rebuilds. > 2. Dynamic - the term is a bit dated, but this refers to any vdb that performs import from a metadata repository that has runtime dependencies. By design this allows for a simple vdb definition and options for caching or re-importing on reload. In a container environment metadata caching no longer makes sense unless we use a volume. Depending upon your viewpoint allowing for runtime import of metadata is potentially a point of mutability that is also not needed in a container environment. > 3. Static - much like our old .index designer vdbs there are benefits to having the full metadata already available to the vdb/image. There is a lot of work that we do lazily at runtime that can be moved to an earlier phase - primarily generating the rest and odata layers, but it would also include the pg system table materializations. For Teiid Spring Boot or usage in containers in general what this would look like is a build phase for the vdb such that it could obtain appropriate metadata and initialize as much as possible statically (eventually for quarkus vm snapshotting). The only metadata that would not be fresh potentially would be the costing metadata - however that is problematic as is and will eventually need a progressive optimization strategy employing a persistent store. > As of now we are currently focused just on #2. As we look toward operators, we should start thinking about #3. > #1 would come into play if/when we start looking at local development options using vs code. > We can treat this issue as an epic and a place to centralize discussion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5921) Add support for the latest Npgsql version

by Luca Castelluzzo (Jira)

Luca Castelluzzo created TEIID-5921: --------------------------------------- Summary: Add support for the latest Npgsql version Key: TEIID-5921 URL: https://issues.redhat.com/browse/TEIID-5921 Project: Teiid Issue Type: Enhancement Components: ODBC Affects Versions: 12.3.2 Reporter: Luca Castelluzzo Assignee: Steven Hawkins As reported [here|https://stackoverflow.com/questions/59970391/teiid-deprecated-floati...], Teiid PostgreSQL emulation can't be accessed with the latest version of Npgsql. It would be a desirable feature. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5920) Update dependencies in order to build in PNC for the .next release

by Van Halbert (Jira)

[ https://issues.redhat.com/browse/TEIID-5920?page=com.atlassian.jira.plugi... ] Van Halbert edited comment on TEIID-5920 at 3/19/20 7:53 AM: ------------------------------------------------------------- [ERROR] Found a problem with the dependency javax.validation:validation-api Resolved version is 2.0.1.Final Version 2.0.1.Final-redhat-1 was expected by artifact: org.teiid.connectors:translator-openapi Will be updating teiid to 201.Final-redhat-1. - Changing to use the pipeline overrides, as this is pulled from MRCC. No change to teiid is now targeted for this issue. Currently testing thru PNC build. was (Author: rhn-engineering-vhalbert): [ERROR] Found a problem with the dependency javax.validation:validation-api Resolved version is 2.0.1.Final Version 2.0.1.Final-redhat-1 was expected by artifact: org.teiid.connectors:translator-openapi Will be updating teiid to 201.Final-redhat-1. > Update dependencies in order to build in PNC for the .next release > ------------------------------------------------------------------- > > Key: TEIID-5920 > URL: https://issues.redhat.com/browse/TEIID-5920 > Project: Teiid > Issue Type: Quality Risk > Components: Build/Kits > Affects Versions: 13.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > > In order to build in PNC, certain dependency alignments are required in order to build. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2020