October 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5525) add a flag to revert to the prior behavior (TEIID-4557)

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5525?page=com.atlassian.jira.plugin... ] Work on TEIID-5525 started by Steven Hawkins. --------------------------------------------- > add a flag to revert to the prior behavior (TEIID-4557) > ------------------------------------------------------- > > Key: TEIID-5525 > URL: https://issues.jboss.org/browse/TEIID-5525 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12.14.6_4, 8.12.15.6_4 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0, 11.2.1 > > > Several customers are seeing errors[1] after https://issues.jboss.org/browse/TEIID-4557 was implemented and generally have to drop the max-active-plans to 1 for their queries to succeed. Can a flag be added to revert to the behavior prior to TEIID-4557? > [1] > ERROR [org.teiid.PROCESSOR] TEIID30019 Unexpected exception for request rcX003UtoyEg.0: org.teiid.core.TeiidComponentException: TEIID31261 Max estimated size 4,963,628,721 for a single operation/table id 85 has been exceeded. The server may need to increase the amount of disk or memory available, or decrease the number of max active plans. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5525) add a flag to revert to the prior behavior (TEIID-4557)

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5525?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5525: ---------------------------------- Fix Version/s: 12.0 11.2.1 > add a flag to revert to the prior behavior (TEIID-4557) > ------------------------------------------------------- > > Key: TEIID-5525 > URL: https://issues.jboss.org/browse/TEIID-5525 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12.14.6_4, 8.12.15.6_4 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0, 11.2.1 > > > Several customers are seeing errors[1] after https://issues.jboss.org/browse/TEIID-4557 was implemented and generally have to drop the max-active-plans to 1 for their queries to succeed. Can a flag be added to revert to the behavior prior to TEIID-4557? > [1] > ERROR [org.teiid.PROCESSOR] TEIID30019 Unexpected exception for request rcX003UtoyEg.0: org.teiid.core.TeiidComponentException: TEIID31261 Max estimated size 4,963,628,721 for a single operation/table id 85 has been exceeded. The server may need to increase the amount of disk or memory available, or decrease the number of max active plans. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5525) add a flag to revert to the prior behavior (TEIID-4557)

by Debbie Steigner (Jira)

Debbie Steigner created TEIID-5525: -------------------------------------- Summary: add a flag to revert to the prior behavior (TEIID-4557) Key: TEIID-5525 URL: https://issues.jboss.org/browse/TEIID-5525 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.12.15.6_4, 8.12.14.6_4 Reporter: Debbie Steigner Assignee: Steven Hawkins Several customers are seeing errors[1] after https://issues.jboss.org/browse/TEIID-4557 was implemented and generally have to drop the max-active-plans to 1 for their queries to succeed. Can a flag be added to revert to the behavior prior to TEIID-4557? [1] ERROR [org.teiid.PROCESSOR] TEIID30019 Unexpected exception for request rcX003UtoyEg.0: org.teiid.core.TeiidComponentException: TEIID31261 Max estimated size 4,963,628,721 for a single operation/table id 85 has been exceeded. The server may need to increase the amount of disk or memory available, or decrease the number of max active plans. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5524) Expose JMX metrics in Thorntail

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5524?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5524: ---------------------------------- Description: Teiid staus and any metrics need to be exposed through JMX, such that they can be exposed later using HAWT.IO console in OpenShift. Given THORN-1918, it may be easiest to just register a few of own mbeans. (was: Teiid staus and any metrics need to be exposed through JMX, such that they can be exposed later using HAWT.IO console in OpenShift.) > Expose JMX metrics in Thorntail > ------------------------------- > > Key: TEIID-5524 > URL: https://issues.jboss.org/browse/TEIID-5524 > Project: Teiid > Issue Type: Enhancement > Components: Embedded > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0, 11.2.1 > > > Teiid staus and any metrics need to be exposed through JMX, such that they can be exposed later using HAWT.IO console in OpenShift. Given THORN-1918, it may be easiest to just register a few of own mbeans. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5515) Teiid metrics needs to be exposed through JMX

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5515?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5515. ----------------------------------- Resolution: Done Marking the initial issue as resolved as it represents the work necessary in wildfly. TEIID-5524 will take it from here for thorntail. > Teiid metrics needs to be exposed through JMX > --------------------------------------------- > > Key: TEIID-5515 > URL: https://issues.jboss.org/browse/TEIID-5515 > Project: Teiid > Issue Type: Enhancement > Components: Embedded > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0, 11.2.1 > > > Teiid staus and any metrics need to be exposed through JMX, such that they can be exposed later using HAWT.IO console in OpenShift. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5524) Expose JMX metrics in Thorntail

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5524: ------------------------------------- Summary: Expose JMX metrics in Thorntail Key: TEIID-5524 URL: https://issues.jboss.org/browse/TEIID-5524 Project: Teiid Issue Type: Enhancement Components: Embedded Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 12.0, 11.2.1 Teiid staus and any metrics need to be exposed through JMX, such that they can be exposed later using HAWT.IO console in OpenShift. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5515) Teiid metrics needs to be exposed through JMX

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5515?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5515: ------------------------------------- Given my non-Thorntail centric view of Teiid in containerization world nowadays, I vote for independent mbeans. > Teiid metrics needs to be exposed through JMX > --------------------------------------------- > > Key: TEIID-5515 > URL: https://issues.jboss.org/browse/TEIID-5515 > Project: Teiid > Issue Type: Enhancement > Components: Embedded > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0, 11.2.1 > > > Teiid staus and any metrics need to be exposed through JMX, such that they can be exposed later using HAWT.IO console in OpenShift. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5515) Teiid metrics needs to be exposed through JMX

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5515?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5515: ---------------------------------- Fix Version/s: 11.2.1 > Teiid metrics needs to be exposed through JMX > --------------------------------------------- > > Key: TEIID-5515 > URL: https://issues.jboss.org/browse/TEIID-5515 > Project: Teiid > Issue Type: Enhancement > Components: Embedded > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0, 11.2.1 > > > Teiid staus and any metrics need to be exposed through JMX, such that they can be exposed later using HAWT.IO console in OpenShift. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5515) Teiid metrics needs to be exposed through JMX

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5515?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5515: --------------------------------------- There is no functioning jmx bridge to wildfly management mbeans in thorntail. This is described in THORN-1918 and I still see that behavior with thorntail 2.3 adding both the jmx and management fractions. So either we can work THORN-1918 or we can just in a targeted way expose some new mbeans. > Teiid metrics needs to be exposed through JMX > --------------------------------------------- > > Key: TEIID-5515 > URL: https://issues.jboss.org/browse/TEIID-5515 > Project: Teiid > Issue Type: Enhancement > Components: Embedded > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0 > > > Teiid staus and any metrics need to be exposed through JMX, such that they can be exposed later using HAWT.IO console in OpenShift. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

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 updated TEIID-5522: ---------------------------------- Component/s: Misc. Connectors Query Engine Fix Version/s: 12.x > 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 > Priority: Major > Fix For: 12.x > > > 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, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2018