February 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5667) Update Infinispan Connector modules to support Infinispan 7.3 Client jars

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5667?page=com.atlassian.jira.plugin... ] Van Halbert edited comment on TEIID-5667 at 2/25/19 4:13 PM: ------------------------------------------------------------- The hot rod client zip has been discontinued and the modules are now rolled into the eap modules zip: jboss-datagrid-7.3.0-eap-modules.zip was (Author: van.halbert): The hot rod client zip has been discontinued and the modules are now rolled into the [eap modules| jboss-datagrid-7.3.0-eap-modules.zip ] zip. > Update Infinispan Connector modules to support Infinispan 7.3 Client jars > ------------------------------------------------------------------------- > > Key: TEIID-5667 > URL: https://issues.jboss.org/browse/TEIID-5667 > Project: Teiid > Issue Type: Enhancement > Components: JDG Connector > Affects Versions: 8.12.17.6_4 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > > The Infinispan connector needs the module updated to support the Infinispan 7.3 client jar's. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5667) Update Infinispan Connector modules to support Infinispan 7.3 Client jars

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5667?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-5667: ------------------------------------ The hot rod client zip has been discontinued and the modules are now rolled into the [eap modules| jboss-datagrid-7.3.0-eap-modules.zip ] zip. > Update Infinispan Connector modules to support Infinispan 7.3 Client jars > ------------------------------------------------------------------------- > > Key: TEIID-5667 > URL: https://issues.jboss.org/browse/TEIID-5667 > Project: Teiid > Issue Type: Enhancement > Components: JDG Connector > Affects Versions: 8.12.17.6_4 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > > The Infinispan connector needs the module updated to support the Infinispan 7.3 client jar's. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5667) Update Infinispan Connector modules to support Infinispan 7.3 Client jars

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5667?page=com.atlassian.jira.plugin... ] Van Halbert resolved TEIID-5667. -------------------------------- Release Notes Text: Due to a change in the jdg hot rod client, the following solution will need to highlighted in order for JDG 7.3 hot rod client to work. [https://access.redhat.com/documentation/en-us/red_hat_data_grid/7.3/html/...] Resolution: Done > Update Infinispan Connector modules to support Infinispan 7.3 Client jars > ------------------------------------------------------------------------- > > Key: TEIID-5667 > URL: https://issues.jboss.org/browse/TEIID-5667 > Project: Teiid > Issue Type: Enhancement > Components: JDG Connector > Affects Versions: 8.12.17.6_4 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > > The Infinispan connector needs the module updated to support the Infinispan 7.3 client jar's. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5645) using an alter to add a key to a view doesn't work unless columns are explicitly declared

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5645?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5645. ----------------------------------- Resolution: Done Added late resolving of key columns in the view with no columns case. > using an alter to add a key to a view doesn't work unless columns are explicitly declared > ----------------------------------------------------------------------------------------- > > Key: TEIID-5645 > URL: https://issues.jboss.org/browse/TEIID-5645 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > DDL such as: > create view v as select 1 as c1, 2 as c2; > alter view v add primary key (c1); > does not work because the columns are not defined for the view until metadata validation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-25) Minimize exposure of the vdb version

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-25?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIIDSB-25. --------------------------------- Fix Version/s: 1.0.3 Resolution: Partially Completed I removed the version usage from examples. In the odata api or jdbc connection since there is single VDB there is no need to define the version at all. > Minimize exposure of the vdb version > ------------------------------------ > > Key: TEIIDSB-25 > URL: https://issues.jboss.org/browse/TEIIDSB-25 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.0.3 > > > We need to ensure that the vdb version is not exposed as a primary concept - it may still exist in the logs and exception messages just due to the how much work that would take to correct. In every other respect - documentation, ddl parsing, connection strings, etc. it must not be required. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-41) Reduce dependency chain with hibernate-tools.jar

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-41?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIIDSB-41. --------------------------------- Fix Version/s: 1.0.3 Resolution: Done > Reduce dependency chain with hibernate-tools.jar > ------------------------------------------------ > > Key: TEIIDSB-41 > URL: https://issues.jboss.org/browse/TEIIDSB-41 > Project: Teiid Spring Boot > Issue Type: Task > Components: core > Affects Versions: 1.0.3 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.0.3 > > > hibernate-tools.jar brings in lot of eclipse based dependencies (12). Investigate and see if these can be removed from the dependency chain. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5656) DDL based import statement incorrectly parses the foreign schema name

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5656?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-5656. --------------------------------- Resolution: Done Added per Steve's suggestion with escape char support. > DDL based import statement incorrectly parses the foreign schema name > --------------------------------------------------------------------- > > Key: TEIID-5656 > URL: https://issues.jboss.org/browse/TEIID-5656 > Project: Teiid > Issue Type: Bug > Components: VDB > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 12.1 > > > The DDL import statement like > {code} > IMPORT FOREIGN SCHEMA public FROM SERVER sampledb INTO accounts OPTIONS("importer.useFullSchemaName" 'false'); > {code} > does not set the "importer.schemaPattern" to "public" instead it sets to "importer.schemaName" property to "public" in runtime thus invalidating its use. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5668) Wrong results on left join + aggregation

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5668?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5668: ---------------------------------- Priority: Blocker (was: Major) > Wrong results on left join + aggregation > ---------------------------------------- > > Key: TEIID-5668 > URL: https://issues.jboss.org/browse/TEIID-5668 > 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: dalex dalex > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 12.1, 12.0.1, 11.2.3 > > Attachments: wrong_count_results_1.jpg, wrong_count_results_2.jpg > > > When using a query with a left join between tables from different schemes and count it produces wrong results. The workflow for reproducing the bug contains two example queries. The only difference between these queries is the order of the counts in select clause. The first query returns wrong results (the output of the "count(b.SalesPersonID)" field). > Additional info: a) the wrong count results are the distinct values b) occurs also with other aggregations. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5668) Wrong results on left join + aggregation

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5668?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5668. ----------------------------------- Fix Version/s: 12.1 12.0.1 11.2.3 Resolution: Done There have been several issues related to this style of query. In limited circumstances we are allowed to push the aggregation to one side of the join - but having aggregates on each side that are cardinality dependent is not something that the logic fully accounts for. For now the fix is to not push the decomposed aggregation. > Wrong results on left join + aggregation > ---------------------------------------- > > Key: TEIID-5668 > URL: https://issues.jboss.org/browse/TEIID-5668 > 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: dalex dalex > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1, 12.0.1, 11.2.3 > > Attachments: wrong_count_results_1.jpg, wrong_count_results_2.jpg > > > When using a query with a left join between tables from different schemes and count it produces wrong results. The workflow for reproducing the bug contains two example queries. The only difference between these queries is the order of the counts in select clause. The first query returns wrong results (the output of the "count(b.SalesPersonID)" field). > Additional info: a) the wrong count results are the distinct values b) occurs also with other aggregations. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5668) Wrong results on left join + aggregation

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5668?page=com.atlassian.jira.plugin... ] Work on TEIID-5668 started by Steven Hawkins. --------------------------------------------- > Wrong results on left join + aggregation > ---------------------------------------- > > Key: TEIID-5668 > URL: https://issues.jboss.org/browse/TEIID-5668 > 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: dalex dalex > Assignee: Steven Hawkins > Priority: Major > Attachments: wrong_count_results_1.jpg, wrong_count_results_2.jpg > > > When using a query with a left join between tables from different schemes and count it produces wrong results. The workflow for reproducing the bug contains two example queries. The only difference between these queries is the order of the counts in select clause. The first query returns wrong results (the output of the "count(b.SalesPersonID)" field). > Additional info: a) the wrong count results are the distinct values b) occurs also with other aggregations. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2019