October 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5821) Allow insert expressions that can be pushed to be pushed

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5821?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5821. ----------------------------------- Resolution: Done The optimizer already had logic to not be over zealous with function evaluation for query expressions - so that logic is now run for all commands. > Allow insert expressions that can be pushed to be pushed > -------------------------------------------------------- > > Key: TEIID-5821 > URL: https://issues.jboss.org/browse/TEIID-5821 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0, 12.3.1 > > > Insert expressions are always being pre-evaluated. For example with: > create foreign table t (col object) options (updatable true); > create foreign function foo (param string) returns object; > Executing: > insert into t (col) values (foo('1')) > will be split into two source executions - one to evaluate the function and another to perform the insert. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1323) Add support for pushdown of non-literal procedure parameter expressions.

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-1323?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-1323: ---------------------------------- Fix Version/s: 13.0 (was: 8.5) > Add support for pushdown of non-literal procedure parameter expressions. > ------------------------------------------------------------------------ > > Key: TEIID-1323 > URL: https://issues.jboss.org/browse/TEIID-1323 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 7.2 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > Attachments: proc_params.patch > > > We are forcing all push-down procedure arguments to be literals (for simplicity), when all expressions should be allowed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1323) Add support for pushdown of non-literal procedure parameter expressions.

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-1323?page=com.atlassian.jira.plugin... ] Steven Hawkins reopened TEIID-1323: ----------------------------------- > Add support for pushdown of non-literal procedure parameter expressions. > ------------------------------------------------------------------------ > > Key: TEIID-1323 > URL: https://issues.jboss.org/browse/TEIID-1323 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 7.2 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > Attachments: proc_params.patch > > > We are forcing all push-down procedure arguments to be literals (for simplicity), when all expressions should be allowed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

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 commented on TEIIDSB-121: --------------------------------------- 1. In k8s cluster we have timeout 1min in network gate, so to get swagger.json need (for this simple configuration) 2.5min. When we did grow timeout i can get swagger.json from service. 2. For more complex metadata (30MB size of Edm) i can't get response in my localhost (i5 ant other). Its my mistake. > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5821) Allow insert expressions that can be pushed to be pushed

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5821: ------------------------------------- Summary: Allow insert expressions that can be pushed to be pushed Key: TEIID-5821 URL: https://issues.jboss.org/browse/TEIID-5821 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 13.0, 12.3.1 Insert expressions are always being pre-evaluated. For example with: create foreign table t (col object) options (updatable true); create foreign function foo (param string) returns object; Executing: insert into t (col) values (foo('1')) will be split into two source executions - one to evaluate the function and another to perform the insert. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

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: ---------------------------------------- > And i can't get swagger.json at all. Only CPU utilization 100%. I'll have a look using something similar to what you have provided. More than likely we'd need to cut down on the amount of metadata generated. A simple workaround would probably be to split your public facing schema up into several smaller ones. How deep are your relationships? As I recall the openapi metadata generator only generates a single nested level, but I'll need to verify that. > P.S. in stateless micro-service architecture we do not have persistence layer (FS). You don't have to view this as state. It's more akin to a cache than persistence. For example you can use an emptyDir volume: https://kubernetes.io/docs/concepts/storage/volumes/#emptydir > 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, 3 months

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 edited comment on TEIIDSB-121 at 10/2/19 8:03 AM: ---------------------------------------------------------------- Ok, i have additionnal data. We have simple odata4 facade for jdbc connection (with using teiid spring-odata and teiid-spring-boot-starter). 1. Metadata size is 650kb in xml odata Edm format 2. 40 tables 3. ~100 columns in table (max) 4. 1 core in k8s cluster node and 1G memory And i can't get swagger.json at all. Only CPU utilization 100%. And if i start service locally (32G RAM, 4 core i5) then i get CPU 100% and not have swagger.json at all. P.S. in stateless micro-service architecture we do not have persistence layer (FS). was (Author: i3draven): Ok, i have additionnal data. We have simple odata4 facade for jdbc connection (with using teiid spring-odata and teiid-spring-boot-starter). 1. Metadata size is 650kb in xml odata Edm format 2. 40 tables 3. ~100 columns in table (max) 4. 1 core in k8s cluster node and 1G memory And i can't get swagger.json at all. Only CPU utilization 100%. > 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, 3 months

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 edited comment on TEIIDSB-121 at 10/2/19 7:59 AM: ---------------------------------------------------------------- Ok, i have additionnal data. We have simple odata4 facade for jdbc connection (with using teiid spring-odata and teiid-spring-boot-starter). 1. Metadata size is 650kb in xml odata Edm format 2. 40 tables 3. ~100 columns in table (max) 4. 1 core in k8s cluster node and 1G memory And i can't get swagger.json at all. Only CPU utilization 100%. was (Author: i3draven): Ok, i have additionnal data. We have simple odata4 facade for jdbc connection (with using teiid spring-odata and teiid-spring-boot-starter). 1. Metadata size is 650kb in xml odata Edm format 2. 40 tables 3. ~100 columns in table (max) 4. 1 core in k8s claster node and 1G memory And i can't get swagger.json at all. Only CPU utilization 100%. > 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, 3 months

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 edited comment on TEIIDSB-121 at 10/2/19 7:59 AM: ---------------------------------------------------------------- Ok, i have additionnal data. We have simple odata4 facade for jdbc connection (with using teiid spring-odata and teiid-spring-boot-starter). 1. Metadata size is 650kb in xml odata Edm format 2. 40 tables 3. ~100 columns in table (max) 4. 1 core in k8s claster node and 1G memory And i can't get swagger.json at all. Only CPU utilization 100%. was (Author: i3draven): Ok, i have additionnal data. We have simple odata4 facade for jdbc connection (with using teiid spring-odata and teiid-spring-boot-starter). 1. Metadata size is 650kb in xml odata Edm format 2. 40 tables 3. ~100 columns in table (max) And i can't get swagger.json at all. Only CPU utilization 100%. > 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, 3 months

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 commented on TEIIDSB-121: --------------------------------------- Ok, i have additionnal data. We have simple odata4 facade for jdbc connection (with using teiid spring-odata and teiid-spring-boot-starter). 1. Metadata size is 650kb in xml odata Edm format 2. 40 tables 3. ~100 columns in table (max) And i can't get swagger.json at all. Only CPU utilization 100%. > 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, 3 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 October 2019