January 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5583) Provide ability to monitor how much memory matviews are using

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5583?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5583. ----------------------------------- Resolution: Won't Fix Marking as won't fix for now - until there's a determination of what's needed. The residual heap memory footprint of a materialized view will be proportional to the number of rows / working page size - but is generally small enough as to not be a primary consideration when determining the overall heap. The actual page data will swap to disk as needed. The rule of thumb from the docs is conservative as to allow for plenty of working heap space, retaining soft references to index pages, etc. > Provide ability to monitor how much memory matviews are using > ------------------------------------------------------------- > > Key: TEIID-5583 > URL: https://issues.jboss.org/browse/TEIID-5583 > Project: Teiid > Issue Type: Enhancement > Reporter: Colin Mondesir > Assignee: Steven Hawkins > Priority: Major > > In the docs it says "Internal materialization (and temp tables in general) have memory overhead for each page. A rough guideline is that there can be 100 million rows in all materialized tables across all VDBs for every gigabyte of heap." > But we have no feature that allows us to monitor how exactly how much memory matviews are actually using, this makes adjusting the heap to match changing requirement difficult. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5598) Updated teiid.io to emphasize the runtime

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5598?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5598: ---------------------------------- Fix Version/s: 12.1 > Updated teiid.io to emphasize the runtime > ----------------------------------------- > > Key: TEIID-5598 > URL: https://issues.jboss.org/browse/TEIID-5598 > Project: Teiid > Issue Type: Task > Components: Documentation > Reporter: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > Related to TEIID-5597, we should update teiid.io to better emphasize the runtime and the burgeoning tool chain / limited (wildfly free) docs. > Ideally starting from the landing page we should: > - make it clear our relationship to syndesis > - highlight the cloud tooling option > - introduce the the runtime via openshift quickstarts > - some other link for everyone else (wildfly / developers) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5425) Concurrency/timing issues observed with travis builds

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5425?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5425: --------------------------------------- Added to 12.1 to address 1/2 - the materialization tests routinely fail. > Concurrency/timing issues observed with travis builds > ----------------------------------------------------- > > Key: TEIID-5425 > URL: https://issues.jboss.org/browse/TEIID-5425 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > Several unit tests have been observed to fail during travis builds occasionally: > 1. TestODBCSocketTransport.testRegClass:757 Â» PSQL ResultSet not positioned prope... > 2. TestExternalMatViews.testLazyUpdate:930 expected:<2> but was:<1> (see https://api.travis-ci.org/v3/job/405801976/log.txt) > 3. [ERROR] TestLocalConnections.testWaitForLoadTimeout:475 > 4. From https://api.travis-ci.org/v3/job/415138409/log.txt > [ERROR] testReplication(org.teiid.systemmodel.TestReplication) Time elapsed: 35.21 s <<< FAILURE! > java.lang.AssertionError: expected:<0.9164140964242746> but was:<0.18750528722359294> > at org.teiid.systemmodel.TestReplication.testReplication(TestReplication.java:122) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5425) Concurrency/timing issues observed with travis builds

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5425?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5425: ---------------------------------- Fix Version/s: 12.1 (was: 12.x) > Concurrency/timing issues observed with travis builds > ----------------------------------------------------- > > Key: TEIID-5425 > URL: https://issues.jboss.org/browse/TEIID-5425 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > Several unit tests have been observed to fail during travis builds occasionally: > 1. TestODBCSocketTransport.testRegClass:757 Â» PSQL ResultSet not positioned prope... > 2. TestExternalMatViews.testLazyUpdate:930 expected:<2> but was:<1> (see https://api.travis-ci.org/v3/job/405801976/log.txt) > 3. [ERROR] TestLocalConnections.testWaitForLoadTimeout:475 > 4. From https://api.travis-ci.org/v3/job/415138409/log.txt > [ERROR] testReplication(org.teiid.systemmodel.TestReplication) Time elapsed: 35.21 s <<< FAILURE! > java.lang.AssertionError: expected:<0.9164140964242746> but was:<0.18750528722359294> > at org.teiid.systemmodel.TestReplication.testReplication(TestReplication.java:122) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5550) DISTINCT pushed down incorrectly in some cases

