September 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIIDSB-121) cpu utilization on 100% when generate openapi doc by metadata

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-121?page=com.atlassian.jira.plugi... ] Ramesh Reddy commented on TEIIDSB-121: -------------------------------------- Is there anything we can do here further? > cpu utilization on 100% when generate openapi doc by metadata > ------------------------------------------------------------- > > Key: TEIIDSB-121 > URL: https://issues.jboss.org/browse/TEIIDSB-121 > Project: Teiid Spring Boot > Issue Type: Bug > Components: datasource, OData > Affects Versions: 1.2.0 > Reporter: Renat Eskenin > Priority: Major > > When i get request as > http://localhost:8080/odata/swagger.json or http://localhost:8080/odata/datasource/Account/swagger.json or http://localhost:8080/odata/datasource/swagger.json > cpu utilization 100% and i do not get any response. > We have 2 bad approach: > 1. In org.teiid.olingo.web.OpenApiHandler:151 teiid create tmp file in filesystem. > Its bad because in Docker k8s systems applications can't create any files in FS. > 2. In org.apache.xalan.transformer.TransformerImpl:709 we get system freeze (CPU utilization 100% infinite) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-122) MongoDB allow default port without configuration

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-122?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIIDSB-122: --------------------------------- Fix Version/s: 1.2.1 > MongoDB allow default port without configuration > ------------------------------------------------ > > Key: TEIIDSB-122 > URL: https://issues.jboss.org/browse/TEIIDSB-122 > Project: Teiid Spring Boot > Issue Type: Bug > Components: core > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.3.0, 1.2.1 > > > The MongoDB configuration in Syndesis allows the server definition without the port, allow the MongoDBConfiguration without port info to match the Syndesis -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-122) MongoDB allow default port without configuration

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-122?page=com.atlassian.jira.plugi... ] Ramesh Reddy resolved TEIIDSB-122. ---------------------------------- Resolution: Done > MongoDB allow default port without configuration > ------------------------------------------------ > > Key: TEIIDSB-122 > URL: https://issues.jboss.org/browse/TEIIDSB-122 > Project: Teiid Spring Boot > Issue Type: Bug > Components: core > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.3.0, 1.2.1 > > > The MongoDB configuration in Syndesis allows the server definition without the port, allow the MongoDBConfiguration without port info to match the Syndesis -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-122) MongoDB allow default port without configuration

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIIDSB-122: ------------------------------------ Summary: MongoDB allow default port without configuration Key: TEIIDSB-122 URL: https://issues.jboss.org/browse/TEIIDSB-122 Project: Teiid Spring Boot Issue Type: Bug Components: core Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 1.3.0 The MongoDB configuration in Syndesis allows the server definition without the port, allow the MongoDBConfiguration without port info to match the Syndesis -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-121) cpu utilization on 100% when generate openapi doc by metadata

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-121?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIIDSB-121: ---------------------------------------- > We have 2 bad approach: 1. This is not necessarily a bad approach - you can always allocate a volume for this. Not having access to any temp space will be an issue for this feature as the generated documents can be quite large and you don't want to have to regenerate them every time. 2. Due to the nature of the expansion to capture all of the odata options in openapi metadata coupled with using an xsl transformation mean that things can be problematic in terms of memory and in this case cpu utilization - there's a warning about that in the docs and in the original issue. What we are looking to do with the Teiid Spring Boot / openshift tooling is to have everything related to metadata pre-generated for the runtime image. This will include these openapi/swagger docs, so that it becomes a build time activity to generate them. However I'm not sure when that will be ready. In the meantime can you provide approximate details of your situation - number of tables / columns involved and any cpu/memory limits you have on your image so we can see if there are any obvious workarounds in the meantime. > cpu utilization on 100% when generate openapi doc by metadata > ------------------------------------------------------------- > > Key: TEIIDSB-121 > URL: https://issues.jboss.org/browse/TEIIDSB-121 > Project: Teiid Spring Boot > Issue Type: Bug > Components: datasource, OData > Affects Versions: 1.2.0 > Reporter: Renat Eskenin > Priority: Major > > When i get request as > http://localhost:8080/odata/swagger.json or http://localhost:8080/odata/datasource/Account/swagger.json or http://localhost:8080/odata/datasource/swagger.json > cpu utilization 100% and i do not get any response. > We have 2 bad approach: > 1. In org.teiid.olingo.web.OpenApiHandler:151 teiid create tmp file in filesystem. > Its bad because in Docker k8s systems applications can't create any files in FS. > 2. In org.apache.xalan.transformer.TransformerImpl:709 we get system freeze (CPU utilization 100% infinite) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-121) cpu utilization on 100% when generate openapi doc by metadata

