May 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4906) Clean up licensing and copyright information

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4906: ------------------------------------- Summary: Clean up licensing and copyright information Key: TEIID-4906 URL: https://issues.jboss.org/browse/TEIID-4906 Project: Teiid Issue Type: Sub-task Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.3 There is some drift in our copyright and licensing information. We also need to more broadly advertise the ancillary licenses we are pulling in. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4901) Add parallel source query handling for when IN criteria values exceed MaxInCriteriaSize for translator

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4901?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4901: --------------------------------- Fix Version/s: 8.12.11.6_3 > Add parallel source query handling for when IN criteria values exceed MaxInCriteriaSize for translator > ------------------------------------------------------------------------------------------------------ > > Key: TEIID-4901 > URL: https://issues.jboss.org/browse/TEIID-4901 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.12.10.6_3 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 9.3, 8.12.11.6_3 > > > Add the capability to split an independent accessnode into multiple parallel source queries when the number of IN criteria values exceed the translator's MaxInCriteriaSize value. This would be similar handling to what we perform on the dependent side of a dependent join when the number of values exceed the size. > The background for this request is regarding input to an SAP gateway source which has a MaxInCriteriaSize of 3 due to URL length restrictions. Currently, if 4 values are submitted the full result set is returned to be processed within the Teiid engine. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4905) Verify and Provide .NET connectivity

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-4905: ----------------------------------- Summary: Verify and Provide .NET connectivity Key: TEIID-4905 URL: https://issues.jboss.org/browse/TEIID-4905 Project: Teiid Issue Type: Feature Request Components: Common Reporter: Ramesh Reddy Assignee: Steven Hawkins The user should be able to connect to Teiid using .NET libraries. Postgres supports [1], this should be verified. [1] http://www.npgsql.org/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4895) Determine community requirements for WildFly usage

by Marco Ardito (JIRA)

