[JBoss JIRA] (TEIID-5664) upgrade jts
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5664?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5664.
-----------------------------------
Fix Version/s: 12.1
Resolution: Done
Completed with a full upgrade. Updating to 1.16.0 org.locationtech jts removes the need to also have the jts-io jar.
> upgrade jts
> -----------
>
> Key: TEIID-5664
> URL: https://issues.jboss.org/browse/TEIID-5664
> Project: Teiid
> Issue Type: Task
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.1
>
>
> The jts2geojson dependency is bringing in scala jars. We can upgrade to jts 0.14.0 with minimal effort or switch to the newer org.locationtech 0.16.0 version.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (TEIID-5664) upgrade jts
by Steven Hawkins (Jira)
Steven Hawkins created TEIID-5664:
-------------------------------------
Summary: upgrade jts
Key: TEIID-5664
URL: https://issues.jboss.org/browse/TEIID-5664
Project: Teiid
Issue Type: Task
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
The jts2geojson dependency is bringing in scala jars. We can upgrade to jts 0.14.0 with minimal effort or switch to the newer org.locationtech 0.16.0 version.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[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 commented on TEIID-5657:
------------------------------------
Added option to specify output file, use the following command:
{code}
mvn exec:java -Dvdb={filepath/to/vdb} [ -Doutput={filepath/to/newvdb} ]
{code}
> 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)
5 years, 10 months
[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 stopped 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)
5 years, 10 months
[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 updated TEIID-5657:
-------------------------------
Git Pull Request: https://github.com/teiid/teiid-openshift-examples/pull/10
> 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)
5 years, 10 months
[JBoss JIRA] (TEIID-5663) increase texttablenode synchronization
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5663?page=com.atlassian.jira.plugin... ]
Steven Hawkins edited comment on TEIID-5663 at 2/20/19 11:03 AM:
-----------------------------------------------------------------
Updated to make the synchronization consistent. Made a similar change to xmltablenode as well - it did not have the same issue with close/reset during execution, but if the workitem were to executed after reset that could be an issue.
was (Author: shawkins):
Made similar changes to both the xml and text nodes.
> 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
> Priority: Major
> 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)
5 years, 10 months
[JBoss JIRA] (TEIID-5663) increase texttablenode synchronization
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5663?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5663.
-----------------------------------
Resolution: Done
Made similar changes to both the xml and text nodes.
> 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
> Priority: Major
> 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)
5 years, 10 months
[JBoss JIRA] (TEIIDSB-40) define logging options
by Steven Hawkins (Jira)
Steven Hawkins created TEIIDSB-40:
-------------------------------------
Summary: define logging options
Key: TEIIDSB-40
URL: https://issues.jboss.org/browse/TEIIDSB-40
Project: Teiid Spring Boot
Issue Type: Sub-task
Components: OpenShift
Reporter: Steven Hawkins
Assignee: Ramesh Reddy
Fix For: 1.0.3
It looks like the preferred mechanism with spring boot is to use:
https://github.com/logstash/logstash-logback-encoder
This should make it easier for the aggregate container logging to use the container logs. I'll validate this and update the example appropriately - which we could create a parallel to prometheus for the logging stack / kibana.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[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)
5 years, 10 months