by Johnathon Lee (Jira)

[ https://issues.jboss.org/browse/TEIID-5550?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-5550: --------------------------------- Fix Version/s: 8.12.17.6_4 > DISTINCT pushed down incorrectly in some cases > ---------------------------------------------- > > Key: TEIID-5550 > URL: https://issues.jboss.org/browse/TEIID-5550 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12.15.6_4 > Environment: JDV 6.4.5 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Priority: Major > Fix For: 11.1.2, 12.0, 11.2.1, 8.12.17.6_4 > > > The parent DISTINCT is being removed over joins in particular situations. This is a regression from TEIID-3063 TEIID-3062. > Conditions: > - basic query structure is select distinct col from a join b on a.col2 = b.col2 > - a sort merge join variant must have been planned > - the sort must not be pushed to one of the children > - the projection related conditions of TEIID-3062 / TEIID-3063 must be met > - there is a one to many relationship > The result is that the parent distinct will be inappropriately removed, such that the output of the join can contain repetition of the col value when it should be distinct. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5593) Add a Java 11 travis build

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5593?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5593: --------------------------------------- No, just don't run arquillian with java 11. > Add a Java 11 travis build > -------------------------- > > Key: TEIID-5593 > URL: https://issues.jboss.org/browse/TEIID-5593 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Van Halbert > Priority: Major > Fix For: 12.1 > > > We should also build/test with java 11 on travis. This is expected to work for everything but the arquillian tests. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5593) Add a Java 11 travis build

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5593?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-5593: ------------------------------------ Ok, just wanted to make sure you are ok with travis build failure, as its currently configured. > Add a Java 11 travis build > -------------------------- > > Key: TEIID-5593 > URL: https://issues.jboss.org/browse/TEIID-5593 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Van Halbert > Priority: Major > Fix For: 12.1 > > > We should also build/test with java 11 on travis. This is expected to work for everything but the arquillian tests. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5593) Add a Java 11 travis build

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5593?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5593: --------------------------------------- No, that's just the arquillian tests everything else should run. > Add a Java 11 travis build > -------------------------- > > Key: TEIID-5593 > URL: https://issues.jboss.org/browse/TEIID-5593 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Van Halbert > Priority: Major > Fix For: 12.1 > > > We should also build/test with java 11 on travis. This is expected to work for everything but the arquillian tests. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5593) Add a Java 11 travis build

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5593?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-5593: ------------------------------------ Since you're saying the tests won't work until a later version of Wildfly, so I assume this jira should be delayed until such time. > Add a Java 11 travis build > -------------------------- > > Key: TEIID-5593 > URL: https://issues.jboss.org/browse/TEIID-5593 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Van Halbert > Priority: Major > Fix For: 12.1 > > > We should also build/test with java 11 on travis. This is expected to work for everything but the arquillian tests. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5603) Support of JAVA 11 has failures running arquillian tests

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5603?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5603. ----------------------------------- Resolution: Rejected Until a later wildfly version java 11 is not supported. > Support of JAVA 11 has failures running arquillian tests > -------------------------------------------------------- > > Key: TEIID-5603 > URL: https://issues.jboss.org/browse/TEIID-5603 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 12.x > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Major > > The normal "release install" build works, unfortunately the arquillian tests fail with following test failures: > {code} > [ERROR] Errors: > [ERROR] IntegrationTestOData4.testCORS:235 » NoClassDefFound javax/xml/bind/JAXBExcept... > [ERROR] IntegrationTestOData4.testCompositeKeyTimestamp:179 » NoClassDefFound javax/xm... > [ERROR] IntegrationTestOData4.testGetDataInGzip:294 » NoClassDefFound javax/xml/bind/J... > [ERROR] IntegrationTestOData4.testOdata:87 » NoClassDefFound javax/xml/bind/JAXBExcept... > [ERROR] IntegrationTestOData4.testOdataMetadataError:210 » NoClassDefFound javax/xml/b... > [ERROR] IntegrationTestOData4.testPutDataInGzip:344 » NoClassDefFound javax/xml/bind/J... > [ERROR] IntegrationTestOData4.testStaticServlet:256 » NoClassDefFound javax/xml/bind/J... > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2019