January 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5633) Configure teiid-spring-boot to build on travis

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5633?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5633: ------------------------------------- spring boot already on travis :) > Configure teiid-spring-boot to build on travis > ---------------------------------------------- > > Key: TEIID-5633 > URL: https://issues.jboss.org/browse/TEIID-5633 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Affects Versions: 12.x > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Major > > Add the travis.yml file to configure to build on travis -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5620) Provide flattened jmx metrics

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5620?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5620: ------------------------------------- [~shawkins] When you mentioned about having the agent bond to have the metrics enabled in the image, I am already using the Java s2i image that has Prometheus and jolokia ports open, isn't those enough to see the metrics in hawtio/Prometheus consoles? > Provide flattened jmx metrics > ----------------------------- > > Key: TEIID-5620 > URL: https://issues.jboss.org/browse/TEIID-5620 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > Providing JMX metrics via jolokia to Prometheus does not work well with complex types. We are providing several metric sets - engine stats, worker pool stats, requests, etc. as beans which needs to be flattened. Simple parameters are ok to the metrics methods, but simple results are required. > We need to make sure that at least statistics are available on: > * number of plans waiting to be processed - this will be a primary metric for determining horizontal scale out > * amount /%of buffer memory used - this will be a primary metric for determining if pods need to be allocated with more memory/disk > Ideally alerting could be available on percent utilization - but we could also add a metric such as out of disk count to provide a hard count of exceptional conditions. > It's assumed that cpu utilization will be monitored from the pod itself - which will be a primary metric for determining if pods should be allocated with more cpu resources. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5555) Create OpenAPI (swagger) metadata document based on OData

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5555?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5555: --------------------------------------- Linking to 3scale support for OpenApi 3.0 - which is still an open issue. As of 3scale 2.4 only 1.2 and 2.0 are listed as supported. > Create OpenAPI (swagger) metadata document based on OData > --------------------------------------------------------- > > Key: TEIID-5555 > URL: https://issues.jboss.org/browse/TEIID-5555 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Critical > Fix For: 12.1 > > > Automatically generate Swagger metadata document based on OData metadata such the tools like 3Scale can understand the metadata through existing plugins until OData specific plugin is generated. Only swagger 2.0 document is considered for now. 3.0 support is not considered. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

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

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-4051?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-4051: ------------------------------------- Fix Version/s: 12.1 (was: 12.x) Assignee: Steven Hawkins (was: 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: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > 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.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5555) Create OpenAPI (swagger) metadata document based on OData

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5555?page=com.atlassian.jira.plugin... ] Work on TEIID-5555 started by Steven Hawkins. --------------------------------------------- > Create OpenAPI (swagger) metadata document based on OData > --------------------------------------------------------- > > Key: TEIID-5555 > URL: https://issues.jboss.org/browse/TEIID-5555 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Critical > Fix For: 12.1 > > > Automatically generate Swagger metadata document based on OData metadata such the tools like 3Scale can understand the metadata through existing plugins until OData specific plugin is generated. Only swagger 2.0 document is considered for now. 3.0 support is not considered. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

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

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-4051?page=com.atlassian.jira.plugin... ] Work on TEIID-4051 started by Steven Hawkins. --------------------------------------------- > 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: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > 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.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5523) Allow for xsd schema association with vdb.xml

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5523?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5523: ---------------------------------- Fix Version/s: 12.x (was: 12.1) Priority: Minor (was: Major) > Allow for xsd schema association with vdb.xml > --------------------------------------------- > > Key: TEIID-5523 > URL: https://issues.jboss.org/browse/TEIID-5523 > Project: Teiid > Issue Type: Quality Risk > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 12.x > > > Using Teiid Thorntail an exception is thrown at deployment when I attempt to associate an xsd with the vdb.xml file. This would be helpful to assist with vdb editing. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5620) Provide flattened jmx metrics

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5620?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIID-5620 at 1/30/19 9:27 AM: ---------------------------------------------------------------- >From https://github.com/prometheus/jmx_exporter and https://jolokia.org/reference/html/protocol.html#serialization-mxbean compositedata is fine, it just requires some additional keys in the export definition. I'll test that out as well. It likely means that we'll keep the existing admin/jmx bean structures and only add flattened values for the most important metrics. was (Author: shawkins): >From https://github.com/prometheus/jmx_exporter compositedata is fine, it just requires some additional keys in the export definition. I'll test that out as well. It likely means that we'll keep the existing admin/jmx bean structures and only add flattened values for the most important metrics. > Provide flattened jmx metrics > ----------------------------- > > Key: TEIID-5620 > URL: https://issues.jboss.org/browse/TEIID-5620 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > Providing JMX metrics via jolokia to Prometheus does not work well with complex types. We are providing several metric sets - engine stats, worker pool stats, requests, etc. as beans which needs to be flattened. Simple parameters are ok to the metrics methods, but simple results are required. > We need to make sure that at least statistics are available on: > * number of plans waiting to be processed - this will be a primary metric for determining horizontal scale out > * amount /%of buffer memory used - this will be a primary metric for determining if pods need to be allocated with more memory/disk > Ideally alerting could be available on percent utilization - but we could also add a metric such as out of disk count to provide a hard count of exceptional conditions. > It's assumed that cpu utilization will be monitored from the pod itself - which will be a primary metric for determining if pods should be allocated with more cpu resources. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5634) Change teiid-spring-boot pom so that samples are not built on release

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5634?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5634: ------------------------------------- Any spring boot specific JIRAs now need to be on https://issues.jboss.org/projects/TEIIDSB/issues > Change teiid-spring-boot pom so that samples are not built on release > --------------------------------------------------------------------- > > Key: TEIID-5634 > URL: https://issues.jboss.org/browse/TEIID-5634 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Affects Versions: 12.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > > The pom needs to be changed so that the samples are not built as part of the release. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5634) Change teiid-spring-boot pom so that samples are not built on release

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5634?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-5634: ------------------------------- Summary: Change teiid-spring-boot pom so that samples are not built on release (was: Change pom so that samples are not built on release) > Change teiid-spring-boot pom so that samples are not built on release > --------------------------------------------------------------------- > > Key: TEIID-5634 > URL: https://issues.jboss.org/browse/TEIID-5634 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Affects Versions: 12.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > > The pom needs to be changed so that the samples are not built as part of the release. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2019