[ https://issues.jboss.org/browse/TEIID-4895?page=com.atlassian.jira.plugin... ] Marco Ardito commented on TEIID-4895: ------------------------------------- We started with Teiid/AS and still currently use Teiid/Wildfly bundle, and we would like to continue: it works well (multiplatform), has a nice web interface and is quite well documented and supported. Would be nice to have and learn other ways, though. And, thanks for asking :) > Determine community requirements for WildFly usage > -------------------------------------------------- > > Key: TEIID-4895 > URL: https://issues.jboss.org/browse/TEIID-4895 > Project: Teiid > Issue Type: Task > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > WildFly is typically the runtime for Teiid. However we want feedback from the community on what style of WildFly integration is important: > - The ability to deploy Teiid into a managed WildFly instance/cluster > - The combination Teiid/WildFly artifact > - A layered docker image > - Not full WildFly, just Swarm > - Not needed, just Embedded > Based upon this we can better tune our documentation, downloads, and examples. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4881) Better account for differences between ddl and vdb.xml vdbs

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4881?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4881. ----------------------------------- Resolution: Done Updated the docs as to these changes and added a section covering the differences. > Better account for differences between ddl and vdb.xml vdbs > ----------------------------------------------------------- > > Key: TEIID-4881 > URL: https://issues.jboss.org/browse/TEIID-4881 > Project: Teiid > Issue Type: Task > Components: Query Engine > Affects Versions: 9.2 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.3 > > > In several aspects the metadata systems are different, which is touched on in TEIID-4536 > This issue will cover making them function as similarly as possible and to also document the ways in which they are different. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4895) Determine community requirements for WildFly usage

by Tom Arnold (JIRA)

[ https://issues.jboss.org/browse/TEIID-4895?page=com.atlassian.jira.plugin... ] Tom Arnold commented on TEIID-4895: ----------------------------------- For us the Teiid/Wildfly combination is useful because our main application runs in Wildfly, so it's just more of the same thing WRT development and deployment. I don't see this changing anytime soon. Our usage is basically this: We have a web app deployed in Teiid/Wildfly that configures data sources (using Teiid Admin and DMR) and generates a VDB. We have several translator JARs as hot-deployments in Teiid/Wildfly, and scripts to redeploy translator + VDB on change. We talk to Teiid over JDBC from other JBoss/Wildfly servers. We don't currently use the clustering/HA features that are out there but we may be looking into this soon. > Determine community requirements for WildFly usage > -------------------------------------------------- > > Key: TEIID-4895 > URL: https://issues.jboss.org/browse/TEIID-4895 > Project: Teiid > Issue Type: Task > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > WildFly is typically the runtime for Teiid. However we want feedback from the community on what style of WildFly integration is important: > - The ability to deploy Teiid into a managed WildFly instance/cluster > - The combination Teiid/WildFly artifact > - A layered docker image > - Not full WildFly, just Swarm > - Not needed, just Embedded > Based upon this we can better tune our documentation, downloads, and examples. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4557) Enable memory management at the query level

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4557?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4557. ----------------------------------- Resolution: Done Given the lack of additional feedback, we'll start with the additional restrictions added here that were both automatic and property driven with maxSessionBufferSizeEstimate - see the doc update for more. > Enable memory management at the query level > ------------------------------------------- > > Key: TEIID-4557 > URL: https://issues.jboss.org/browse/TEIID-4557 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 9.3 > > > Allows managing (and limiting if needed) the memory consumed by the execution of a particular view. Maybe this can be done through a max. memory and swapping settings on the view. > Would it also be possible to set a global memory limit for the execution of any query in the server or in a particular VDB. This provides a simple and general setting to guarantee no query can monopolize server resources -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4895) Determine community requirements for WildFly usage

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4895?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4895: ------------------------------------- Another way to look at is, how would you see your current architectures changing in coming years with Teiid, would you still see the need JEE based server. We want to start thinking/talking/planning about for next 3-5 yrs time frame. > Determine community requirements for WildFly usage > -------------------------------------------------- > > Key: TEIID-4895 > URL: https://issues.jboss.org/browse/TEIID-4895 > Project: Teiid > Issue Type: Task > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > WildFly is typically the runtime for Teiid. However we want feedback from the community on what style of WildFly integration is important: > - The ability to deploy Teiid into a managed WildFly instance/cluster > - The combination Teiid/WildFly artifact > - A layered docker image > - Not full WildFly, just Swarm > - Not needed, just Embedded > Based upon this we can better tune our documentation, downloads, and examples. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4051) Swagger metadata includes internal java constructs

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4051?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-4051: ----------------------------------- Assignee: Ramesh Reddy > Swagger metadata includes internal java constructs > -------------------------------------------------- > > Key: TEIID-4051 > URL: https://issues.jboss.org/browse/TEIID-4051 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Affects Versions: 8.12.x > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 10.0 > > > From IntegrationTestRestWarGeneration the swagger metadata includes definitions for Statement, ResultSet, StreamingOutput, etc.: > ... > InputStream: > type: "object" > Statement: > type: "object" > properties: > queryTimeout: > type: "integer" > format: "int32" > closed: > type: "boolean" > default: false > resultSet: > $ref: "#/definitions/ResultSet" > ... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4051) Swagger metadata includes internal java constructs

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4051?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4051: ------------------------------------- In light of APICurio, I would like to see what kind of runtime changes Teiid would need in this space? we should probably (deprecate) enhance current REST implementation to force the user to redo some parts on payload definition side in terms of metadata. I believe I added many extension properties needed while working on the Swagger translator. > Swagger metadata includes internal java constructs > -------------------------------------------------- > > Key: TEIID-4051 > URL: https://issues.jboss.org/browse/TEIID-4051 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Affects Versions: 8.12.x > Reporter: Steven Hawkins > Fix For: 10.0 > > > From IntegrationTestRestWarGeneration the swagger metadata includes definitions for Statement, ResultSet, StreamingOutput, etc.: > ... > InputStream: > type: "object" > Statement: > type: "object" > properties: > queryTimeout: > type: "integer" > format: "int32" > closed: > type: "boolean" > default: false > resultSet: > $ref: "#/definitions/ResultSet" > ... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 May 2017