September 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5820) Move the release notes to the docs

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5820: ------------------------------------- Summary: Move the release notes to the docs Key: TEIID-5820 URL: https://issues.jboss.org/browse/TEIID-5820 Project: Teiid Issue Type: Sub-task Components: Documentation Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 13.0 Rather than having the release note nested in the wildfly kit, they should be moved to a common spot in the documentation. Wildfly specific release notes can remain in the kit. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5819) rename translator-swagger to translator-openapi

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5819?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5819. ----------------------------------- Resolution: Done Updated the build to use tranlator-openapi instead and added a release note. > rename translator-swagger to translator-openapi > ----------------------------------------------- > > Key: TEIID-5819 > URL: https://issues.jboss.org/browse/TEIID-5819 > Project: Teiid > Issue Type: Task > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > The term swagger should no longer be prominently used. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-113) Update Teiid OpenShift Examples based on Operator

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-113?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIIDSB-113: --------------------------------- Fix Version/s: 1.3.0 (was: 1.2.0) > Update Teiid OpenShift Examples based on Operator > ------------------------------------------------- > > Key: TEIIDSB-113 > URL: https://issues.jboss.org/browse/TEIIDSB-113 > Project: Teiid Spring Boot > Issue Type: Task > Components: examples > Reporter: Ramesh Reddy > Priority: Major > Fix For: 1.3.0 > > > Based on the work from the Operator the `openshift-examples` can be updated to take the Operator model. This will also expose any gaps in the Operator offering. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-114) Validate vdb-import

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-114?page=com.atlassian.jira.plugi... ] Ramesh Reddy commented on TEIIDSB-114: -------------------------------------- The example above is not a complete representation of the design. It is showing one form of it for simplicity, in hindsight, it may be bad example given the scenarios, as you mention, probably not useful. The above example can be redesigned, where user can write 4 different projects, one for {{foo.vdb}}, another for {{bar.vdb}} then build another combined vdb in another project by defining the {{foo}} and {{bar}} as dependencies. Then in the last, another project that represents the application can define {{dependecy.copy}} action with the combined vdb as its dependency, which will be loaded. I was only showing the kind of later two to minimize the verbosity. I should correct it and write some documentation. > Validate vdb-import > ------------------- > > Key: TEIIDSB-114 > URL: https://issues.jboss.org/browse/TEIIDSB-114 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: core > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.2.0 > > > VDB Import should be supported through the Teiid Spring Boot. The groundwork has been done in the VDB plugin. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-114) Validate vdb-import

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-114?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIIDSB-114: ---------------------------------------- I'm still unsure of the usage paradigm. The imports are still declared in the vdb, not in the pom, and the vdbs to import are already in the same project - not in a repository? Or is this base functionality that the full import feature would be built off of? > Validate vdb-import > ------------------- > > Key: TEIIDSB-114 > URL: https://issues.jboss.org/browse/TEIIDSB-114 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: core > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.2.0 > > > VDB Import should be supported through the Teiid Spring Boot. The groundwork has been done in the VDB plugin. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-114) Validate vdb-import

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-114?page=com.atlassian.jira.plugi... ] Ramesh Reddy resolved TEIIDSB-114. ---------------------------------- Resolution: Done An example of the `vdb-import` can be seen here https://github.com/teiid/teiid-spring-boot/tree/master/samples/vdb-maven > Validate vdb-import > ------------------- > > Key: TEIIDSB-114 > URL: https://issues.jboss.org/browse/TEIIDSB-114 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: core > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.2.0 > > > VDB Import should be supported through the Teiid Spring Boot. The groundwork has been done in the VDB plugin. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5818) separate the wildfly build/repo

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5818?page=com.atlassian.jira.plugin... ] Work on TEIID-5818 started by Steven Hawkins. --------------------------------------------- > separate the wildfly build/repo > ------------------------------- > > Key: TEIID-5818 > URL: https://issues.jboss.org/browse/TEIID-5818 > Project: Teiid > Issue Type: Task > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > The wildfly build should be further decoupled from the Teiid build. Initially this could be as simple as removing the module references from the parent pom. We also need to update the wildfly logic poms to start referencing teiid artifacts via a distinct version (rather than project.version). > From there we can decide how to promote it into its own repository. As it doesn't seem likely that we'll invest in a mechanism to update teiid-wildly using some kind of teiid core overlay, we'll likely just do a teiid-wildfly release with every teiid release. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-119) Upgrade Teiid to 12.3.0

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-119?page=com.atlassian.jira.plugi... ] Ramesh Reddy resolved TEIIDSB-119. ---------------------------------- Fix Version/s: 1.2.0 Resolution: Done > Upgrade Teiid to 12.3.0 > ----------------------- > > Key: TEIIDSB-119 > URL: https://issues.jboss.org/browse/TEIIDSB-119 > Project: Teiid Spring Boot > Issue Type: Task > Components: core > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.2.0 > > > Upgrade Teiid version to 12.3.0 to align with new released version -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-119) Upgrade Teiid to 12.3.0

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIIDSB-119: ------------------------------------ Summary: Upgrade Teiid to 12.3.0 Key: TEIIDSB-119 URL: https://issues.jboss.org/browse/TEIIDSB-119 Project: Teiid Spring Boot Issue Type: Task Components: core Reporter: Ramesh Reddy Assignee: Ramesh Reddy Upgrade Teiid version to 12.3.0 to align with new released version -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-27) Created targeted documentation

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-27?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIIDSB-27: -------------------------------- Fix Version/s: 1.3.0 (was: 1.2.0) > Created targeted documentation > ------------------------------ > > Key: TEIIDSB-27 > URL: https://issues.jboss.org/browse/TEIIDSB-27 > Project: Teiid Spring Boot > Issue Type: Task > Components: documentation > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.3.0 > > > It's expected that all developer oriented aspects will be self documented with javadoc and examples (udfs, pom options, configuration, custom extensions, etc.). However the Teiid ddl, sql - and in particular the presentation of topics that were presented separately such as data roles - need to be covered by documentation that does not reference topics such as Designer, wildfly/cli, xml vdbs, etc. We should probably also discuss if it makes any sense to still offer the local adminapi. > We expect to receive some input from the documentation group around doc structure and strategies for generating specific documentation sets off of a master. At a high level we have: > Administrator’s Guide - WildFly specific and should mostly be replaced by examples > Caching Guide - References adminapi, Teiid JDBC, xml vdbs.. > Client Developer’s Guide - Teiid JDBC > Developer’s Guide - References WildFly and several arche-types are specific to WildFly/JEE - should mostly be replaced by examples > Embedded Guide - Should mostly be replaced by examples > Reference Guide - References XML vdbs > Security Guide - WildFly specific and should mostly be replaced by examples, but a lot is TDB -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2019