June 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIIDSB-107) Update Teiid version to 12.2.1

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-107?page=com.atlassian.jira.plugi... ] Ramesh Reddy resolved TEIIDSB-107. ---------------------------------- Resolution: Done > Update Teiid version to 12.2.1 > ------------------------------ > > Key: TEIIDSB-107 > URL: https://issues.jboss.org/browse/TEIIDSB-107 > Project: Teiid Spring Boot > Issue Type: Task > Components: core > Affects Versions: 1.1.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 7.4-1.1.1 > > > Update the Teiid version to 12.2.1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-107) Update Teiid version to 12.2.1

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIIDSB-107: ------------------------------------ Summary: Update Teiid version to 12.2.1 Key: TEIIDSB-107 URL: https://issues.jboss.org/browse/TEIIDSB-107 Project: Teiid Spring Boot Issue Type: Task Components: core Affects Versions: 1.1.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 1.2.0, 7.4-1.1.1 Update the Teiid version to 12.2.1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-105) Modelling a Json entitty with array of "details"

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-105?page=com.atlassian.jira.plugi... ] Ramesh Reddy resolved TEIIDSB-105. ---------------------------------- Resolution: Done > Modelling a Json entitty with array of "details" > ------------------------------------------------ > > Key: TEIIDSB-105 > URL: https://issues.jboss.org/browse/TEIIDSB-105 > Project: Teiid Spring Boot > Issue Type: Bug > Components: JPA > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.2.0 > > > When using the @JsonTable the construct only supports reading the array type of same data types, with mixed type it does not work. For ex: > {code} > [1, 1, 3] > {code} > works, but > {code} > [1, "two", 3.0] > {code} > does not work. If the user chooses to read it as a string array converting the values to match Teiid semantics it is not possible. However, when it is created as > {code} > { id: 1, desc: "two", weight: 3.0} > {code} > can be read an entity. The array form could also be modeled as an entity with single parameter as `string[]` -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-105) Modelling a Json entitty with array of "details"

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-105?page=com.atlassian.jira.plugi... ] Ramesh Reddy commented on TEIIDSB-105: -------------------------------------- In general none of the array based fragments other than simple arrays were working earlier due to an issue with code. That has been fixed now, when the entity is used with @OneToMany from Parent entity and @ManyToOne from child entity, if you define the @Id as the join key itself (as the json will not have id duplicated in child fragments as in relational tables) then data is read correctly into respective entities. For a complete example see https://github.com/teiid/teiid-spring-boot/tree/master/samples/json > Modelling a Json entitty with array of "details" > ------------------------------------------------ > > Key: TEIIDSB-105 > URL: https://issues.jboss.org/browse/TEIIDSB-105 > Project: Teiid Spring Boot > Issue Type: Bug > Components: JPA > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.2.0 > > > When using the @JsonTable the construct only supports reading the array type of same data types, with mixed type it does not work. For ex: > {code} > [1, 1, 3] > {code} > works, but > {code} > [1, "two", 3.0] > {code} > does not work. If the user chooses to read it as a string array converting the values to match Teiid semantics it is not possible. However, when it is created as > {code} > { id: 1, desc: "two", weight: 3.0} > {code} > can be read an entity. The array form could also be modeled as an entity with single parameter as `string[]` -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-105) Modelling a Json entitty with array of "details"

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-105?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIIDSB-105: --------------------------------- Fix Version/s: 1.2.0 > Modelling a Json entitty with array of "details" > ------------------------------------------------ > > Key: TEIIDSB-105 > URL: https://issues.jboss.org/browse/TEIIDSB-105 > Project: Teiid Spring Boot > Issue Type: Bug > Components: JPA > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.2.0 > > > When using the @JsonTable the construct only supports reading the array type of same data types, with mixed type it does not work. For ex: > {code} > [1, 1, 3] > {code} > works, but > {code} > [1, "two", 3.0] > {code} > does not work. If the user chooses to read it as a string array converting the values to match Teiid semantics it is not possible. However, when it is created as > {code} > { id: 1, desc: "two", weight: 3.0} > {code} > can be read an entity. The array form could also be modeled as an entity with single parameter as `string[]` -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-105) Modelling a Json entitty with array of "details"

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-105?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIIDSB-105: --------------------------------- Issue Type: Bug (was: Enhancement) > Modelling a Json entitty with array of "details" > ------------------------------------------------ > > Key: TEIIDSB-105 > URL: https://issues.jboss.org/browse/TEIIDSB-105 > Project: Teiid Spring Boot > Issue Type: Bug > Components: JPA > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.2.0 > > > When using the @JsonTable the construct only supports reading the array type of same data types, with mixed type it does not work. For ex: > {code} > [1, 1, 3] > {code} > works, but > {code} > [1, "two", 3.0] > {code} > does not work. If the user chooses to read it as a string array converting the values to match Teiid semantics it is not possible. However, when it is created as > {code} > { id: 1, desc: "two", weight: 3.0} > {code} > can be read an entity. The array form could also be modeled as an entity with single parameter as `string[]` -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-106) Provide ability to dynamically provide the URL query parameters for Rest Calls

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-106?page=com.atlassian.jira.plugi... ] Ramesh Reddy resolved TEIIDSB-106. ---------------------------------- Resolution: Done Opened up to issue the REST call to be handled entirely the user so that they can modify any way they want such that query parameters, headers, auth can be completely handled by a Function method defined by the user and configures it access to Teiid as Spring Bean. For example, see: https://github.com/teiid/teiid-spring-boot/tree/master/samples/rest > Provide ability to dynamically provide the URL query parameters for Rest Calls > ------------------------------------------------------------------------------ > > Key: TEIIDSB-106 > URL: https://issues.jboss.org/browse/TEIIDSB-106 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: JPA > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.2.0 > > > When using the rest based called on @RestConfiguration, headers can be sent as user specific values, however, there is no facility for the URL parameters. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-106) Provide ability to dynamically provide the URL query parameters for Rest Calls

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-106?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIIDSB-106: --------------------------------- Fix Version/s: 1.2.0 > Provide ability to dynamically provide the URL query parameters for Rest Calls > ------------------------------------------------------------------------------ > > Key: TEIIDSB-106 > URL: https://issues.jboss.org/browse/TEIIDSB-106 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: JPA > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.2.0 > > > When using the rest based called on @RestConfiguration, headers can be sent as user specific values, however, there is no facility for the URL parameters. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5765) Criteria Pushdown is not working on FULL OUTER JOIN

