June 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5382) rename wildfly-swarm-teiid-examples to thorntail-teiid examples

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-5382: ------------------------------------- Summary: rename wildfly-swarm-teiid-examples to thorntail-teiid examples Key: TEIID-5382 URL: https://issues.jboss.org/browse/TEIID-5382 Project: Teiid Issue Type: Task Reporter: Steven Hawkins Assignee: Steven Hawkins We need to update the repository wildfly-swarm-teiid-examples to reflect the new project name. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5380) Disallow the default option for a function parameter

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5380?page=com.atlassian.jira.plugin... ] Work on TEIID-5380 started by Steven Hawkins. --------------------------------------------- > Disallow the default option for a function parameter > ---------------------------------------------------- > > Key: TEIID-5380 > URL: https://issues.jboss.org/browse/TEIID-5380 > Project: Teiid > Issue Type: Bug > Reporter: Jan Stastny > Assignee: Steven Hawkins > > Currently there's no support in Teiid for default values for parameters of a Function. > But [Function element in BNF for SQL Grammar|https://teiid.gitbooks.io/documents/content/reference/BNF_for_SQL_Grammar.html#createDDLProcedure] shares the definition with Procedure, which permits to deploy such a VDB, where there are DEFAULT values defined on a Function parameter. > So a VDB with following DDL shouldn't deploy successfully: > {code:sql} > CREATE VIRTUAL FUNCTION f1(e2 string NOT NULL DEFAULT 'default') RETURNS string AS > BEGIN > RETURN e2; > END; > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5380) Disallow the default option for a function parameter

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5380?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5380: ---------------------------------- Issue Type: Quality Risk (was: Bug) Component/s: Query Engine > Disallow the default option for a function parameter > ---------------------------------------------------- > > Key: TEIID-5380 > URL: https://issues.jboss.org/browse/TEIID-5380 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Jan Stastny > Assignee: Steven Hawkins > > Currently there's no support in Teiid for default values for parameters of a Function. > But [Function element in BNF for SQL Grammar|https://teiid.gitbooks.io/documents/content/reference/BNF_for_SQL_Grammar.html#createDDLProcedure] shares the definition with Procedure, which permits to deploy such a VDB, where there are DEFAULT values defined on a Function parameter. > So a VDB with following DDL shouldn't deploy successfully: > {code:sql} > CREATE VIRTUAL FUNCTION f1(e2 string NOT NULL DEFAULT 'default') RETURNS string AS > BEGIN > RETURN e2; > END; > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5381) Add a doc note about deployment names

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5381?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5381. ----------------------------------- Resolution: Done Added a note in the versioning documentation. > Add a doc note about deployment names > ------------------------------------- > > Key: TEIID-5381 > URL: https://issues.jboss.org/browse/TEIID-5381 > Project: Teiid > Issue Type: Quality Risk > Components: Documentation > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.0 > > > Especially with regards to vdb versioning, it needs to be made clear that a unique deployment name is still used. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5381) Add a doc note about deployment names

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-5381: ------------------------------------- Summary: Add a doc note about deployment names Key: TEIID-5381 URL: https://issues.jboss.org/browse/TEIID-5381 Project: Teiid Issue Type: Quality Risk Components: Documentation Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 11.0 Especially with regards to vdb versioning, it needs to be made clear that a unique deployment name is still used. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5372) Enhance docker support

by Rafal Korytkowski (JIRA)

