October 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5822) Move off of gitbook

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5822?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5822: --------------------------------------- Updated the travis build to use calibre 3.48 for now. > Move off of gitbook > ------------------- > > Key: TEIID-5822 > URL: https://issues.jboss.org/browse/TEIID-5822 > Project: Teiid > Issue Type: Task > Components: Documentation > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.x > > > The gitbook cli tools are now deprecated. An update to the pdf logic has caused the travis builds to break - we need to use an old node js version because the gitbook stuff uses old constructs, but that means an older distribution - which calibre does not support anymore. For now I can look at customizing the calibre install, but longer term we need to get off of gitbook publishing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5803) Seems to be not possible to POST a new entity via a navigation property to a collection

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5803?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5803. ----------------------------------- Resolution: Done Marking as resolved for 13 now that we are using the 4.7 olingo snapshot. > Seems to be not possible to POST a new entity via a navigation property to a collection > --------------------------------------------------------------------------------------- > > Key: TEIID-5803 > URL: https://issues.jboss.org/browse/TEIID-5803 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Christoph John > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > Hello Steven, > I am currently trying to post/create an entity in a collection via a relative binding path. Unfortunately, I always get an error saying > {"error":{"code":null,"message":"HTTP method 'POST' not allowed for this resource."}} > I have bound the root view to .../Account(1) from which I have a navigation property to the relevant collection. Currently I have trouble to post to collections via a navigation path. > As far as I understood from > http://docs.oasis-open.org/odata/odata/v4.01/csprd04/part1-protocol/odata... > chapter 11.4.2 this should work according to my tries below. > Might you tell me if my path via the navigation property should work for post requests or what I am doing wrong? > Directly writing to the collection is fine, i.e. something like the following: > curl --user sap:sap -i -X POST -H 'Content-Type: application/json;charset=UTF-8;IEEE754Compatible=true' -d '{"fkProfile":"1","idCode":null,"lc":"de","product_name":"A Product","brands":"A brand","energy_100g":2259,"carbohydrates_100g":60.08,"sugars_100g":10.1,"proteins_100g":24.03,"fat_100g":15.89,"saturated_fat_100g":10.0,"salt_100g":1.0}' http://localhost:18080/odata4/svc/my_nutri_diary/UserDefinedProducts > and a GET request via a navigation property path (given below) also works, but a path via a navigation property does not work when using the path in a POST request. I.e. when going via the navigation property. Example: > curl --user sap:sap -i -X POST -H 'Content-Type: application/json;charset=UTF-8;IEEE754Compatible=true' -d '{"fkProfile":"1","idCode":null,"lc":"de","product_name":"A Product","brands":"A brand","energy_100g":2259,"carbohydrates_100g":60.08,"sugars_100g":10.1,"proteins_100g":24.03,"fat_100g":15.89,"saturated_fat_100g":10.0,"salt_100g":1.0}' http://localhost:18080/odata4/svc/my_nutri_diary/Account$1$/UserDefined... > Here you find the backend metadata. They show that UserDefinedProducts_fKUserDefinedProductToAccount is simply a navigaton path from Account(xxx) to the UserDefinedProducts collection. > https://ecubed-solutions.ddnss.de/odata4/svc/my_nutri_diary/$metadata > user: sap > password: sap > Thanks a lot for your help! > Note: I am currently trying to add data via a navigation property path because my frontend library sapui5 only caches and syncs data queried via a single context binding. Hence, to be consistent via all views in my app which bind to the odata model, I need to use only one absolute binding and have to query/update other contexts via relative binding paths from this single absolute path, to allow for all frontend views to maintain data consistency -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5822) Move off of gitbook

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5822: ------------------------------------- Summary: Move off of gitbook Key: TEIID-5822 URL: https://issues.jboss.org/browse/TEIID-5822 Project: Teiid Issue Type: Task Components: Documentation Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 13.x The gitbook cli tools are now deprecated. An update to the pdf logic has caused the travis builds to break - we need to use an old node js version because the gitbook stuff uses old constructs, but that means an older distribution - which calibre does not support anymore. For now I can look at customizing the calibre install, but longer term we need to get off of gitbook publishing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5565) Drop client and other support for 1.6

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5565?page=com.atlassian.jira.plugin... ] Work on TEIID-5565 started by Steven Hawkins. --------------------------------------------- > Drop client and other support for 1.6 > ------------------------------------- > > Key: TEIID-5565 > URL: https://issues.jboss.org/browse/TEIID-5565 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Driver > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > Compatibility of the client/core code will need to be moved up to Java 8, while the project as a whole can move forward to Java 11. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5557) Restrict imports to a single schema

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5557?page=com.atlassian.jira.plugin... ] Work on TEIID-5557 started by Steven Hawkins. --------------------------------------------- > Restrict imports to a single schema > ----------------------------------- > > Key: TEIID-5557 > URL: https://issues.jboss.org/browse/TEIID-5557 > Project: Teiid > Issue Type: Quality Risk > Components: Connector API > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.x, 13.0 > > > To better align with SQL/MED and to simplify legacy import properties it would be best to restrict foreign imports to a single schema. This will remove quite a bit of confusion around potential duplicate object names. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3522) Provide Data Aggregation Extension to OData V4

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-3522?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3522. ----------------------------------- Resolution: Done Merged into 13.0 based upon the 4.7 olingo snapshot. Ideally there will be an olingo release in the next 6 weeks. > Provide Data Aggregation Extension to OData V4 > ---------------------------------------------- > > Key: TEIID-3522 > URL: https://issues.jboss.org/browse/TEIID-3522 > Project: Teiid > Issue Type: Feature Request > Components: OData > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > OData V4 specification defines extension for Data Aggregation http://docs.oasis-open.org/odata/odata-data-aggregation-ext/v4.0/cs01/oda... > Teiid should provide support for this extension. There is Olingo support on this yet. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 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 resolved TEIID-1323. ----------------------------------- Resolution: Done It is possible that given TEIID-5821 there could be a need for procedure parameter pushdown with an expression needs to be supported as well. This is a long standing issue that was only partially addressed previously. To fully address we need a new capability and a breaking method change to SQLConversionVisitor - it's possible to backport without the breaking change though. > 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, 6 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: ---------------------------------------- Just trying to simplistically reproduce this locally and I'm not seeing the same behavior. I'm using 100 tables each with 100 columns. All have a single relationship to another table. That gives me a ~550KB edm file and a 2.7 MB openapi or swagger file generated in about 7 seconds on a vm constrained to 256MB of memory. This is the same using teiid spring boot or with using a teiid embedded test using jetty. It seems like there is something more specific to the form / content of your metadata. Would it be possible for you to provide your edm file? > 2. For more complex metadata (30MB size of Edm) i can't get response in my localhost (i5 ant other). Its my mistake. That's a pretty large edm file. Can you describe that scenario? > 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 > Assignee: Steven Hawkins > 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, 6 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... ] Work on TEIIDSB-121 started by Steven Hawkins. ---------------------------------------------- > 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 > Assignee: Steven Hawkins > 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5813) Using the PG protocol the Virtual View schema items are not visible

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5813?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5813: --------------------------------------- Just confirmed I cannot reproduce this on master. > Using the PG protocol the Virtual View schema items are not visible > ------------------------------------------------------------------- > > Key: TEIID-5813 > URL: https://issues.jboss.org/browse/TEIID-5813 > Project: Teiid > Issue Type: Bug > Components: ODBC, Query Engine > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > > When using PSQL client against Teiid deployed VDB, the metadata does not show the tables/views that are defined under a virtual schema. The physical or foreign types are visible correctly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 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