January 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5599) When creating an entity via POST message, it is expected, that the returned message includes the primary key of the newly created instance. This is not the case currently

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5599?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5599: --------------------------------------- It doesn't see like the idProfile should be needed in the insert/post if it is auto-increment. What happens when you do not specify it? Also what does the OData metadata for the entity look like, and what does the Teiid/source metadata look like? > When creating an entity via POST message, it is expected, that the returned message includes the primary key of the newly created instance. This is not the case currently > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-5599 > URL: https://issues.jboss.org/browse/TEIID-5599 > Project: Teiid > Issue Type: Bug > Reporter: Christoph John > Assignee: Steven Hawkins > Priority: Critical > > The following communication shows the issue. What I am doing here is to create a new Account entity via post request. My underlaying mysql database requires the primary key in the table to be set to NN (not null), hence, a value must be provided. Moreover the primary key is set to autoincrement and is generated by the database. The only execepted value here seems to be, to provide the key with value=0. The object is created in the database as expected. However, Teiid answers with the created object, but again with the primary key (idProfile) set as zero, instead to provide the newly created primary key. > POST Account HTTP/1.1 > Accept:application/json;odata.metadata=minimal;IEEE754Compatible=true > Accept-Language:de-DE > Content-Type:application/json;charset=UTF-8;IEEE754Compatible=true > {"uuidUser":"65820574-7525-463b-9d20-5ee133a06b94","idProfile":"0"} > --batch_id-1547485733072-21 > Content-Type:application/http > Content-Transfer-Encoding:binary > The response: > HTTP/1.1 201 Created > Location: http://localhost/odata4/svc/my_nutri_diary/Account(0) > Content-Type: application/json;ieee754compatible=true;odata.metadata=minimal > Content-Length: 147 > {"@odata.context":"http://localhost/odata4/svc/my_nutri_diary/$metadata#Account","idProfile":"0","uuidUser":"65820574-7525-463b-9d20-5ee133a06b94"} > --batch_e834eb7c-df0d-4e22-a423-78cd3638955f > Content-Type: application/http > Content-Transfer-Encoding: binary -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5602) Move Teiid Spring Boot to Teiid 12 version

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIID-5602: ----------------------------------- Summary: Move Teiid Spring Boot to Teiid 12 version Key: TEIID-5602 URL: https://issues.jboss.org/browse/TEIID-5602 Project: Teiid Issue Type: Task Reporter: Ramesh Reddy Assignee: Ramesh Reddy Move the current version supported by teiid spring boot to Teiid 12 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5521) Add build plugins used by basepom to help with dependency handling

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5521?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-5521: ---------------------------------- Assignee: Steven Hawkins (was: Van Halbert) > Add build plugins used by basepom to help with dependency handling > ------------------------------------------------------------------ > > Key: TEIID-5521 > URL: https://issues.jboss.org/browse/TEIID-5521 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Affects Versions: 12.x > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > Utilize plugins that basebom uses, which will help reduce half the headaches you go though during the productization with versions. > plugins: > * duplicate-finder-maven-plugin > * maven-dependency-plugin > * maven-dependency-versions-check-plugin -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5600) Use Caffeine as default cache implementation with Teiid Spring Boot applications

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5600?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-5600: -------------------------------- Summary: Use Caffeine as default cache implementation with Teiid Spring Boot applications (was: Use Caffine as default cache implementation with Teiid Spring Boot applications) > Use Caffeine as default cache implementation with Teiid Spring Boot applications > -------------------------------------------------------------------------------- > > Key: TEIID-5600 > URL: https://issues.jboss.org/browse/TEIID-5600 > Project: Teiid > Issue Type: Enhancement > Components: spring-boot > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > > Currently, Teiid Spring Boot uses LRU based cache as default caching layer, this should be replaced with [caffeine|https://github.com/ben-manes/caffeine] -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5601) OData needs to account for source order and org.teiid.defaultNullOrder

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5601: ------------------------------------- Summary: OData needs to account for source order and org.teiid.defaultNullOrder Key: TEIID-5601 URL: https://issues.jboss.org/browse/TEIID-5601 Project: Teiid Issue Type: Quality Risk Components: OData Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 12.1 Teiid's default null handling (low) matches that of the odata spec. However we don't have strict enforcement that pushdown order bys must match that ordering - only an option to do so if it's supported by the source org.teiid.pushdownDefaultOrderBy. We also have org.teiid.defaultNullOrder which can be set to something other than low. In either of those cases the returned ordering will not match the spec: http://docs.oasis-open.org/odata/odata/v4.01/cs01/part1-protocol/odata-v4... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5600) Use Caffine as default cache implementation with Teiid Spring Boot applications

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5600?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-5600: -------------------------------- Description: Currently, Teiid Spring Boot uses LRU based cache as default caching layer, this should be replaced with [caffeine|https://github.com/ben-manes/caffeine] (was: Currently, Teiid Spring Boot uses LRU based cache as default caching layer, this should be replaced with [caffine|https://github.com/ben-manes/caffeine]) > Use Caffine as default cache implementation with Teiid Spring Boot applications > ------------------------------------------------------------------------------- > > Key: TEIID-5600 > URL: https://issues.jboss.org/browse/TEIID-5600 > Project: Teiid > Issue Type: Enhancement > Components: spring-boot > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > > Currently, Teiid Spring Boot uses LRU based cache as default caching layer, this should be replaced with [caffeine|https://github.com/ben-manes/caffeine] -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5600) Use Caffine as default cache implementation with Teiid Spring Boot applications

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIID-5600: ----------------------------------- Summary: Use Caffine as default cache implementation with Teiid Spring Boot applications Key: TEIID-5600 URL: https://issues.jboss.org/browse/TEIID-5600 Project: Teiid Issue Type: Enhancement Components: spring-boot Reporter: Ramesh Reddy Assignee: Ramesh Reddy Currently, Teiid Spring Boot uses LRU based cache as default caching layer, this should be replaced with [caffine|https://github.com/ben-manes/caffeine] -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5560) Make Spring Boot port of Teiid library to support VDB deployment

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5560?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-5560. --------------------------------- Fix Version/s: 12.0 Resolution: Done Support will be available in 1.0.2 version > Make Spring Boot port of Teiid library to support VDB deployment > ---------------------------------------------------------------- > > Key: TEIID-5560 > URL: https://issues.jboss.org/browse/TEIID-5560 > Project: Teiid > Issue Type: Feature Request > Components: spring-boot > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 12.0 > > > Spring Boot majorly focuses on the JPA style programming for data virtualization where it gives developers the ability to define the Entity model whereby the VDB internals required are automatically generated deployed. > In addition to the above, this library also should provide ways to deploy an existing VDB as Thorntail/WildFly does. There should be a process defined to take VDB and create an immutable process with it. It is expected to be used in the generation of OpenShift images for Teiid. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5066) Move resource-adapters configuration style more adaptable to Spring/OpenShift based datasources

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5066?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-5066. --------------------------------- Resolution: Out of Date > Move resource-adapters configuration style more adaptable to Spring/OpenShift based datasources > ----------------------------------------------------------------------------------------------- > > Key: TEIID-5066 > URL: https://issues.jboss.org/browse/TEIID-5066 > Project: Teiid > Issue Type: Enhancement > Components: Connector API > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 12.x > > > The current configuration in the resource-adapters, i.e. ManagedConnectionFactory and managed connection are so tightly integrated with JCA semantics that use of this connection code else where in environments like Spring Boot or Embedded or OpenShift makes it either cumbersome or impossible. > All resource-adapter modules need to be refactored such that JCA semantics are add-ons rather than main part of it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5599) When creating an entity via POST message, it is expected, that the returned message includes the primary key of the newly created instance. This is not the case currently

by Christoph John (Jira)

Christoph John created TEIID-5599: ------------------------------------- Summary: When creating an entity via POST message, it is expected, that the returned message includes the primary key of the newly created instance. This is not the case currently Key: TEIID-5599 URL: https://issues.jboss.org/browse/TEIID-5599 Project: Teiid Issue Type: Bug Reporter: Christoph John Assignee: Steven Hawkins The following communication shows the issue. What I am doing here is to create a new Account entity via post request. My underlaying mysql database requires the primary key in the table to be set to NN (not null), hence, a value must be provided. Moreover the primary key is set to autoincrement and is generated by the database. The only execepted value here seems to be, to provide the key with value=0. The object is created in the database as expected. However, Teiid answers with the created object, but again with the primary key (idProfile) set as zero, instead to provide the newly created primary key. POST Account HTTP/1.1 Accept:application/json;odata.metadata=minimal;IEEE754Compatible=true Accept-Language:de-DE Content-Type:application/json;charset=UTF-8;IEEE754Compatible=true {"uuidUser":"65820574-7525-463b-9d20-5ee133a06b94","idProfile":"0"} --batch_id-1547485733072-21 Content-Type:application/http Content-Transfer-Encoding:binary The response: HTTP/1.1 201 Created Location: http://localhost/odata4/svc/my_nutri_diary/Account(0) Content-Type: application/json;ieee754compatible=true;odata.metadata=minimal Content-Length: 147 {"@odata.context":"http://localhost/odata4/svc/my_nutri_diary/$metadata#Account","idProfile":"0","uuidUser":"65820574-7525-463b-9d20-5ee133a06b94"} --batch_e834eb7c-df0d-4e22-a423-78cd3638955f Content-Type: application/http Content-Transfer-Encoding: binary -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2019