April 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIIDSB-61) Not able to delete/create entity in

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-61?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIIDSB-61: ------------------------------------- So, the question should we by default add this into the Teiid starter? I had it before, but removed it later on, don't remember why :( > Not able to delete/create entity in > ------------------------------------ > > Key: TEIIDSB-61 > URL: https://issues.jboss.org/browse/TEIIDSB-61 > Project: Teiid Spring Boot > Issue Type: Bug > Reporter: Jan Safarik > Assignee: Steven Hawkins > Priority: Major > > Trying to use the teiid-spring-boot/samples/odata project, I am not able to Create, Update or Delete an entity. Tried on Customer, with Delete I get back code: TEIID30504 with message: "TEIID30504 accounts: 23503 TEIID11013:TEIID11004 Error executing statement(s): [SQL: DELETE FROM "CUSTOMER" WHERE "CUSTOMER"."SSN" = 'CST01002']". With Create (Post) I get code: TEIID30528 with message: "TEIID30528 javax.transaction.SystemException". -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-54) Provide Salesforce source support

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-54?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIIDSB-54: ----------------------------------- Assignee: Ramesh Reddy > Provide Salesforce source support > --------------------------------- > > Key: TEIIDSB-54 > URL: https://issues.jboss.org/browse/TEIIDSB-54 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Affects Versions: 1.1.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > > Salesforce data source needs to be supported. Should support the same authentication as the Syndesis -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-54) Provide Salesforce source support

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-54?page=com.atlassian.jira.plugin... ] Work on TEIIDSB-54 started by Ramesh Reddy. ------------------------------------------- > Provide Salesforce source support > --------------------------------- > > Key: TEIIDSB-54 > URL: https://issues.jboss.org/browse/TEIIDSB-54 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Affects Versions: 1.1.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > > Salesforce data source needs to be supported. Should support the same authentication as the Syndesis -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-65) OData include files are not being served correctly

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-65?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIIDSB-65: ------------------------------------- Ok. will do. As per the Auth, it should be the same in Openshift or standalone app. > OData include files are not being served correctly > -------------------------------------------------- > > Key: TEIIDSB-65 > URL: https://issues.jboss.org/browse/TEIIDSB-65 > Project: Teiid Spring Boot > Issue Type: Bug > Components: OData > Affects Versions: 1.0.3 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 1.1.0 > > > The include metadata files are not being served correctly through OData interface. > One of the reference is calculated as http://rdbms-example-odata-teiid-dataservice.apps.garys-e21d.openshiftwor... > The class tries to request from this include url and this is what causes the 406 error > see $metadata int he URL -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-61) Not able to delete/create entity in

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-61?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIIDSB-61: ------------------------------------- if you add {code} <dependency> <groupId>me.snowdrop</groupId> <artifactId>narayana-spring-boot-starter</artifactId> <version>2.1.0</version> </dependency> {code} it will add in the transaction manager to the application which gets automatically gets registered with Teiid engine to make use of it. > Not able to delete/create entity in > ------------------------------------ > > Key: TEIIDSB-61 > URL: https://issues.jboss.org/browse/TEIIDSB-61 > Project: Teiid Spring Boot > Issue Type: Bug > Reporter: Jan Safarik > Assignee: Steven Hawkins > Priority: Major > > Trying to use the teiid-spring-boot/samples/odata project, I am not able to Create, Update or Delete an entity. Tried on Customer, with Delete I get back code: TEIID30504 with message: "TEIID30504 accounts: 23503 TEIID11013:TEIID11004 Error executing statement(s): [SQL: DELETE FROM "CUSTOMER" WHERE "CUSTOMER"."SSN" = 'CST01002']". With Create (Post) I get code: TEIID30528 with message: "TEIID30528 javax.transaction.SystemException". -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-47) Determine behavior of alter statements

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-47?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIIDSB-47: --------------------------------------- I will add an option to turn off all alter effects - except for costing updates. > Determine behavior of alter statements > -------------------------------------- > > Key: TEIIDSB-47 > URL: https://issues.jboss.org/browse/TEIIDSB-47 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: core > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > > The engine allows alter statements to ephemerally (by default) change view definitions, turn on/off triggers, etc. For Spring Boot and OpenShift deployment in particular we should consider whether this should be allowable/optional behavior. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5713) Safesforce-41 translator errors

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5713?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5713: --------------------------------------- > what do you think how we should support scenarios like this where multiple same translator is available in multiple versions? We have 2 class loading issues: - multiple same source, different driver versions. - different sources with class conflicts across them. Having both a salesforce-41 and 34 at this point is effectively the first case as there aren't any classes that we need to override anymore in the 41 version. IT seems highly unlikely that someone would specifically need 36 access and 45 access at the same time in a forward looking sense. We can even consider from the ui only exposing the 41/latest initially. For a standalone user the best we can do in the either of these cases is produce a build time warning, perhaps suggesting a specific basepom configuration that will detect those scenarios. > Safesforce-41 translator errors > ------------------------------- > > Key: TEIID-5713 > URL: https://issues.jboss.org/browse/TEIID-5713 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2, 11.2.3, 12.1.1 > > > Using the Salesforce-41 translator, just loading the metadata it fails with error. I have verified this with WF and SB. I think, it is probably better to switch this version to new version, and remove this version. > {code} > Caused by: com.sforce.ws.ConnectionException: ChangeEventHeader Not a valid enumeration for type: class com.sforce.soap.partner.SoapType > at com.force.api:41//com.sforce.ws.bind.TypeMapper.readSingle(TypeMapper.java:668) > at com.force.api:41//com.sforce.ws.bind.TypeMapper.readObject(TypeMapper.java:556) > at com.force.api:41//com.sforce.soap.partner.Field.setSoapType(Field.java:1702) > at com.force.api:41//com.sforce.soap.partner.Field.loadFields1(Field.java:2039) > at com.force.api:41//com.sforce.soap.partner.Field.loadFields(Field.java:1912) > at com.force.api:41//com.sforce.soap.partner.Field.load(Field.java:1906) > at com.force.api:41//com.sforce.ws.bind.TypeMapper.readSingle(TypeMapper.java:674) > at com.force.api:41//com.sforce.ws.bind.TypeMapper.readArray(TypeMapper.java:580) > at com.force.api:41//com.sforce.ws.bind.TypeMapper.readObject(TypeMapper.java:558) > at com.force.api:41//com.sforce.soap.partner.DescribeSObjectResult.setFields(DescribeSObjectResult.java:398) > at com.force.api:41//com.sforce.soap.partner.DescribeSObjectResult.loadFields1(DescribeSObjectResult.java:1421) > at com.force.api:41//com.sforce.soap.partner.DescribeSObjectResult.loadFields(DescribeSObjectResult.java:1350) > at com.force.api:41//com.sforce.soap.partner.DescribeSObjectResult.load(DescribeSObjectResult.java:1344) > at com.force.api:41//com.sforce.ws.bind.TypeMapper.readSingle(TypeMapper.java:674) > at com.force.api:41//com.sforce.ws.bind.TypeMapper.readArray(TypeMapper.java:580) > at com.force.api:41//com.sforce.ws.bind.TypeMapper.readObject(TypeMapper.java:558) > at com.force.api:41//com.sforce.soap.partner.DescribeSObjectsResponse_element.setResult(DescribeSObjectsResponse_element.java:48) > at com.force.api:41//com.sforce.soap.partner.DescribeSObjectsResponse_element.loadFields1(DescribeSObjectsResponse_element.java:107) > at com.force.api:41//com.sforce.soap.partner.DescribeSObjectsResponse_element.loadFields(DescribeSObjectsResponse_element.java:83) > at com.force.api:41//com.sforce.soap.partner.DescribeSObjectsResponse_element.load(DescribeSObjectsResponse_element.java:77) > at com.force.api:41//com.sforce.ws.bind.TypeMapper.readSingle(TypeMapper.java:674) > at com.force.api:41//com.sforce.ws.bind.TypeMapper.readObject(TypeMapper.java:556) > at com.force.api:41//com.sforce.ws.transport.SoapConnection.bind(SoapConnection.java:180) > at com.force.api:41//com.sforce.ws.transport.SoapConnection.receive(SoapConnection.java:154) > at com.force.api:41//com.sforce.ws.transport.SoapConnection.send(SoapConnection.java:99) > at com.force.api:41//com.sforce.soap.partner.PartnerConnection.describeSObjects(PartnerConnection.java:1225) > at org.jboss.teiid.resource-adapter.salesforce-41@12.2.0-SNAPSHOT//org.teiid.resource.adapter.salesforce.SalesforceConnectionImpl.getObjectMetaData(SalesforceConnectionImpl.java:514) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-65) OData include files are not being served correctly

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-65?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIIDSB-65: --------------------------------------- > It is the service root. If one is copying and pasting this URL into fuse or any other application for integration purpose they need to know to add the "/odata4" otherwise it will end up in error. This should simply a little. I'm not sure why that is an issue. It's up to the service if there is any additional context. It's not a bad idea to have odata4 or a service name by default as the context if there will be anything else available at that same host/port - whether static files, rest access, yet another odata version, etc. If you don't want this as the default for user driven spring boot that's fine, but it should be the default for anything generated by the ui. > We do not need any. Previous auth redirects are currently supported natively in Keycloak. That's why I'm asking specifically about standalone, not openshift. Is there a good ootb experience there with keycloak? > OData include files are not being served correctly > -------------------------------------------------- > > Key: TEIIDSB-65 > URL: https://issues.jboss.org/browse/TEIIDSB-65 > Project: Teiid Spring Boot > Issue Type: Bug > Components: OData > Affects Versions: 1.0.3 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 1.1.0 > > > The include metadata files are not being served correctly through OData interface. > One of the reference is calculated as http://rdbms-example-odata-teiid-dataservice.apps.garys-e21d.openshiftwor... > The class tries to request from this include url and this is what causes the 406 error > see $metadata int he URL -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-28) Don't allow hidden schema objects to be accessible

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-28?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIIDSB-28: ---------------------------------- Fix Version/s: 1.1.0 > Don't allow hidden schema objects to be accessible > -------------------------------------------------- > > Key: TEIIDSB-28 > URL: https://issues.jboss.org/browse/TEIIDSB-28 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: core > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > To be consistent with odata access hidden schema should not be accessible even over pg. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-28) Don't allow hidden schema objects to be accessible

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-28?page=com.atlassian.jira.plugin... ] Work on TEIIDSB-28 stopped by Steven Hawkins. --------------------------------------------- > Don't allow hidden schema objects to be accessible > -------------------------------------------------- > > Key: TEIIDSB-28 > URL: https://issues.jboss.org/browse/TEIIDSB-28 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: core > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > To be consistent with odata access hidden schema should not be accessible even over pg. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2019