February 2019 - teiid-issues - Jboss List Archives

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

by dalex dalex (Jira)

dalex dalex created TEIID-5668: ---------------------------------- Summary: 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 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)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5605) widenUnsignedTypes does not account for long/bigint

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5605?page=com.atlassian.jira.plugin... ] Work on TEIID-5605 started by Steven Hawkins. --------------------------------------------- > widenUnsignedTypes does not account for long/bigint > --------------------------------------------------- > > Key: TEIID-5605 > URL: https://issues.jboss.org/browse/TEIID-5605 > Project: Teiid > Issue Type: Quality Risk > Components: JDG Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > An unsigned long/bigint from a database will still be mapped to a teiid long - which will have issues with values above max_long. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5604) Issue with javadoc plugin

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5604?page=com.atlassian.jira.plugin... ] Work on TEIID-5604 started by Steven Hawkins. --------------------------------------------- > Issue with javadoc plugin > ------------------------- > > Key: TEIID-5604 > URL: https://issues.jboss.org/browse/TEIID-5604 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > With the 12.0.0 release it was missed that version.javadoc.plugin was not set in the root pom.xml - it had previously come from jboss parent. Using either the new version 3.0.1 or the old 2.10.4 (from the 11.2 jboss parent) results in a lot of javadoc issues that were previously ignored. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5513) Fully automate release

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5513?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5513: ---------------------------------- Fix Version/s: 12.2 (was: 12.1) outstanding tasks: - doc release, javacc grammar generation / branching if needed - adding signing, jboss.org credentials to travis > Fully automate release > ---------------------- > > Key: TEIID-5513 > URL: https://issues.jboss.org/browse/TEIID-5513 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2 > > > We should add a fully automated release on the creation of a tag. > One outstanding task is to clean up the javacc doc generation and link that with the doc release as well. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5619) Provide tables representing admin information

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5619?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5619: ---------------------------------- Fix Version/s: 12.2 (was: 12.1) > Provide tables representing admin information > --------------------------------------------- > > Key: TEIID-5619 > URL: https://issues.jboss.org/browse/TEIID-5619 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2 > > > Information provided over the admin api about sessions, requests, transactions, etc. should also be available via system tables. > Similarly many of the admin operations could be provided as system procedures - kill session, flush cache, etc. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-219) Add a way to limit or suppress queries that exceed a threshold Cost-Based Optimizer value

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-219?page=com.atlassian.jira.plugin.... ] Steven Hawkins updated TEIID-219: --------------------------------- Fix Version/s: 12.2 (was: 12.1) > Add a way to limit or suppress queries that exceed a threshold Cost-Based Optimizer value > ----------------------------------------------------------------------------------------- > > Key: TEIID-219 > URL: https://issues.jboss.org/browse/TEIID-219 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Server > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2 > > > Client requesting an ability to impose a limit on, or suppress, any query that exceeds a cost estimate value specified by the user/administrator. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4251) Built in support for Postgres DB as materialization target

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-4251?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4251: ---------------------------------- Fix Version/s: 12.2 (was: 12.1) > Built in support for Postgres DB as materialization target > ---------------------------------------------------------- > > Key: TEIID-4251 > URL: https://issues.jboss.org/browse/TEIID-4251 > Project: Teiid > Issue Type: Sub-task > Components: Server > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2 > > > If Postgres database is available along with install or assumed that it is available, then some of the materialization task can be automated, like > - Creation of a common STATUS table > - Creation of the materilization targets (create views on dbms) > - On load, on undeploy and load scripts for all the materialization views > We need to device a way this to be pluggable, such that based on success of this, we can provide additional support for other sources. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5582) xml format option is ignored by odata crossjoin

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5582?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5582. ----------------------------------- Resolution: Done Added an error, rather than just ignoring. > xml format option is ignored by odata crossjoin > ----------------------------------------------- > > Key: TEIID-5582 > URL: https://issues.jboss.org/browse/TEIID-5582 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > Since we have a custom serializer that is only implemented for json, the use of a format option is ignored for cross join queries. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5582) xml format option is ignored by odata crossjoin

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5582?page=com.atlassian.jira.plugin... ] Work on TEIID-5582 started by Steven Hawkins. --------------------------------------------- > xml format option is ignored by odata crossjoin > ----------------------------------------------- > > Key: TEIID-5582 > URL: https://issues.jboss.org/browse/TEIID-5582 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > Since we have a custom serializer that is only implemented for json, the use of a format option is ignored for cross join queries. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5522) Avoid pushing join to datasource if DS cannot handle 1600+ columns

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5522?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5522. ----------------------------------- Resolution: Done Added a new method ExecutionFactory.getMaxProjectedColumns to limit how much can be pushed - this will not subdivide a single table, but will prevent joins. It also can rely on an estimate on the number of output columns, so that we don't incur running rule assign output elements again. > Avoid pushing join to datasource if DS cannot handle 1600+ columns > ------------------------------------------------------------------- > > Key: TEIID-5522 > URL: https://issues.jboss.org/browse/TEIID-5522 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors, Query Engine > Reporter: Norbert Funke > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > Problem: I am trying to create a wide view (~5000 columns), which works across data sources fine JDV. However, when I try to create the view with a join on 2+ table from data source, the optimizer pushes down the join to the source. The current source cannot handle more then ~1600 columns. > Example: When trying to join Member_DX1 and Member_DX2 at client, JDV pushes the enter code herecombined join to postgres as one getting the too max column error. > /* TABLE 1 */ > CREATE VIEW Member_DX1 ( > MEMB_BID Integer > , DX130402000000 Integer > , DX180608000000 Integer > , DX20401070000 Integer > .... /* 1000 more */ > as > SELECT dx.memb_bid > , case dx.EPI_1_DX4 when 130402000000 then 1 else 0 END as DX130402000000 > , case dx.EPI_1_DX4 when 180608000000 then 1 else 0 END as DX180608000000 > , case dx.EPI_1_DX4 when 20401070000 then 1 else 0 END as DX20401070000 > ... > FROM BDR.ENH_EPI_DETAIL dx > /* TABLE 2 */ > CREATE VIEW Member_DX2 ( > MEMB_BID Integer > , DX200102010000 Integer > , DX90125000000 Integer > , DX160603070000 Integer > ... /* 1000 more ... > SELECT dx.memb_bid /* FOREIGN TABLE */ > , case dx.EPI_1_DX4 when 200102010000 then 1 else 0 END as DX200102010000 > , case dx.EPI_1_DX4 when 90125000000 then 1 else 0 END as DX90125000000 > , case dx.EPI_1_DX4 when 160603070000 then 1 else 0 END as DX160603070000 > ...`enter code here` > FROM BDR.ENH_EPI_DETAIL dx; > then my query in (e.g. dBeaver) looks like this: > SELECT * from Member_DX1 dx1 > join Member_DX2 dx2 > on dx1.MEMB_BID = dx2.MEMB_BID -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 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 February 2019