by Dmitrii Pogorelov (Jira)

[ https://issues.jboss.org/browse/TEIID-5765?page=com.atlassian.jira.plugin... ] Dmitrii Pogorelov commented on TEIID-5765: ------------------------------------------ [~shawkins] thx a lot for the quick fix, I've already checked these changes locally and it worked. Thx again! > Criteria Pushdown is not working on FULL OUTER JOIN > --------------------------------------------------- > > Key: TEIID-5765 > URL: https://issues.jboss.org/browse/TEIID-5765 > 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: Blocker > Fix For: 12.3, 12.1.2, 12.2.1 > > > Criteria Pushdown is not working on FULL OUTER JOIN (according to query plan criteria is not pushed down at all, it's in criteria of LEFT OUTER JOIN node): > {code:noformat} > ---------------------------------------------------------------------------- > OPTIMIZATION COMPLETE: > PROCESSOR PLAN: > ProjectNode(0) output=[1] [1] > SelectNode(1) output=[a.a] a.a = 1 > JoinNode(2) [MERGE JOIN (ALREADY_SORTED/ALREADY_SORTED)] [LEFT OUTER JOIN] criteria=[a.a=b.b] output=[a.a] > AccessNode(3) output=[a.a] SELECT g_0.a AS c_0 FROM test.test_a AS g_0 ORDER BY c_0 > AccessNode(4) output=[b.b] SELECT g_0.b AS c_0 FROM dwh_my.test_a AS g_0 ORDER BY c_0 > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5763) GENERATED_KEY returns NULL if used in INSTEAD OF INSERT Triggers in DDL files

by Christoph John (Jira)

[ https://issues.jboss.org/browse/TEIID-5763?page=com.atlassian.jira.plugin... ] Christoph John edited comment on TEIID-5763 at 6/12/19 3:55 PM: ---------------------------------------------------------------- Hello Steven, I am sorry, but I do not have enough Java background to be able to build and remotely debug the sources in an Eclipse environment. I hope the following will help you https://c.gmx.net/@328076122686231878/aW-zSH_GTzaajkuYGZPtbQ In the TeiidMySQL package you can find a docker-compose file with a mysql db and a teiid server with yesterdays git sources. In the dockerfile you can also see the mysql driver configuration. I tested with both variants XA and non-XA. The mysql container will be initialized with three tables which are from the simplified example in our previous discussions. The teiid container will be initialized with the relevant vdb for these tables. I also attached a curl script which sends a POST request to show the error. And finally I also added the Teiid Web Console to the container to show you the issue with missing runtime information. The second bug we discussed this week. More usage details are given in the README. Let me know if you have questions or I can be of further help! was (Author: cjohn001): Hello Steven, I am sorry, but I do not have enough Java background to be able to build and remotely debug the sources in an Eclipse environment. I hope the following will help you https://c.gmx.net/@328076122686231878/aW-zSH_GTzaajkuYGZPtbQ In the TeiidMySQL package you can find a docker-compose file with a mysql db and a teiid server with yesterdays git sources. In the dockerfile you can also see the mysql driver configuration. I tested with both variants XA and non-XA. The mysql container will be initialized with three tables which are from the simplified example in our previous discussions. The teiid container will be initialized with the relevant vdb for these tables. I also attached a curl script which sends a POST request to show the error. And finally I also added the Teiid Web Console to the container to show you the issue with missing runtime information. The second bug we discussed this week. > GENERATED_KEY returns NULL if used in INSTEAD OF INSERT Triggers in DDL files > ----------------------------------------------------------------------------- > > Key: TEIID-5763 > URL: https://issues.jboss.org/browse/TEIID-5763 > Project: Teiid > Issue Type: Bug > Affects Versions: 12.2 > Reporter: Christoph John > Assignee: Steven Hawkins > Priority: Blocker > > The issue arrised in: > https://developer.jboss.org/message/989700#989700 > Following sceanarios are given: > Variant 1: > Table Product(id), primary key = autoincrement; > Table QuicklyAddedProduct, primary key is foreign key on Product.id > Table Diary_SRC > View Diary on Diary_SRC > INSTEAD OF INSERT Trigger on Diary should : > -create new record on Product, > -get autoincremented Product.id of new record, > - create new QuicklyAddedProduct with returned Product.id as primary key > - create new Diary record with QuicklyAddedProduct > { > INSERT a new record on Product; > idProduct = CONVERT(GENERATED_KEY('idProduct'),long); // fails > } > Variant 2: > INSTEAD OF INSERT trigger on Diary should : > - create new QuicklyAddedProduct > - add Quickly added prodcut to Diary > additionally a INSTEAD OF trigger on QuicklyAddedProduct exists which: > - creates new Product record > - uses returned GENERATED_KEY(Product.id) to add record on QuicklyAddedProduct with Product.id as primary key -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2019