November 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3158) VDB versioning does not work

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3158?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3158: ------------------------------------------------ Debi Rieden <drieden(a)redhat.com> changed the Status of [bug 1098413|https://bugzilla.redhat.com/show_bug.cgi?id=1098413] from VERIFIED to CLOSED > VDB versioning does not work > ---------------------------- > > Key: TEIID-3158 > URL: https://issues.jboss.org/browse/TEIID-3158 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4.1 > Environment: - JDV 6.0.0 > Reporter: Hisanobu Okuda > Assignee: Steven Hawkins > > The vdb "test.1.vdb" should be deployed as the vdb "test" of the version "1" as described in [1]. But, it is deployed as the vdb "test.1" in fact as following:- > {code} > 20:48:20,210 INFO [org.jboss.as.repository] (management-handler-thread - 6) JBAS014900: Content added at location /opt/dv600/jboss-eap-6.1/standalone/data/content/b8/a0bf2213af6edc2817c63f149f760d1d796cda/content > 20:48:20,212 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "test.1.vdb" (runtime-name: "test.1.vdb") > 20:48:20,270 INFO [org.teiid.RUNTIME] (MSC service thread 1-6) TEIID50029 VDB test.1 model "SourceModel" metadata is currently being loaded. Start Time: 10/2/14 8:48 PM > 20:48:20,273 INFO [org.teiid.RUNTIME] (MSC service thread 1-6) TEIID50029 VDB test.1 model "ViewModel" metadata is currently being loaded. Start Time: 10/2/14 8:48 PM > 20:48:20,296 INFO [org.teiid.RUNTIME] (teiid-async-threads - 4) TEIID50030 VDB test.1 model "ViewModel" metadata loaded. End Time: 10/2/14 8:48 PM > 20:48:20,296 INFO [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50030 VDB test.1 model "SourceModel" metadata loaded. End Time: 10/2/14 8:48 PM > 20:48:20,300 INFO [org.jboss.as.server] (management-handler-thread - 6) JBAS018559: Deployed "test.1.vdb" (runtime-name : "test.1.vdb") > 20:48:20,334 INFO [org.teiid.RUNTIME] (teiid-async-threads - 3) Data Source SourceModel not accessible. > 20:48:20,334 INFO [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID40003 VDB test.1 is set to ACTIVE > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3826) Upgrade to use resteasy-jaxrs:jar:2.3.10.Final

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3826?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3826: ------------------------------------ Then we need to do it now so that these issues can be worked thru. > Upgrade to use resteasy-jaxrs:jar:2.3.10.Final > ---------------------------------------------- > > Key: TEIID-3826 > URL: https://issues.jboss.org/browse/TEIID-3826 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 8.12 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Blocker > > 8.12.x is currently dependent on resteasy-jaxrs:jar:2.3.7.Final > In upgrading the IP-BOM to 30, which is dependent on 2.3.10, it seems the following class has been removed from javax-rs 2.3.10: > org/jboss/resteasy/util/HttpServletRequestDelegate.java > which breaks ProxyHttpServletRequest.java -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3825) Add a wildfly-swarm-teiid Fraction for running teiid as an uberjar

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3825?page=com.atlassian.jira.plugin... ] Kylin Soong commented on TEIID-3825: ------------------------------------ http://wildfly.org/swarm/fractions/ has some introduction of Swarm Fraction, below is a example of DataSourceFraction https://github.com/wildfly-swarm/wildfly-swarm-examples/blob/master/datas... > Add a wildfly-swarm-teiid Fraction for running teiid as an uberjar > ------------------------------------------------------------------ > > Key: TEIID-3825 > URL: https://issues.jboss.org/browse/TEIID-3825 > Project: Teiid > Issue Type: Feature Request > Components: Embedded > Affects Versions: 9.0 > Reporter: Kylin Soong > Assignee: Kylin Soong > Fix For: 9.x > > > Fractions within WildFly Swarm are roughly equivalent to subsystems within WildFly, we have teiid subsystem in Server mode, so I think a Fraction is necessary to run teiid with Swarm. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3462) Add support for semantic versioning of VDBs

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3462?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3462: --------------------------------------- So the full proposal would be along the lines of we will allow both semantic and the old revision based mechanism. You'd be allowed to use one or the other, but not both. For that we'll make the version integer optional in the vdb.xml - for both import and for the vdb itself vdb deployments with a name (or deployment name) of the pattern - name.v[semantic version] will be understood as versioned and we could support a qualifier in the version - SNAPSHOT, but I'm not sure if we want to go to that extent. If there is no semantic version specified, we'll effectively treat it as 0.0.0. In database metadata system functions for backwards compatibility we'll just report the base name as the vdb name. The semantic version would be reported in the system virtualdatabases table. For all api calls the vdb name would be the full name. For connection strings we'd then support: name - same as before latest connection type any. name.1 - would mean version 0.0.0 with revision 1 name.v1.1.1 - means exactly that version name.v1 - short-hand would be supported, so this would be the same as name.v1.0.0 New feature: name.v1. - means it must have a major version of 1 I do agree that this is a lot of work. You can get part of the way in the existing scheme by including the major version in the vdb name - foov1, foov2, which would mean that you could use the version field for micro releases - however this means that clients are dependent only on major versions and there would be no qualifier support. A hybrid approach would be to somehow let the current version field represent the micro version number. > Add support for semantic versioning of VDBs > ------------------------------------------- > > Key: TEIID-3462 > URL: https://issues.jboss.org/browse/TEIID-3462 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.7 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 9.0 > > > Semantic versioning [1] should be supported in the VDB versioning in order to be able to easier determine whether there are breaking changes from the client perspective and to more easily establish a link between client software versions and the VDBs they rely upon. > [1] http://semver.org/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3826) Upgrade to use resteasy-jaxrs:jar:2.3.10.Final

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3826?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3826: ------------------------------------ Yes, bom version 30. > Upgrade to use resteasy-jaxrs:jar:2.3.10.Final > ---------------------------------------------- > > Key: TEIID-3826 > URL: https://issues.jboss.org/browse/TEIID-3826 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 8.12 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Blocker > > 8.12.x is currently dependent on resteasy-jaxrs:jar:2.3.7.Final > In upgrading the IP-BOM to 30, which is dependent on 2.3.10, it seems the following class has been removed from javax-rs 2.3.10: > org/jboss/resteasy/util/HttpServletRequestDelegate.java > which breaks ProxyHttpServletRequest.java -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3826) Upgrade to use resteasy-jaxrs:jar:2.3.10.Final

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3826?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3826: ------------------------------------- [~vhalbert] is that the same version EAP is using? > Upgrade to use resteasy-jaxrs:jar:2.3.10.Final > ---------------------------------------------- > > Key: TEIID-3826 > URL: https://issues.jboss.org/browse/TEIID-3826 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 8.12 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Blocker > > 8.12.x is currently dependent on resteasy-jaxrs:jar:2.3.7.Final > In upgrading the IP-BOM to 30, which is dependent on 2.3.10, it seems the following class has been removed from javax-rs 2.3.10: > org/jboss/resteasy/util/HttpServletRequestDelegate.java > which breaks ProxyHttpServletRequest.java -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3576) Issues with waitForLoad

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3576?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3576. ----------------------------------- Fix Version/s: 8.11.2 8.12 Resolution: Done Updated to allow the user of the login timeout and the proper default. > Issues with waitForLoad > ----------------------- > > Key: TEIID-3576 > URL: https://issues.jboss.org/browse/TEIID-3576 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver, Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11.2, 8.12 > > > TEIID-2059 should be refined in that the existing loginTimeout property should be used instead of waitForLoad. > Also we're not properly using the property. When waitForLoad is specified, we're actually using the system default property instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3826) Upgrade to use resteasy-jaxrs:jar:2.3.10.Final

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3826?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-3826: ------------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) Looks like Ramesh already created a duplicate class for the olingo logic, so assigning to him to see if we want to promote it to a common spot. > Upgrade to use resteasy-jaxrs:jar:2.3.10.Final > ---------------------------------------------- > > Key: TEIID-3826 > URL: https://issues.jboss.org/browse/TEIID-3826 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 8.12 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Blocker > > 8.12.x is currently dependent on resteasy-jaxrs:jar:2.3.7.Final > In upgrading the IP-BOM to 30, which is dependent on 2.3.10, it seems the following class has been removed from javax-rs 2.3.10: > org/jboss/resteasy/util/HttpServletRequestDelegate.java > which breaks ProxyHttpServletRequest.java -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3826) Upgrade to use resteasy-jaxrs:jar:2.3.10.Final

