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 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)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5598) Updated teiid.io to emphasize the runtime

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5598?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-5598: ------------------------------------- Assignee: (was: Steven Hawkins) > Updated teiid.io to emphasize the runtime > ----------------------------------------- > > Key: TEIID-5598 > URL: https://issues.jboss.org/browse/TEIID-5598 > Project: Teiid > Issue Type: Task > Components: Documentation > Reporter: Steven Hawkins > Priority: Major > > Related to TEIID-5597, we should update teiid.io to better emphasize the runtime and the burgeoning tool chain / limited (wildfly free) docs. > Ideally starting from the landing page we should: > - make it clear our relationship to syndesis > - highlight the cloud tooling option > - introduce the the runtime via openshift quickstarts > - some other link for everyone else (wildfly / developers) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5598) Updated teiid.io to emphasize the runtime

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5598: ------------------------------------- Summary: Updated teiid.io to emphasize the runtime Key: TEIID-5598 URL: https://issues.jboss.org/browse/TEIID-5598 Project: Teiid Issue Type: Task Components: Documentation Reporter: Steven Hawkins Assignee: Steven Hawkins Related to TEIID-5597, we should update teiid.io to better emphasize the runtime and the burgeoning tool chain / limited (wildfly free) docs. Ideally starting from the landing page we should: - make it clear our relationship to syndesis - highlight the cloud tooling option - introduce the the runtime via openshift quickstarts - some other link for everyone else (wildfly / developers) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5597) Retire teiid.jboss.org

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5597: ------------------------------------- Summary: Retire teiid.jboss.org Key: TEIID-5597 URL: https://issues.jboss.org/browse/TEIID-5597 Project: Teiid Issue Type: Task Components: Documentation Reporter: Steven Hawkins Fix For: 12.1 The legacy site will have been unmaintained since approximately a 4/2018. We can leave archive information, such as doc and old download links in place - but all other content should be removed or ported to teiid.io. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5596) Remove the Infinispan dependency from Teiid Embedded

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5596?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5596. ----------------------------------- Resolution: Done The change makes infinispan optional, but it will be used if it exists in the embedded classpath. That has been noted in the docs/release notes. The infinispan specific config methods have been deprecated as we will likely remove that direct integration later. > Remove the Infinispan dependency from Teiid Embedded > ---------------------------------------------------- > > Key: TEIID-5596 > URL: https://issues.jboss.org/browse/TEIID-5596 > Project: Teiid > Issue Type: Task > Components: Embedded, Infinispan, Server > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0 > > > Infinispan brings a direct dependency on Teiid Embedded in runtime module. Teiid runtime already defines the abstract classes to keep the implementation of the Cache implementation dependent, however TeiiedEmbedded server configuration ignores and brings tight coupling. > Move the Infinispan Cache wrapper implementation to separate project, such that embedded is freed from dependency. > in Spring Boot I see that the version is defined by Spring's bom and not find a way to a way override that, plus given the version differences the loading of cache fails. This change should lead to plugging in an independent cache implementation like Redis or Caffeine with Teiid Embedded. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5596) Remove the Infinispan dependency from Teiid Embedded

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5596?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-5596: ----------------------------------- Assignee: Steven Hawkins (was: Ramesh Reddy) > Remove the Infinispan dependency from Teiid Embedded > ---------------------------------------------------- > > Key: TEIID-5596 > URL: https://issues.jboss.org/browse/TEIID-5596 > Project: Teiid > Issue Type: Task > Components: Embedded, Infinispan, Server > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0 > > > Infinispan brings a direct dependency on Teiid Embedded in runtime module. Teiid runtime already defines the abstract classes to keep the implementation of the Cache implementation dependent, however TeiiedEmbedded server configuration ignores and brings tight coupling. > Move the Infinispan Cache wrapper implementation to separate project, such that embedded is freed from dependency. > in Spring Boot I see that the version is defined by Spring's bom and not find a way to a way override that, plus given the version differences the loading of cache fails. This change should lead to plugging in an independent cache implementation like Redis or Caffeine with Teiid Embedded. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5592) Update or deprecate teiid-quickstarts

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5592?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5592: ---------------------------------- Fix Version/s: 12.1 (was: 12.0) > Update or deprecate teiid-quickstarts > ------------------------------------- > > Key: TEIID-5592 > URL: https://issues.jboss.org/browse/TEIID-5592 > Project: Teiid > Issue Type: Quality Risk > Components: Quick Starts > Reporter: Steven Hawkins > Assignee: Van Halbert > Priority: Major > Fix For: 12.1 > > > The last update to the quickstarts was for Teiid 10 - which should have been largely compatible with Teiid 11. However this should be reviewed and updated for Teiid 11 - or we should deprecate them and update teiid.io appropriately. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5592) Update or deprecate teiid-quickstarts

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5592?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5592: ---------------------------------- Summary: Update or deprecate teiid-quickstarts (was: Updated or deprecate teiid-quickstarts) > Update or deprecate teiid-quickstarts > ------------------------------------- > > Key: TEIID-5592 > URL: https://issues.jboss.org/browse/TEIID-5592 > Project: Teiid > Issue Type: Quality Risk > Components: Quick Starts > Reporter: Steven Hawkins > Assignee: Van Halbert > Priority: Major > Fix For: 12.1 > > > The last update to the quickstarts was for Teiid 10 - which should have been largely compatible with Teiid 11. However this should be reviewed and updated for Teiid 11 - or we should deprecate them and update teiid.io appropriately. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5220) Add support for information_schema namespace

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5220?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5220: --------------------------------------- > I was looking at this issue and I wondered why you decided to implement these tables/views under pg_catalog instead of a separate "information_schema" model/schema. [~fox123] see the first comment the metadata is specific to our pg protocol. > This way the implementation would have been closer to the ANSI-standard and also the potential issue with redirecting queries to an information_schema model added by the user would have been avoided. Yes, we may eventually reserve the information_schema schema name for our use. > Add support for information_schema namespace > -------------------------------------------- > > Key: TEIID-5220 > URL: https://issues.jboss.org/browse/TEIID-5220 > Project: Teiid > Issue Type: Bug > Components: ODBC, Query Engine > Reporter: Divyesh Vallabh > Assignee: Steven Hawkins > Priority: Major > Fix For: 10.3, 10.2.1 > > > The npgsql provider uses the the infomation_schema namespace to query meta information for tables and views. > Add support for information_schema.tables ( > https://www.postgresql.org/docs/10/static/infoschema-tables.html) to teiid > Add support for information_schema.views ( > https://www.postgresql.org/docs/10/static/infoschema-views.html) to teiid > Add support for information_schema.columns ( > https://www.postgresql.org/docs/10/static/infoschema-columns.html) to teiid -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5220) Add support for information_schema namespace

