[JBoss JIRA] (TEIID-5372) Enhance docker support
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-5372?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-5372:
-------------------------------------
Agree. OpenShift focus will align both community and any product needs.
I have been artificially keeping a barrier between "Thorntail" offering to that of "OpenShift" like for example, we have "thorntail-teiid-examples" but not yet "openshift-teiid-examples", we need a way to showcase how we can take the same example and deploy standalone and OpenShift. What else can we think of improvements here?
- maven plugin support for multiple vdbs
> 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
[JBoss JIRA] (TEIID-5383) CURRENT_DATE without parens doesn't work
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5383?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5383:
----------------------------------
Component/s: Query Engine
Description:
CURRENT_DATE don't work (parse exception)
CURDATE() versions work well
Use case: universal query builder from JOOQ uses CURRENT_DATE function name format (probably ANSI compatible one?)
was:
CURRENT_DATE/CURRENT_TIME/CURRENT_TIMESTAMP functions don't work (parse exception)
CURDATE() versions work well
Use case: universal query builder from JOOQ uses CURRENT_DATE function name format (probably ANSI compatible one?)
Fix Version/s: 11.0
Summary: CURRENT_DATE without parens doesn't work (was: CURRENT_DATE/CURRENT_TIME/CURRENT_TIMESTAMP doesn't work)
Updated based upon TEIID-5317 - which leaves only support for CURRENT_DATE without parens to add.
> CURRENT_DATE without parens doesn't work
> ----------------------------------------
>
> Key: TEIID-5383
> URL: https://issues.jboss.org/browse/TEIID-5383
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Lukáš Svačina
> Assignee: Steven Hawkins
> Priority: Minor
> Fix For: 11.0
>
>
> CURRENT_DATE don't work (parse exception)
> CURDATE() versions work well
> Use case: universal query builder from JOOQ uses CURRENT_DATE function name format (probably ANSI compatible one?)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[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:
---------------------------------------
> S2I as in the generation of the image for OpenShift? what are you thinking here?
Yes it seems like we (Teiid community) should promote OpenShift rather than just docker.
> 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
[JBoss JIRA] (TEIID-5385) POSITION function
by Lukáš Svačina (JIRA)
Lukáš Svačina created TEIID-5385:
------------------------------------
Summary: POSITION function
Key: TEIID-5385
URL: https://issues.jboss.org/browse/TEIID-5385
Project: Teiid
Issue Type: Feature Request
Reporter: Lukáš Svačina
Assignee: Steven Hawkins
syntax should work as: POSITION(something in something)
Use case: universal query builder from JOOQ uses POSITION function (probably ANSI compatible one?)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[JBoss JIRA] (TEIID-5384) CHAR_LENGTH function
by Lukáš Svačina (JIRA)
Lukáš Svačina created TEIID-5384:
------------------------------------
Summary: CHAR_LENGTH function
Key: TEIID-5384
URL: https://issues.jboss.org/browse/TEIID-5384
Project: Teiid
Issue Type: Feature Request
Reporter: Lukáš Svačina
Assignee: Steven Hawkins
Should work same as LENGTH function.
Use case: universal query builder from JOOQ uses CHAR_LENGTH function (probably ANSI compatible one?)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[JBoss JIRA] (TEIID-5383) CURRENT_DATE/CURRENT_TIME/CURRENT_TIMESTAMP doesn't work
by Lukáš Svačina (JIRA)
Lukáš Svačina created TEIID-5383:
------------------------------------
Summary: CURRENT_DATE/CURRENT_TIME/CURRENT_TIMESTAMP doesn't work
Key: TEIID-5383
URL: https://issues.jboss.org/browse/TEIID-5383
Project: Teiid
Issue Type: Bug
Reporter: Lukáš Svačina
Assignee: Steven Hawkins
Priority: Minor
CURRENT_DATE/CURRENT_TIME/CURRENT_TIMESTAMP functions don't work (parse exception)
CURDATE() versions work well
Use case: universal query builder from JOOQ uses CURRENT_DATE function name format (probably ANSI compatible one?)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[JBoss JIRA] (TEIID-5372) Enhance docker support
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-5372?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-5372:
-------------------------------------
S2I as in the generation of the image for OpenShift? what are you thinking here?
As I was mentioning above, we could further drive Docker images based on Throntail, where the configuration is at least minimized.
> 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