by Van Halbert (JIRA)

Van Halbert created TEIID-3826: ---------------------------------- Summary: Upgrade to use resteasy-jaxrs:jar:2.3.10.Final Key: TEIID-3826 URL: https://issues.jboss.org/browse/TEIID-3826 Project: Teiid Issue Type: Enhancement Components: OData Affects Versions: 8.12 Reporter: Van Halbert Assignee: Steven Hawkins Priority: Blocker 8.12.x is currently dependent on resteasy-jaxrs:jar:2.3.7.Final In upgrading the IP-BOM to 30, which is dependent on 2.3.10, it seems the following class has been removed from javax-rs 2.3.10: org/jboss/resteasy/util/HttpServletRequestDelegate.java which breaks ProxyHttpServletRequest.java -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3462) Add support for semantic versioning of VDBs

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3462?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3462: ------------------------------------- So you will expand the "vdb-name" to allow (include) the semantic version, but at deployment time parse the vdb-name with defined rules of the semantic versioning and qualifiers. Then you will extend the current "connect by" to semantic version. I am kind of still confused how you going to deal with the semantic version in system metadata, sysadmin, Admin API, any external api methods etc., they all seem large changes to me. Luckily I see that SYS only uses vdb-name and only uses "version" in VirtualDatabases table. > Add support for semantic versioning of VDBs > ------------------------------------------- > > Key: TEIID-3462 > URL: https://issues.jboss.org/browse/TEIID-3462 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.7 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 9.0 > > > Semantic versioning [1] should be supported in the VDB versioning in order to be able to easier determine whether there are breaking changes from the client perspective and to more easily establish a link between client software versions and the VDBs they rely upon. > [1] http://semver.org/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 November 2015