by Salvatore R (Jira)

[ https://issues.jboss.org/browse/TEIID-5220?page=com.atlassian.jira.plugin... ] Salvatore R commented on TEIID-5220: ------------------------------------ Hi [~shawkins], I was looking at this issue and I wondered why you decided to implement these tables/views under pg_catalog instead of a separate "information_schema" model/schema. This way the implementation would have been closer to the ANSI-standard and also the potential issue with redirecting queries to an information_schema model added by the user would have been avoided. > Add support for information_schema namespace > -------------------------------------------- > > Key: TEIID-5220 > URL: https://issues.jboss.org/browse/TEIID-5220 > Project: Teiid > Issue Type: Bug > Components: ODBC, Query Engine > Reporter: Divyesh Vallabh > Assignee: Steven Hawkins > Priority: Major > Fix For: 10.3, 10.2.1 > > > The npgsql provider uses the the infomation_schema namespace to query meta information for tables and views. > Add support for information_schema.tables ( > https://www.postgresql.org/docs/10/static/infoschema-tables.html) to teiid > Add support for information_schema.views ( > https://www.postgresql.org/docs/10/static/infoschema-views.html) to teiid > Add support for information_schema.columns ( > https://www.postgresql.org/docs/10/static/infoschema-columns.html) to teiid -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 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 January 2019