October 2018 - teiid-issues - Jboss List Archives

[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: --------------------------------------- The WildFly subsystems are automatically mapped to JMX. Running through JConsole there appear to be some issues: - nullable operation parameters are still expected (not necessarily a pressing concern) - in many places boolean parameters are typed as string - CompositeData is used to represent non-simple type results. Exceptions arise when getting these results, such as engineStatistics - the standard configuration properties are exposed readily enough. as are the non-persistent attributes such as activeSessionCount. I'll determine where the exceptions are happening with CompositeData results. If it's just a JConsole issue we are mostly done. If not we can look at things like registering a specific engine stats mbean. I'll validate that this all works through thorntail as well. As long as jolokia integration is available (?) then Prometheus integration will be available. > 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)

7 years, 5 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.0 (was: 12.x) > 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 > Priority: Major > Fix For: 12.0 > > > 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)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5451) Upgrade infinispan translator to support JDG 7.2

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5451?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-5451: ------------------------------- Git Pull Request: https://github.com/teiid/jdg/pull/42, https://github.com/teiid/jdg/pull/43 (was: https://github.com/teiid/jdg/pull/42) > Upgrade infinispan translator to support JDG 7.2 > ------------------------------------------------ > > Key: TEIID-5451 > URL: https://issues.jboss.org/browse/TEIID-5451 > Project: Teiid > Issue Type: Enhancement > Components: Infinispan > Affects Versions: 8.12.15.6_4 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > Fix For: 8.12.15.6_4 > > > The infinispan translator requires its module.xml to have the slots added to support 7.2 JDG modules. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

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 reassigned TEIID-5515: ------------------------------------- Fix Version/s: 12.0 Assignee: Steven Hawkins > 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)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5510) Update .cli and subsystem template to use new infinispan config

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5510?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5510. ----------------------------------- Resolution: Done The cli and subsystem config have been updated as well. For some reason the cli maps directly to the infinispan configuration, but the subsystem is slightly different. > Update .cli and subsystem template to use new infinispan config > --------------------------------------------------------------- > > Key: TEIID-5510 > URL: https://issues.jboss.org/browse/TEIID-5510 > Project: Teiid > Issue Type: Sub-task > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0 > > > To avoid warnings, additional changes are needed to the cli and templates to change the eviction element to memory. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5516) Exclude hidden schemas in metadata

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5516?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5516. ----------------------------------- Resolution: Done All schemas, except for sys/sysadmin, without a read permission or any readable object will now be hidden. > Exclude hidden schemas in metadata > ---------------------------------- > > Key: TEIID-5516 > URL: https://issues.jboss.org/browse/TEIID-5516 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Driver, Query Engine > Affects Versions: 8.12.15.6_4 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0 > > Attachments: Screen_Shot_2018-10-25_at_14.36.23.png > > > See https://issues.jboss.org/browse/TEIID-2476, now that hidden tables/columns are excluded, customer is requesting that the schemas also be excluded. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 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 moved TEIIDTOOLS-519 to TEIID-5522: -------------------------------------------------- Project: Teiid (was: Teiid Tools) Key: TEIID-5522 (was: TEIIDTOOLS-519) > 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 > Reporter: Norbert Funke > Priority: Major > > 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)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5521) Add build plugins used by basepom to help with dependency handling

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5521?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5521: ---------------------------------- Fix Version/s: 12.0 > Add build plugins used by basepom to help with dependency handling > ------------------------------------------------------------------ > > Key: TEIID-5521 > URL: https://issues.jboss.org/browse/TEIID-5521 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Affects Versions: 12.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > Fix For: 12.0 > > > Utilize plugins that basebom uses, which will help reduce half the headaches you go though during the productization with versions. > plugins: > * duplicate-finder-maven-plugin > * maven-dependency-plugin > * maven-dependency-versions-check-plugin -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5490) Make long analytical results the default

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5490?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5490. ----------------------------------- Resolution: Done Updated the default and added a release note and migration note. > Make long analytical results the default > ---------------------------------------- > > Key: TEIID-5490 > URL: https://issues.jboss.org/browse/TEIID-5490 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0 > > > We should switch the default for org.teiid.longRanks to true as that better matches the behavior of most platforms. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5520) Setting longRanks to true fails to resolve views appropriately

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5520?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5520. ----------------------------------- Resolution: Done Corrected the metadata logic and updated a pg view that expected an integer result from row_number. > Setting longRanks to true fails to resolve views appropriately > -------------------------------------------------------------- > > Key: TEIID-5520 > URL: https://issues.jboss.org/browse/TEIID-5520 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Affects Versions: 11.2 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0, 11.2.1 > > > When setting longRanks to true views projecting a ranking function will fail to resolve appropriately as the TransformationMetadata state is not copied appropriately. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 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 October 2018