October 2018 - teiid-issues - Jboss List Archives

[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)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4624) Integrate with Debezium for Result set cache invalidation

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-4624?page=com.atlassian.jira.plugin... ] Steven Hawkins reopened TEIID-4624: ----------------------------------- > Integrate with Debezium for Result set cache invalidation > --------------------------------------------------------- > > Key: TEIID-4624 > URL: https://issues.jboss.org/browse/TEIID-4624 > Project: Teiid > Issue Type: Sub-task > Components: Server > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 12.x > > > Provide debezium based out of the box support for result set cache invalidation built upon the current table level update event logic - EventDistributor.dataModification -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4624) Integrate with Debezium for Result set cache invalidation

by Barry LaFond (Jira)

[ https://issues.jboss.org/browse/TEIID-4624?page=com.atlassian.jira.plugin... ] Barry LaFond closed TEIID-4624. ------------------------------- Resolution: Won't Do > Integrate with Debezium for Result set cache invalidation > --------------------------------------------------------- > > Key: TEIID-4624 > URL: https://issues.jboss.org/browse/TEIID-4624 > Project: Teiid > Issue Type: Sub-task > Components: Server > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 12.x > > > Provide debezium based out of the box support for result set cache invalidation built upon the current table level update event logic - EventDistributor.dataModification -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5523) Allow for xsd schema association with vdb.xml

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5523: ------------------------------------- Summary: Allow for xsd schema association with vdb.xml Key: TEIID-5523 URL: https://issues.jboss.org/browse/TEIID-5523 Project: Teiid Issue Type: Quality Risk Components: Build/Kits Reporter: Steven Hawkins Assignee: Steven Hawkins Using Teiid Thorntail an exception is thrown at deployment when I attempt to associate an xsd with the vdb.xml file. This would be helpful to assist with vdb editing. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

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

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/TEIID-5451?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-5451: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1619728, https://bugzilla.redhat.com/show_bug.cgi?id=1643022 Bugzilla Update: Perform > 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, 2 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 commented on TEIID-5515: --------------------------------------- The primary issue is that the attribute metadata matters for the jmx mapping - but not for dmr since we were handling all the wrapping and unwrapping on both ends. So the initial commit addresses this by removing the describe methods and correcting the attribute definitions at least to where everything works. Now to test with thorntail... Other considerations: - do we need to flatten our operations for statistics to attributes - do we need to remove or use a feature flag to expose mutative operations (add/remove source, role, etc.) > 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, 2 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 commented on TEIID-5515: --------------------------------------- Exception for cache stats: java.lang.IllegalArgumentException at org.jboss.dmr.ModelValue.getChild(ModelValue.java:115) at org.jboss.dmr.PropertyModelValue.getChild(PropertyModelValue.java:120) at org.jboss.dmr.ModelNode.get(ModelNode.java:1002) at org.jboss.as.jmx.model.TypeConverters$ComplexTypeConverter.fromModelNode(TypeConverters.java:552) at org.jboss.as.jmx.model.TypeConverters$ListTypeConverter.fromModelNode(TypeConverters.java:458) at org.jboss.as.jmx.model.TypeConverters.fromModelNode(TypeConverters.java:117) at org.jboss.as.jmx.model.ModelControllerMBeanHelper.invoke(ModelControllerMBeanHelper.java:546) at org.jboss.as.jmx.model.ModelControllerMBeanHelper.invoke(ModelControllerMBeanHelper.java:487) at org.jboss.as.jmx.model.ModelControllerMBeanServerPlugin.invoke(ModelControllerMBeanServerPlugin.java:191) at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:724) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468) > 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, 2 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 commented on TEIID-5515: --------------------------------------- That was my impression as well - it's something that they've been working towards, but has problems. > 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, 2 months

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: ------------------------------------- I think in original version we did not have Jolokia or Prometheus support, but in new versions, we may have it. But THORN-204 and THORN-1859 sound like they turned them off, I know some flags need to be modified to make them active but not sure if support available yet 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 > > > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5519) Update and Delete with WHERE clause not working for delimited flat file(header true)

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5519?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5519. ----------------------------------- Resolution: Incomplete Description There's not enough information to move forward with this issue. There is a similar forum topic that was opened. That dialog should be continued until it's determined if there is an issue needed and this can be reopened with more details. > Update and Delete with WHERE clause not working for delimited flat file(header true) > ------------------------------------------------------------------------------------ > > Key: TEIID-5519 > URL: https://issues.jboss.org/browse/TEIID-5519 > Project: Teiid > Issue Type: Bug > Affects Versions: 9.1.3 > Environment: teiid-9.1.3 WildFly running on Windows Server 2012 R2 > Reporter: Rujuta Samant > Assignee: Steven Hawkins > Priority: Major > > Hi Team, > I have observed that in case of header true delimited flatfiles for FTP/SFTP, we are unable to execute update/delete query with where clause. We are able to execute simple queries(without where clause) on Header True files succesfully. Adding to the same, we are able to execute queries succesfully in case of Delimited Header false flat files and Fixed width Flat files. > Given below is the query along with error message. > *Query* - > {code:sql} > UPDATE flatfileDeli.TRANSACTION_DTL_new SET TRANSACTION_DTL_new.product_type='sports' where TRANSACTION_DTL_new.acct_number='123'; > {code} > *Error Message* - > TEIID30253 Source UPDATE or DELETE command "UPDATE flatfileDeli.TRANSACTION_DTL_new SET acct_number = ? WHERE flatfileDeli.TRANSACTION_DTL_new.product_type = ?" contains non-pushdown constructs and no compensating action can be taken as the table lacks a unique key or the source does not support equality predicates. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 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