August 2019 - teiid-issues - Jboss List Archives

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

by Christoph John (Jira)

Christoph John created TEIID-5803: ------------------------------------- Summary: 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 Reporter: Christoph John Assignee: Steven Hawkins Hello Steven, I am currently trying to post/create an entity into a collection via a relative binding. 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. Might you tell me if my path via the navigation property should work for post requests? 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 the following navigation property path also works, but not when using the path in a POST request. I.e. when going via the navigation property via 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... it does not work. Here you find the backend metadata: 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 as my frontend library sapui5 caches and syncs data in a single context binding only. Hence, to be consistent via all application views which bind to the model I just want to use one one absolute binding and relative data bindings from there to allow all frontend views to maintain data consistency -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5774) Javadoc cleanup

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5774?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5774. ----------------------------------- Resolution: Done Added javadoc generation to the default profile, but left it out of the travis builds - for some reason it causes things to fail with java 11. All errors have been addressed, but there are a lot of warnings still. > Javadoc cleanup > --------------- > > Key: TEIID-5774 > URL: https://issues.jboss.org/browse/TEIID-5774 > Project: Teiid > Issue Type: Sub-task > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3 > > > An open ended jira to cleanup the java doc to the point where the plugin can run with fail on error. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5745) Reduce memory overhead of ddl vdbs

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5745?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5745. ----------------------------------- Fix Version/s: (was: 12.3) Resolution: Deferred This issue largely exists in the memory footprint for xml as well - as we'll have the ddl in source metadata objects. For DDL there's more duplication of structural metadata, but we'll live with that for now. > Reduce memory overhead of ddl vdbs > ---------------------------------- > > Key: TEIID-5745 > URL: https://issues.jboss.org/browse/TEIID-5745 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > > Due to mapping to the existing vdb metadata structure we are holding a memory reference to the full ddl. At a minimum that could be replaced with a file reference. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5802) Row based security and column masking don't work correctly for materialized tables (views)

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5802?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5802: ---------------------------------- Priority: Major (was: Blocker) > Row based security and column masking don't work correctly for materialized tables (views) > ------------------------------------------------------------------------------------------ > > Key: TEIID-5802 > URL: https://issues.jboss.org/browse/TEIID-5802 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 12.0 > Environment: teiid-12.0.0 on WildFly Full 14.0.1.Final (WildFly Core 6.0.2.Final) > Reporter: Dmitrii Pogorelov > Assignee: Steven Hawkins > Priority: Major > > Row based security doesn't work for materialized tables (views). For example, having the following permissions for materialized views.test_view1 and views.test_view2 views according to query plan Teiid applies ApplySecurity rule only for views.test_view2 view but should also apply for views.test_view1 view: > {code:xml} > <data-role name="role1" any-authenticated="true" allow-create-temporary-tables="true"> > <description>Allow read only</description> > <permission> > <resource-name>dsp</resource-name> > <allow-read>true</allow-read> > </permission> > <permission> > <resource-name>views.test_view1</resource-name> > <allow-read>true</allow-read> > <condition constraint="false">col2 > 1</condition> > </permission> > <permission> > <resource-name>views.test_view2</resource-name> > <allow-read>true</allow-read> > <condition constraint="false">col0 = 'sa'</condition> > </permission> > </data-role> > {code} > The same situation is for column masking feature, see below. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-4) Provide rest access with SpringBoot

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-4?page=com.atlassian.jira.plugin.... ] Ramesh Reddy resolved TEIIDSB-4. -------------------------------- Resolution: Done Example here https://github.com/teiid/teiid-spring-boot/tree/master/samples/openapi > Provide rest access with SpringBoot > ----------------------------------- > > Key: TEIIDSB-4 > URL: https://issues.jboss.org/browse/TEIIDSB-4 > Project: Teiid Spring Boot > Issue Type: Feature Request > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.2.0 > > > The current rest access layer is based upon the generation of a war with deployment hooks in wildfly. There should be a build-time or similar mechanism to expose rest with spring boot. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-4) Provide rest access with SpringBoot

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-4?page=com.atlassian.jira.plugin.... ] Ramesh Reddy commented on TEIIDSB-4: ------------------------------------ After working through the complete example, I am looking at retiring the `REST:` metadata semantics for VDB as to keep supporting to make a complete OpenAPI document with return types and various other features as those are extensive and changing. The current implementation will only support an external OpenAPI document that matches with procedure names to `OperationId`. Any requirement for `REST:` need to be reconsidered on user request. > Provide rest access with SpringBoot > ----------------------------------- > > Key: TEIIDSB-4 > URL: https://issues.jboss.org/browse/TEIIDSB-4 > Project: Teiid Spring Boot > Issue Type: Feature Request > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.2.0 > > > The current rest access layer is based upon the generation of a war with deployment hooks in wildfly. There should be a build-time or similar mechanism to expose rest with spring boot. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5740) Create tables/procedures for query plans and vdb info

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5740?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5740: ---------------------------------- Fix Version/s: 13.0 (was: 12.3) > Create tables/procedures for query plans and vdb info > ----------------------------------------------------- > > Key: TEIID-5740 > URL: https://issues.jboss.org/browse/TEIID-5740 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > We need another mechanism for viewing plans - either a procedure or a table. We also have a lot of vdb information that is not exposed via system metadata. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5740) Create tables/procedures for query plans and vdb info

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5740?page=com.atlassian.jira.plugin... ] Work on TEIID-5740 stopped by Steven Hawkins. --------------------------------------------- > Create tables/procedures for query plans and vdb info > ----------------------------------------------------- > > Key: TEIID-5740 > URL: https://issues.jboss.org/browse/TEIID-5740 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > We need another mechanism for viewing plans - either a procedure or a table. We also have a lot of vdb information that is not exposed via system metadata. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5795) Embedded Admin deploy should handle .zip and .ddl

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5795?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5795. ----------------------------------- Resolution: Done Updated the admin deploy method to also accept -vdb.ddl. Added a deployVDBZip to Admin as well. This allows for the deployment of any type of vdb without direct access to the EmbeddedServer. > Embedded Admin deploy should handle .zip and .ddl > ------------------------------------------------- > > Key: TEIID-5795 > URL: https://issues.jboss.org/browse/TEIID-5795 > Project: Teiid > Issue Type: Enhancement > Components: AdminApi > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3 > > > The embedded admin logic currently only handles the deployment of .xml vdbs. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-219) Add a way to limit or suppress queries that exceed a threshold Cost-Based Optimizer value

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-219?page=com.atlassian.jira.plugin.... ] Steven Hawkins updated TEIID-219: --------------------------------- Fix Version/s: 13.0 (was: 12.3) > Add a way to limit or suppress queries that exceed a threshold Cost-Based Optimizer value > ----------------------------------------------------------------------------------------- > > Key: TEIID-219 > URL: https://issues.jboss.org/browse/TEIID-219 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Server > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > Client requesting an ability to impose a limit on, or suppress, any query that exceeds a cost estimate value specified by the user/administrator. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2019