[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:
-------------------------------------
There are a couple of reasons I kept the default at the root as service root.
1) Simple root URL. Otherwise, we have to use something "/odata4" or "vdb-name". The user needs to be educated about it.
2) One that works with JPA model as well as the VDB based model
3) In the OpenShift when the route is created you cannot create URL with context. That means clicking on it will end up in always a 404.
Perhaps we could move "static" to a more obscure name, such that chance of conflict is minimal?
> 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)
6 years, 12 months
[JBoss JIRA] (TEIID-5706) Use streaming/iterator OData result building
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5706?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5706:
----------------------------------
Priority: Minor (was: Major)
This requires changes on the OData side as setting the response content is done in EntitySetResponse - and it doesn't fit with how we are processing expands, so it's probably a couple of days effort. Given that this will only be needed for users manually setting large pages, dropping the priority.
> Use streaming/iterator OData result building
> --------------------------------------------
>
> Key: TEIID-5706
> URL: https://issues.jboss.org/browse/TEIID-5706
> Project: Teiid
> Issue Type: Sub-task
> Components: OData
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Minor
> Fix For: 12.x
>
>
> Add support for building results off of a stream, rather than fully realizing the entity collection and then serializing.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 12 months
[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:
---------------------------------------
I don't think it's worth making that change at this time - if they are now going to have a lot of forward/backwards compatibility then the exact version isn't as meaningful.
> 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)
7 years
[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 resolved TEIIDSB-65.
---------------------------------
Resolution: Done
The issue was in the calculation of the baseURI between various different paths. Also since metadata gets cached the very first time, it can be any request.
Current Spring Boot supports
{code}
http://<h>:<p>
http://<h>:<p>/model
http://<h>:<p>/context
http://<h>:<p>/context/model
{code}
all for single VDB. Where user has the choice of setting the context (this really is SB feature, we can not turn off), then "/model" option when user also wants to expose at model level. By default "/" is at view model level, if there is only a single physical model then it takes the place of View model level in terms of URL handling.
> 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)
7 years
[JBoss JIRA] (TEIID-5713) Safesforce-41 translator errors
by Ramesh Reddy (Jira)
[ https://issues.jboss.org/browse/TEIID-5713?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-5713:
-------------------------------------
Thanks, I flip it back to salesforce-41. Should we call this salesforce-45 perhaps in this case?
> 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)
7 years
[JBoss JIRA] (TEIID-5710) Create remaining spring docs
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5710?page=com.atlassian.jira.plugin... ]
Work on TEIID-5710 started by Steven Hawkins.
---------------------------------------------
> Create remaining spring docs
> ----------------------------
>
> Key: TEIID-5710
> URL: https://issues.jboss.org/browse/TEIID-5710
> Project: Teiid
> Issue Type: Sub-task
> Components: Documentation
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.2
>
>
> Presuming that the embedded, dev, and security docs will all be available as part of their respective code (javadocs and examples), that leaves admin, caching, and client-dev as the remaining books that need a spring specific spin.
> Most of the admin guide is not applicable - but we do need to capture somewhere all of the information related to system/env properties
> Most of the caching guide is TBD - but the sections on result set and other caching are still applicable.
> Most of the client guide is applicable to spring.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years