by Renat Eskenin (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-121?page=com.atlassian.jira.plugi... ] Renat Eskenin updated TEIIDSB-121: ---------------------------------- Description: When i get request as http://localhost:8080/odata/swagger.json or http://localhost:8080/odata/datasource/Account/swagger.json or http://localhost:8080/odata/datasource/swagger.json cpu utilization 100% and i do not get any response. We have 2 bad approach: 1. In org.teiid.olingo.web.OpenApiHandler:151 teiid create tmp file in filesystem. Its bad because in Docker k8s systems applications can't create any files in FS. 2. In org.apache.xalan.transformer.TransformerImpl:709 we get system freeze (CPU utilization 100% infinite) was: When i get request as http://localhost:8080/odata/swagger.json or http://localhost:8080/odata/Account/swagger.json cpu utilization 100% and i do not get any response. We have 2 bad approach: 1. In org.teiid.olingo.web.OpenApiHandler:151 teiid create tmp file in filesystem. Its bad because in Docker k8s systems applications can't create any files in FS. 2. In org.apache.xalan.transformer.TransformerImpl:709 we get system freeze (CPU utilization 100% infinite) > cpu utilization on 100% when generate openapi doc by metadata > ------------------------------------------------------------- > > Key: TEIIDSB-121 > URL: https://issues.jboss.org/browse/TEIIDSB-121 > Project: Teiid Spring Boot > Issue Type: Bug > Components: datasource, OData > Affects Versions: 1.2.0 > Reporter: Renat Eskenin > Priority: Major > > When i get request as > http://localhost:8080/odata/swagger.json or http://localhost:8080/odata/datasource/Account/swagger.json or http://localhost:8080/odata/datasource/swagger.json > cpu utilization 100% and i do not get any response. > We have 2 bad approach: > 1. In org.teiid.olingo.web.OpenApiHandler:151 teiid create tmp file in filesystem. > Its bad because in Docker k8s systems applications can't create any files in FS. > 2. In org.apache.xalan.transformer.TransformerImpl:709 we get system freeze (CPU utilization 100% infinite) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-121) cpu utilization on 100% when generate openapi doc by metadata

by Renat Eskenin (Jira)

Renat Eskenin created TEIIDSB-121: ------------------------------------- Summary: cpu utilization on 100% when generate openapi doc by metadata Key: TEIIDSB-121 URL: https://issues.jboss.org/browse/TEIIDSB-121 Project: Teiid Spring Boot Issue Type: Bug Components: datasource, OData Affects Versions: 1.2.0 Reporter: Renat Eskenin When i get request as http://localhost:8080/odata/swagger.json or http://localhost:8080/odata/Account/swagger.json cpu utilization 100% and i do not get any response. We have 2 bad approach: 1. In org.teiid.olingo.web.OpenApiHandler:151 teiid create tmp file in filesystem. Its bad because in Docker k8s systems applications can't create any files in FS. 2. In org.apache.xalan.transformer.TransformerImpl:709 we get system freeze (CPU utilization 100% infinite) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-120) Update MongoDB data source generation in vdb-code-gen plugin

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-120?page=com.atlassian.jira.plugi... ] Ramesh Reddy resolved TEIIDSB-120. ---------------------------------- Assignee: Ramesh Reddy Resolution: Done Updated the template for MongoDB > Update MongoDB data source generation in vdb-code-gen plugin > ------------------------------------------------------------ > > Key: TEIIDSB-120 > URL: https://issues.jboss.org/browse/TEIIDSB-120 > Project: Teiid Spring Boot > Issue Type: Bug > Components: core > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.3.0 > > > Update the MongoDb code generation to match the new configuration created. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5820) Move the release notes to the docs

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5820?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5820. ----------------------------------- Resolution: Done Created an adoc version of the release notes and added a reference to the main docs in the kit. Tried to add a drop down version selection for docs in a header - but it looks like gitbook no longer supports general plugins, which includes the header plugin. > Move the release notes to the docs > ---------------------------------- > > Key: TEIID-5820 > URL: https://issues.jboss.org/browse/TEIID-5820 > Project: Teiid > Issue Type: Sub-task > Components: Documentation > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > Rather than having the release note nested in the wildfly kit, they should be moved to a common spot in the documentation. Wildfly specific release notes can remain in the kit. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-120) Update MongoDB data source generation in vdb-code-gen plugin

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIIDSB-120: ------------------------------------ Summary: Update MongoDB data source generation in vdb-code-gen plugin Key: TEIIDSB-120 URL: https://issues.jboss.org/browse/TEIIDSB-120 Project: Teiid Spring Boot Issue Type: Bug Components: core Reporter: Ramesh Reddy Fix For: 1.3.0 Update the MongoDb code generation to match the new configuration created. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2019