December 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5578) Issues if xa txn import fails

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5578: ------------------------------------- Summary: Issues if xa txn import fails Key: TEIID-5578 URL: https://issues.jboss.org/browse/TEIID-5578 Project: Teiid Issue Type: Bug Components: JDBC Driver, Server Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 12.0, 11.2.2 There are two issues if the import fails. The first is that the transaction type is already set on the context which will cause an npe later when the session is killed - as no txn will be set on the context as expected. The other issue is that the client does not rethrow the exception. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5577) Create clean dependencies / separate boms

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5577: ------------------------------------- Summary: Create clean dependencies / separate boms Key: TEIID-5577 URL: https://issues.jboss.org/browse/TEIID-5577 Project: Teiid Issue Type: Sub-task Components: Build/Kits Reporter: Steven Hawkins Assignee: Van Halbert The teiid-bom currently defines all of the non-overlapping dependencies with the wildfly bom. We should introduce another bom that defines the overlapping dependencies used by the core project - this includes things like vfs, jboss-logging, the javax api jars, marshalling, infinispan, etc. We should also substitute usage of the jboss javax jars for whatever the vanilla replacements are. We should then be able to cut ties with wildfly boms in the core project. For connector development convenience we could also introduce a bom-wildfly which imports both the teiid-bom and the wildfly-parent. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5576) switch arche-types to use bom

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5576?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5576: --------------------------------------- With this change it highlights that usage of wildfly api jars, such as jboss-connector-api_1.7_spec, they are only available if we also import the wildfly-parent bom. For now instead I made the connector arche-type use the teiid-parent. [~rareddy] [~rhn-engineering-vhalbert] unless there are any objections, we should probably go ahead and replace all of the jboss api jars with their equivalent just javax versions. > switch arche-types to use bom > ----------------------------- > > Key: TEIID-5576 > URL: https://issues.jboss.org/browse/TEIID-5576 > Project: Teiid > Issue Type: Quality Risk > Components: Tools > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0 > > > There are a couple of hard coded versions that can be removed with the bom. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5576) switch arche-types to use bom

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5576: ------------------------------------- Summary: switch arche-types to use bom Key: TEIID-5576 URL: https://issues.jboss.org/browse/TEIID-5576 Project: Teiid Issue Type: Quality Risk Components: Tools Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 12.0 There are a couple of hard coded versions that can be removed with the bom. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5563) Separate the Teiid WildFly distribution into their own repo or module

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5563?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5563: --------------------------------------- The resource dependency has now been removed from the engine. We needed a new interface XAImporter to encapsulate the functionality provided by the workmanager and xaterminator. For simplicity the interface is in teiid-api and the impl is in teiid-resource-spi. This does mean that api still has a dependency to javax.transaction, but since that still exists in the engine it's a minor issue. > Separate the Teiid WildFly distribution into their own repo or module > --------------------------------------------------------------------- > > Key: TEIID-5563 > URL: https://issues.jboss.org/browse/TEIID-5563 > Project: Teiid > Issue Type: Task > Components: Build/Kits, Integration Tests > Affects Versions: 12.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > > With the different types of distributions now being built based on Teiid like > * WildFly > * Thorntail > * SpringBoot > * Embedded > Having main `github.com/teiid` repo contain artifacts for WildFly distribution poses an unnecessary dependency burden on other distributions. For example, the resource adapters are mainly for use with WildFly and Thorntail V2. They can still be applicable to embedded and SpringBoot as either non-managed connection factories, or require the user to provide appropriate management / pooling. When they are pulled into environments like SpringBoot they will bring several wildfly dependencies / and JEE constructs that are unnecessary - specifically the dependencies jboss-jaxws-api (teiid-api), javax.activation (teiid-core), jboss-transaction-api (teiid-api), and jboss-connector-api (teiid-api). > This proposal is to separate "teiid" core modules along with all translators into one repository and move all the resource adapters along with any feature-packs and module building into a sperate repository like "teiid-wildfly". With the goal of providing similar connectivity in SpringBoot using as much common logic from SpringBoot (Spring Data in particular) and even Fuse as possible. > Basically, when finished, the core Teiid modules only provide Maven artifacts along with their clean pom.xml with for direct and maybe transitive dependencies. None of the WildFly based modules support will be here. At worst this may introduce duplicate dependencies into the WildFly environment as we will need to manage all core / translator dependencies independently from those provided by WildFly. Where possible the teiid-api / core modules will need to use the generic javax dependency - or even remove the dependency if possible. > The "teiid-wildfly" module on the other hand, will exactly preserve what is in the current repo as far feature packs and module building and overall WildFly distribution building. > A follow-on task we can task we can look into is, converting the main teiid then to use basepom rather than the jboss-parent pom. However, the recommendation is this should be done after, not simultaneously. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5563) Separate the Teiid WildFly distribution into their own repo or module

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5563?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-5563: ------------------------------- Comment: was deleted (was: with the refactoring of wildfly and connectors, what do you think about calling the connectors now "translators", since that is only what it contains (and related modules)? And use connectors for what is moved under wildfly.) > Separate the Teiid WildFly distribution into their own repo or module > --------------------------------------------------------------------- > > Key: TEIID-5563 > URL: https://issues.jboss.org/browse/TEIID-5563 > Project: Teiid > Issue Type: Task > Components: Build/Kits, Integration Tests > Affects Versions: 12.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > > With the different types of distributions now being built based on Teiid like > * WildFly > * Thorntail > * SpringBoot > * Embedded > Having main `github.com/teiid` repo contain artifacts for WildFly distribution poses an unnecessary dependency burden on other distributions. For example, the resource adapters are mainly for use with WildFly and Thorntail V2. They can still be applicable to embedded and SpringBoot as either non-managed connection factories, or require the user to provide appropriate management / pooling. When they are pulled into environments like SpringBoot they will bring several wildfly dependencies / and JEE constructs that are unnecessary - specifically the dependencies jboss-jaxws-api (teiid-api), javax.activation (teiid-core), jboss-transaction-api (teiid-api), and jboss-connector-api (teiid-api). > This proposal is to separate "teiid" core modules along with all translators into one repository and move all the resource adapters along with any feature-packs and module building into a sperate repository like "teiid-wildfly". With the goal of providing similar connectivity in SpringBoot using as much common logic from SpringBoot (Spring Data in particular) and even Fuse as possible. > Basically, when finished, the core Teiid modules only provide Maven artifacts along with their clean pom.xml with for direct and maybe transitive dependencies. None of the WildFly based modules support will be here. At worst this may introduce duplicate dependencies into the WildFly environment as we will need to manage all core / translator dependencies independently from those provided by WildFly. Where possible the teiid-api / core modules will need to use the generic javax dependency - or even remove the dependency if possible. > The "teiid-wildfly" module on the other hand, will exactly preserve what is in the current repo as far feature packs and module building and overall WildFly distribution building. > A follow-on task we can task we can look into is, converting the main teiid then to use basepom rather than the jboss-parent pom. However, the recommendation is this should be done after, not simultaneously. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5563) Separate the Teiid WildFly distribution into their own repo or module

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5563?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-5563: ------------------------------------ with the refactoring of wildfly and connectors, what do you think about calling the connectors now "translators", since that is only what it contains (and related modules)? And use connectors for what is moved under wildfly. > Separate the Teiid WildFly distribution into their own repo or module > --------------------------------------------------------------------- > > Key: TEIID-5563 > URL: https://issues.jboss.org/browse/TEIID-5563 > Project: Teiid > Issue Type: Task > Components: Build/Kits, Integration Tests > Affects Versions: 12.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > > With the different types of distributions now being built based on Teiid like > * WildFly > * Thorntail > * SpringBoot > * Embedded > Having main `github.com/teiid` repo contain artifacts for WildFly distribution poses an unnecessary dependency burden on other distributions. For example, the resource adapters are mainly for use with WildFly and Thorntail V2. They can still be applicable to embedded and SpringBoot as either non-managed connection factories, or require the user to provide appropriate management / pooling. When they are pulled into environments like SpringBoot they will bring several wildfly dependencies / and JEE constructs that are unnecessary - specifically the dependencies jboss-jaxws-api (teiid-api), javax.activation (teiid-core), jboss-transaction-api (teiid-api), and jboss-connector-api (teiid-api). > This proposal is to separate "teiid" core modules along with all translators into one repository and move all the resource adapters along with any feature-packs and module building into a sperate repository like "teiid-wildfly". With the goal of providing similar connectivity in SpringBoot using as much common logic from SpringBoot (Spring Data in particular) and even Fuse as possible. > Basically, when finished, the core Teiid modules only provide Maven artifacts along with their clean pom.xml with for direct and maybe transitive dependencies. None of the WildFly based modules support will be here. At worst this may introduce duplicate dependencies into the WildFly environment as we will need to manage all core / translator dependencies independently from those provided by WildFly. Where possible the teiid-api / core modules will need to use the generic javax dependency - or even remove the dependency if possible. > The "teiid-wildfly" module on the other hand, will exactly preserve what is in the current repo as far feature packs and module building and overall WildFly distribution building. > A follow-on task we can task we can look into is, converting the main teiid then to use basepom rather than the jboss-parent pom. However, the recommendation is this should be done after, not simultaneously. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-219) Add a way to limit or suppress queries that exceed a threshold Cost-Based Optimizer value

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-219?page=com.atlassian.jira.plugin.... ] Work on TEIID-219 stopped by Steven Hawkins. -------------------------------------------- > Add a way to limit or suppress queries that exceed a threshold Cost-Based Optimizer value > ----------------------------------------------------------------------------------------- > > Key: TEIID-219 > URL: https://issues.jboss.org/browse/TEIID-219 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Server > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > Client requesting an ability to impose a limit on, or suppress, any query that exceeds a cost estimate value specified by the user/administrator. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-219) Add a way to limit or suppress queries that exceed a threshold Cost-Based Optimizer value

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-219?page=com.atlassian.jira.plugin.... ] Steven Hawkins updated TEIID-219: --------------------------------- Fix Version/s: 12.1 (was: 12.0) > Add a way to limit or suppress queries that exceed a threshold Cost-Based Optimizer value > ----------------------------------------------------------------------------------------- > > Key: TEIID-219 > URL: https://issues.jboss.org/browse/TEIID-219 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Server > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > Client requesting an ability to impose a limit on, or suppress, any query that exceeds a cost estimate value specified by the user/administrator. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5563) Separate the Teiid WildFly distribution into their own repo or module

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5563?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5563: --------------------------------------- xml.ws has now been moved out of teiid-api by just putting the connection interface with the translator. > Separate the Teiid WildFly distribution into their own repo or module > --------------------------------------------------------------------- > > Key: TEIID-5563 > URL: https://issues.jboss.org/browse/TEIID-5563 > Project: Teiid > Issue Type: Task > Components: Build/Kits, Integration Tests > Affects Versions: 12.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > > With the different types of distributions now being built based on Teiid like > * WildFly > * Thorntail > * SpringBoot > * Embedded > Having main `github.com/teiid` repo contain artifacts for WildFly distribution poses an unnecessary dependency burden on other distributions. For example, the resource adapters are mainly for use with WildFly and Thorntail V2. They can still be applicable to embedded and SpringBoot as either non-managed connection factories, or require the user to provide appropriate management / pooling. When they are pulled into environments like SpringBoot they will bring several wildfly dependencies / and JEE constructs that are unnecessary - specifically the dependencies jboss-jaxws-api (teiid-api), javax.activation (teiid-core), jboss-transaction-api (teiid-api), and jboss-connector-api (teiid-api). > This proposal is to separate "teiid" core modules along with all translators into one repository and move all the resource adapters along with any feature-packs and module building into a sperate repository like "teiid-wildfly". With the goal of providing similar connectivity in SpringBoot using as much common logic from SpringBoot (Spring Data in particular) and even Fuse as possible. > Basically, when finished, the core Teiid modules only provide Maven artifacts along with their clean pom.xml with for direct and maybe transitive dependencies. None of the WildFly based modules support will be here. At worst this may introduce duplicate dependencies into the WildFly environment as we will need to manage all core / translator dependencies independently from those provided by WildFly. Where possible the teiid-api / core modules will need to use the generic javax dependency - or even remove the dependency if possible. > The "teiid-wildfly" module on the other hand, will exactly preserve what is in the current repo as far feature packs and module building and overall WildFly distribution building. > A follow-on task we can task we can look into is, converting the main teiid then to use basepom rather than the jboss-parent pom. However, the recommendation is this should be done after, not simultaneously. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2018