July 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4539) Reduce memory footprint of DatabaseStore

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4539?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4539. ----------------------------------- Resolution: Out of Date The older changes on which this issue was based were not yet brought forward. > Reduce memory footprint of DatabaseStore > ---------------------------------------- > > Key: TEIID-4539 > URL: https://issues.jboss.org/browse/TEIID-4539 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > > The DatabaseStore holds an in-memory copy of Databases and there is the functional VDBRepository copy as well. String canonicalization in the metadata objects should help with reducing the memory footprint, but it may be good to go further and use clones of the functional metadata on demand. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5362) Odata4 outputs in wrong timezone

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5362?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5362. ----------------------------------- Resolution: Incomplete Description Marking as incomplete description. Based upon the description this does not appear directly related to odata and seems instead to be an issue with the database driver. Given that the user has an acceptable workaround, marking this as incomplete description. > Odata4 outputs in wrong timezone > -------------------------------- > > Key: TEIID-5362 > URL: https://issues.jboss.org/browse/TEIID-5362 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12.13.6_4 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > The incoming odata4 request is requesting the records at 08:52Z (specifying UTC time). The DataVirt server (running in US/Chicago time) converts that into SQL to ask the database for records at 03:52 (with no timezone specifier... should be in local time, or US/Chicago). The database should recognize that the 03:52 Local time should be converted back to 08:52Z to match the DB records, however, it is not. This (and other tests), leads us to the conclusion that the database session/connection is actually not using US/Chicago (-5:00) timezone, but is instead using the UTC timezone. Unfortunately, we were not able to confirm either in the logs or in the configuration, where the connection was being set up in UTC timezone. > . -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 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: --------------------------------------- > Sure, if you externalized the volume mount for configuration, that is the simplest route. Same could be said for modules. It does not appear that anyone promotes a base wildfly image that is persistently mutable. The usage scenarios that jboss/red hat promotes are an s2i base image (https://github.com/openshift-s2i/s2i-wildfly) and the simple base image (https://github.com/jboss-dockerfiles/wildfly). So I'm going to side with Ramesh and say there isn't a lot of value in offering this approach on our own - even just as a developer aid as it should be just as easy for a developer to bring up a full wildfly or arquillian tests. Option 1, we can keep building our own base image with the following updates: - as Rafal suggests add a latest tag and provide some example(s) that demonstrate extending the image via a dockerfile using cli to configure the system. Rather than our old example which - add some documentation to the dockerhub page Option 2, just remove the teiid community docker image and push updates to the jboss dockerfile for teiid - https://github.com/jboss-dockerfiles/teiid > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5405) Change default vdb version behavior for Odata/Odata4 to use Connection type like JDBC Connections

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5405?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5405: ---------------------------------- Fix Version/s: 11.1 This behavior was part of the original odata logic and was preserved with the changes to suppor semantic versions. The rationale I believe is that the best practice for odata is to require explicit versioning. Perhaps this could be driven by a vdb property. > Change default vdb version behavior for Odata/Odata4 to use Connection type like JDBC Connections > ------------------------------------------------------------------------------------------------- > > Key: TEIID-5405 > URL: https://issues.jboss.org/browse/TEIID-5405 > Project: Teiid > Issue Type: Feature Request > Components: OData > Affects Versions: 8.12.13.6_4 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 11.1 > > > With JDBC/ODBC Connections having the Connection type set to BY_VERSION for all versions of a VDB and not specifying the version in the URL it connects to the earliest version (as it should) and setting the Connection type to ANY for the latest version of the VDB it connects to that version by default if none is specified in the URL (this is also the correct behavior) but connecting via OData/OData4 it will always connect to version 1 if the version is not specified in the URL even if the latest VDB version has Connection type of ANY and all others are set to BY_VERSION. Can the OData connection behavior be the same as JDBC/ODBC? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5392) Define how other artifacts are included in a vdb archive

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5392?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5392: ---------------------------------- Fix Version/s: 11.1 > Define how other artifacts are included in a vdb archive > -------------------------------------------------------- > > Key: TEIID-5392 > URL: https://issues.jboss.org/browse/TEIID-5392 > Project: Teiid > Issue Type: Sub-task > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 11.1 > > > An example throntail build should show how to incorporate udf jar(s) or other vdb resources. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5394) Define how to utilize multiple vdbs

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5394?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5394: ---------------------------------- Fix Version/s: 11.1 > Define how to utilize multiple vdbs > ----------------------------------- > > Key: TEIID-5394 > URL: https://issues.jboss.org/browse/TEIID-5394 > Project: Teiid > Issue Type: Sub-task > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.1 > > > Perhaps to support vdb imports, we should define how a build can incorporate multiple vdbs. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5391) Thorntail and s2i builds

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5391?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5391: ---------------------------------- Fix Version/s: 11.1 > Thorntail and s2i builds > ------------------------ > > Key: TEIID-5391 > URL: https://issues.jboss.org/browse/TEIID-5391 > Project: Teiid > Issue Type: Feature Request > Components: Build/Kits, Documentation > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.1 > > > This will serve as the parent issue for building with thorntail and creating openshift images. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5393) Build time validation when the metadata is fully specified.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5393?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5393: ---------------------------------- Fix Version/s: 11.1 > Build time validation when the metadata is fully specified. > ----------------------------------------------------------- > > Key: TEIID-5393 > URL: https://issues.jboss.org/browse/TEIID-5393 > Project: Teiid > Issue Type: Sub-task > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.1 > > > To tighten the development loop for creating thorntail deployments there should be a build time validation of a vdb - either just parsing, or effectively a local loading when the metadata if fully specified. That will catch any issues before generating / running the image. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5405) Change default vdb version behavior for Odata/Odata4 to use Connection type like JDBC Connections

by Debbie Steigner (JIRA)

Debbie Steigner created TEIID-5405: -------------------------------------- Summary: Change default vdb version behavior for Odata/Odata4 to use Connection type like JDBC Connections Key: TEIID-5405 URL: https://issues.jboss.org/browse/TEIID-5405 Project: Teiid Issue Type: Feature Request Components: OData Affects Versions: 8.12.13.6_4 Reporter: Debbie Steigner Assignee: Steven Hawkins With JDBC/ODBC Connections having the Connection type set to BY_VERSION for all versions of a VDB and not specifying the version in the URL it connects to the earliest version (as it should) and setting the Connection type to ANY for the latest version of the VDB it connects to that version by default if none is specified in the URL (this is also the correct behavior) but connecting via OData/OData4 it will always connect to version 1 if the version is not specified in the URL even if the latest VDB version has Connection type of ANY and all others are set to BY_VERSION. Can the OData connection behavior be the same as JDBC/ODBC? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5404) JPA Translator fails embeddeds

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5404?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5404: ---------------------------------- Fix Version/s: 11.1 > JPA Translator fails embeddeds > ------------------------------ > > Key: TEIID-5404 > URL: https://issues.jboss.org/browse/TEIID-5404 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Harold Campbell > Assignee: Steven Hawkins > Fix For: 11.1 > > > The JPA translator does not properly handle embedded properties. Columns can overlap if the embedded has properties sharing the same name as the parent or other embedded properties. Come query time, embedded columns do not get translated into correct entity path traversals. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2018