February 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5662) Add option to Migration Utility to write to file

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5662?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-5662: ------------------------------------ Adding option to utility to now take 2 arguments: org.teiid.runtime.util.ConvertVDB pathToVDB [pathToOutputVDBFile] The second is optional, and when not included, the output will be written to sysout. > Add option to Migration Utility to write to file > ------------------------------------------------ > > Key: TEIID-5662 > URL: https://issues.jboss.org/browse/TEIID-5662 > Project: Teiid > Issue Type: Feature Request > Components: Tooling > Affects Versions: 12.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > > Add an option to the Migration Utility for writing the converted vdb to a file, which could include the path to persist it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

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 commented on TEIID-5508: --------------------------------------- This is effectively being done now just for the spring boot case. > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5647) reserve information_schema for future use

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5647?page=com.atlassian.jira.plugin... ] Work on TEIID-5647 started by Steven Hawkins. --------------------------------------------- > reserve information_schema for future use > ----------------------------------------- > > Key: TEIID-5647 > URL: https://issues.jboss.org/browse/TEIID-5647 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > Most vendors support the information_schema. We should reserve that schema name for internal use only - although there will be potential conflicts with the specialized pg_catalog.information_schema introduced for odbc. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5660) With the change to the basebom v25, brings in issue with javadoc override in pipeline build

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5660?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5660. ----------------------------------- Resolution: Done Merged the pr > With the change to the basebom v25, brings in issue with javadoc override in pipeline build > ------------------------------------------------------------------------------------------- > > Key: TEIID-5660 > URL: https://issues.jboss.org/browse/TEIID-5660 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 12.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > When the changes were committed last week that changed the basebom version to 25, it now causes a dependency issue with the javadoc override to 3.0.1. If I do the following: > {code} > <version.javadoc.plugin>${dep.plugin.javadoc.version}</version.javadoc.plugin> > {code} > It now builds. > Not sure what we're loosing by using version: 3.0.0-M1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5612) Switch to auto release

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5612?page=com.atlassian.jira.plugin... ] Work on TEIID-5612 started by Steven Hawkins. --------------------------------------------- > Switch to auto release > ---------------------- > > Key: TEIID-5612 > URL: https://issues.jboss.org/browse/TEIID-5612 > Project: Teiid > Issue Type: Enhancement > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > Just like the thorntail parent, we should just auto release from staging http://central.maven.org/maven2/io/thorntail/parent/10/parent-10.pom > There are additional settings covered there as well, which would eliminate the need to specify them on the command line. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5663) increase texttablenode synchronization

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5663: ------------------------------------- Summary: increase texttablenode synchronization Key: TEIID-5663 URL: https://issues.jboss.org/browse/TEIID-5663 Project: Teiid Issue Type: Quality Risk Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 12.1 Async work started by the texttablenode may be in process or process after reset. Typically this will create a npe which is just swallowed as an unreported async exception. However we should properly synchronizing close/reset and preventing any invalid async work. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5662) Add option to Migration Utility to write to file

by Van Halbert (Jira)

Van Halbert created TEIID-5662: ---------------------------------- Summary: Add option to Migration Utility to write to file Key: TEIID-5662 URL: https://issues.jboss.org/browse/TEIID-5662 Project: Teiid Issue Type: Feature Request Components: Tooling Affects Versions: 12.x Reporter: Van Halbert Assignee: Barry LaFond Add an option to the Migration Utility for writing the converted vdb to a file, which could include the path to persist it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5662) Add option to Migration Utility to write to file

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5662?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-5662: ---------------------------------- Assignee: Van Halbert (was: Barry LaFond) > Add option to Migration Utility to write to file > ------------------------------------------------ > > Key: TEIID-5662 > URL: https://issues.jboss.org/browse/TEIID-5662 > Project: Teiid > Issue Type: Feature Request > Components: Tooling > Affects Versions: 12.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > > Add an option to the Migration Utility for writing the converted vdb to a file, which could include the path to persist it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5657) VDB Migration Tool

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5657?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-5657: ---------------------------------- Assignee: Van Halbert (was: Ramesh Reddy) > VDB Migration Tool > ------------------ > > Key: TEIID-5657 > URL: https://issues.jboss.org/browse/TEIID-5657 > Project: Teiid > Issue Type: Feature Request > Components: Documentation, Quick Starts, Tooling > Affects Versions: 12.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > > A migration tool will be provided to convert customer vdbs into just ddl. More than likely this will be just a single ddl file - which will probably not be acceptable to customers with large vdbs. > We have this utility already available as just a main method in one of our jars. It is anticipated that a maven repo will be distribution mechanism and minimal documentation will be provided. > There should be optional validation available for the vdb ddl at build time. This breaks down into 3 parts: > 1. static syntactic validation, potentially even fully resolving if all metadata is present. This makes sure that basic typos will be caught. > 2. providing hard errors for things that are completely removed - an error for usage of soap or function models for example. > 3. providing errors or warning for features that are not yet available - vdb imports, sources that aren't yet supported etc. > To avoid introducing a new plugin or plugging into fmp it's been suggested that the validation could be run via a generated unit test, which ties into another task which is booster, base project, or last resort an arche type that scaffolds the developer project. > This could possibly be included in the quickstarts as a means to facilitate its use. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5657) VDB Migration Tool

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5657?page=com.atlassian.jira.plugin... ] Work on TEIID-5657 started by Van Halbert. ------------------------------------------ > VDB Migration Tool > ------------------ > > Key: TEIID-5657 > URL: https://issues.jboss.org/browse/TEIID-5657 > Project: Teiid > Issue Type: Feature Request > Components: Documentation, Quick Starts, Tooling > Affects Versions: 12.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > > A migration tool will be provided to convert customer vdbs into just ddl. More than likely this will be just a single ddl file - which will probably not be acceptable to customers with large vdbs. > We have this utility already available as just a main method in one of our jars. It is anticipated that a maven repo will be distribution mechanism and minimal documentation will be provided. > There should be optional validation available for the vdb ddl at build time. This breaks down into 3 parts: > 1. static syntactic validation, potentially even fully resolving if all metadata is present. This makes sure that basic typos will be caught. > 2. providing hard errors for things that are completely removed - an error for usage of soap or function models for example. > 3. providing errors or warning for features that are not yet available - vdb imports, sources that aren't yet supported etc. > To avoid introducing a new plugin or plugging into fmp it's been suggested that the validation could be run via a generated unit test, which ties into another task which is booster, base project, or last resort an arche type that scaffolds the developer project. > This could possibly be included in the quickstarts as a means to facilitate its use. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2019