[ https://issues.jboss.org/browse/TEIID-5372?page=com.atlassian.jira.plugin... ] Rafal Korytkowski commented on TEIID-5372: ------------------------------------------ [~shawkins], in order to make an informed decision I need to exercise the s2i process a bit more to understand how it aligns with developer and deployment workflows. I'll spend more time today on that. > Enhance docker support > ---------------------- > > Key: TEIID-5372 > URL: https://issues.jboss.org/browse/TEIID-5372 > Project: Teiid > Issue Type: Enhancement > Reporter: Rafal Korytkowski > Assignee: Rafal Korytkowski > Priority: Optional > > Currently there's limited support for docker in Teiid, which can be enabled by adding -Ddocker=true to the build command. The generated image is based on CentOS and running standalone on the Wildfly server. Latest builds are pushed to https://hub.docker.com/r/jboss/teiid/, but versions are not tagged automatically with releases. Development with Docker is not supported. > Proposed changes: > 1. Produce docker image based on Alpine, which is better suited for microservices, in addition to CentOS. > 2. Automatically tag versions in Docker when doing releases. > 3. Support development by providing a docker-compose file with the possibility to start server in a debug mode and enabled auto-redeployment of code changes. > 4. Optionally provide a Docker image for building code using maven in Docker. Having Docker as the only prerequisite is convenient for CI environments and makes the build environment agnostic. > [~shawkins], [~rareddy], thoughts? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5285) Add high-level feature for redirection of updates

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-5285?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5285: ------------------------------------- I am not sure if a new issue is warranted for this at least right now, but seems like these both issues go together. However, Schema Evolution seems to go much deeper. Schema Evolution, Data Redirection, and Data Migration all seem to integral parts of a solution. My ambitious goal is somehow to bring all together with some level of automation using Teiid, but right now I am really skimpy on details. Yes, I am trying to think through to put a proposal using FlywayDB for last day or so, but no luck yet. I think we can tie FlywayDB's "migration" action to a new VDB version generation + deployment of that VDB + update of older VDB version (like an update of view transformation). But for needed code generation, the interception of migration script and native DB code generation is not clear without clear patterns of how to handle say "adding a new column", "change data type" etc. > Add high-level feature for redirection of updates > ------------------------------------------------- > > Key: TEIID-5285 > URL: https://issues.jboss.org/browse/TEIID-5285 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Teiid Spring Boot > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 11.x > > Attachments: redirection-vdb.xml > > > In microservices testing it is desirable to test against production/live data but not commit any updates. We should offer a simple solution that can defined by extension metadata and enabled/disabled by a feature flag. We may need to make simplifying assumptions about the scope (per session, per application, etc.) and durability of the updates. > Under the covers this will be achieved by using views, update triggers, and a store for the updates and when not enabled the expectation is that all operations should pass through. However the application will be limited to using Teiid SQL and will be required to use the Teiid or pg driver, or Teiid spring boot. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5285) Add high-level feature for redirection of updates

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5285?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5285: --------------------------------------- Did you want to start a new issue/topic on the migration part? Are you looking at documenting / pairing dv with migration tools like flywaydb? > Add high-level feature for redirection of updates > ------------------------------------------------- > > Key: TEIID-5285 > URL: https://issues.jboss.org/browse/TEIID-5285 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Teiid Spring Boot > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 11.x > > Attachments: redirection-vdb.xml > > > In microservices testing it is desirable to test against production/live data but not commit any updates. We should offer a simple solution that can defined by extension metadata and enabled/disabled by a feature flag. We may need to make simplifying assumptions about the scope (per session, per application, etc.) and durability of the updates. > Under the covers this will be achieved by using views, update triggers, and a store for the updates and when not enabled the expectation is that all operations should pass through. However the application will be limited to using Teiid SQL and will be required to use the Teiid or pg driver, or Teiid spring boot. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5372) Enhance docker support

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5372?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5372: --------------------------------------- [~rkorytkowski] [~rareddy] We kind of left this hanging. Let's come to a consensus on whether the current docker image is of any value. If not, then we should pull it from the build and focus on the s2i process instead. Alternatively we can also look at providing an openshift image/template for standing up a traditional WildFly+Teiid environment with persistent storage for the configuration, deployments, etc. - but of course that is contrary to the main openshift direction. > Enhance docker support > ---------------------- > > Key: TEIID-5372 > URL: https://issues.jboss.org/browse/TEIID-5372 > Project: Teiid > Issue Type: Enhancement > Reporter: Rafal Korytkowski > Assignee: Rafal Korytkowski > Priority: Optional > > Currently there's limited support for docker in Teiid, which can be enabled by adding -Ddocker=true to the build command. The generated image is based on CentOS and running standalone on the Wildfly server. Latest builds are pushed to https://hub.docker.com/r/jboss/teiid/, but versions are not tagged automatically with releases. Development with Docker is not supported. > Proposed changes: > 1. Produce docker image based on Alpine, which is better suited for microservices, in addition to CentOS. > 2. Automatically tag versions in Docker when doing releases. > 3. Support development by providing a docker-compose file with the possibility to start server in a debug mode and enabled auto-redeployment of code changes. > 4. Optionally provide a Docker image for building code using maven in Docker. Having Docker as the only prerequisite is convenient for CI environments and makes the build environment agnostic. > [~shawkins], [~rareddy], thoughts? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5285) Add high-level feature for redirection of updates

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-5285?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5285: ------------------------------------- Another article from Martin Flower about the evolution of Database Schema [3] in agile development. [3] https://www.martinfowler.com/articles/evodb.html > Add high-level feature for redirection of updates > ------------------------------------------------- > > Key: TEIID-5285 > URL: https://issues.jboss.org/browse/TEIID-5285 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Teiid Spring Boot > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 11.x > > Attachments: redirection-vdb.xml > > > In microservices testing it is desirable to test against production/live data but not commit any updates. We should offer a simple solution that can defined by extension metadata and enabled/disabled by a feature flag. We may need to make simplifying assumptions about the scope (per session, per application, etc.) and durability of the updates. > Under the covers this will be achieved by using views, update triggers, and a store for the updates and when not enabled the expectation is that all operations should pass through. However the application will be limited to using Teiid SQL and will be required to use the Teiid or pg driver, or Teiid spring boot. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2018