March 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4819) Tree page modifications removing the previous page, don't remove immediately

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4819?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4819. ----------------------------------- Resolution: Done Corrected to always perform the remove and simplified the addMemoryEntry call. > Tree page modifications removing the previous page, don't remove immediately > ---------------------------------------------------------------------------- > > Key: TEIID-4819 > URL: https://issues.jboss.org/browse/TEIID-4819 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.9, 8.7.6.6_2 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.3, 9.1.5, 9.2.2 > > > TEIID-3119 introduced logic to reuse the existing cacheentry, but the removal of the old entry was based upon the wrong remove method - just a remove from cache and not memory. That would delay the cleanup of the memory reference until eviction or when the buffer/tree is removed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4819) Tree page modifications removing the previous page, don't remove immediately

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4819?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4819: ---------------------------------- Affects Version/s: 8.7.6.6_2 8.9 > Tree page modifications removing the previous page, don't remove immediately > ---------------------------------------------------------------------------- > > Key: TEIID-4819 > URL: https://issues.jboss.org/browse/TEIID-4819 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.9, 8.7.6.6_2 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.3, 9.1.5, 9.2.2 > > > TEIID-3119 introduced logic to reuse the existing cacheentry, but the removal of the old entry was based upon the wrong remove method - just a remove from cache and not memory. That would delay the cleanup of the memory reference until eviction or when the buffer/tree is removed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4603) Insert issue when cache contains multiple pojo's with the same key value

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4603?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4603: ------------------------------- Component/s: Documentation > Insert issue when cache contains multiple pojo's with the same key value > ------------------------------------------------------------------------ > > Key: TEIID-4603 > URL: https://issues.jboss.org/browse/TEIID-4603 > Project: Teiid > Issue Type: Bug > Components: Documentation, Misc. Connectors > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Blocker > Fix For: 9.2, 8.12.x-6.4 > > > There is an INSERT issue when there are multiple pojo's stored in the same cache and the keys' overlap (meaning the different types of pojo's have the same key). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4812) Processor is not exiting the join as soon as it's determined one side contains 0 rows

by Marcus Carvalho (JIRA)

[ https://issues.jboss.org/browse/TEIID-4812?page=com.atlassian.jira.plugin... ] Marcus Carvalho commented on TEIID-4812: ---------------------------------------- Ok, I got it. It is clear now. Also, I saw your workaround as a proposed temp solution on the customer case for the released product. Thanks for helping. > Processor is not exiting the join as soon as it's determined one side contains 0 rows > ------------------------------------------------------------------------------------- > > Key: TEIID-4812 > URL: https://issues.jboss.org/browse/TEIID-4812 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.12.8.6_3, 8.7.11.6_2 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 9.3, 9.2.2 > > > There is an issue with the processor during a join, it doesn't exit the join as soon as it's determined that one side of the join returns 0 rows. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4812) Processor is not exiting the join as soon as it's determined one side contains 0 rows

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4812?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4812: --------------------------------------- For released product you would still engage support for one-off or non-production patches. >From the community side you could re-test the scenario using a the community bits or local build. > Processor is not exiting the join as soon as it's determined one side contains 0 rows > ------------------------------------------------------------------------------------- > > Key: TEIID-4812 > URL: https://issues.jboss.org/browse/TEIID-4812 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.12.8.6_3, 8.7.11.6_2 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 9.3, 9.2.2 > > > There is an issue with the processor during a join, it doesn't exit the join as soon as it's determined that one side of the join returns 0 rows. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4815) How could I debug JDV memory allocation properly

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4815?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4815. ----------------------------------- Resolution: Done Marking as done based upon the doc note. https://teiid.gitbooks.io/documents/content/admin/Diagnosing_Issues.html already generally describes memory issues with drivers and that heap analysis should be used when diagnosing out of memory issues. > How could I debug JDV memory allocation properly > ------------------------------------------------ > > Key: TEIID-4815 > URL: https://issues.jboss.org/browse/TEIID-4815 > Project: Teiid > Issue Type: Feature Request > Reporter: Rafael Coutinho > Assignee: Steven Hawkins > Attachments: Screenshot from 2017-03-17 17-54-24.png, Screenshot from 2017-03-17 18-14-50.png > > > We hare having trouble with memory allocation on our JDV server (using Red Hat JBoss Data Virtualization - Version 6.3.0) for some reason memory gets allocated but never released. > For simple queries memory increases just a little, however when we make complex joins etc, we are seeing scenarios with 20GB+ allocated heap. > I wonder if there is any inspection tool for debugging what is consuming it in JDV. > Our main datasource is an Oracle DS, but we do have a MariaDB being used too. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4815) How could I debug JDV memory allocation properly

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4815?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4815: ---------------------------------- Fix Version/s: 9.3 > How could I debug JDV memory allocation properly > ------------------------------------------------ > > Key: TEIID-4815 > URL: https://issues.jboss.org/browse/TEIID-4815 > Project: Teiid > Issue Type: Feature Request > Reporter: Rafael Coutinho > Assignee: Steven Hawkins > Fix For: 9.3 > > Attachments: Screenshot from 2017-03-17 17-54-24.png, Screenshot from 2017-03-17 18-14-50.png > > > We hare having trouble with memory allocation on our JDV server (using Red Hat JBoss Data Virtualization - Version 6.3.0) for some reason memory gets allocated but never released. > For simple queries memory increases just a little, however when we make complex joins etc, we are seeing scenarios with 20GB+ allocated heap. > I wonder if there is any inspection tool for debugging what is consuming it in JDV. > Our main datasource is an Oracle DS, but we do have a MariaDB being used too. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4815) How could I debug JDV memory allocation properly

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4815?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4815: ---------------------------------- Issue Type: Quality Risk (was: Feature Request) > How could I debug JDV memory allocation properly > ------------------------------------------------ > > Key: TEIID-4815 > URL: https://issues.jboss.org/browse/TEIID-4815 > Project: Teiid > Issue Type: Quality Risk > Reporter: Rafael Coutinho > Assignee: Steven Hawkins > Fix For: 9.3 > > Attachments: Screenshot from 2017-03-17 17-54-24.png, Screenshot from 2017-03-17 18-14-50.png > > > We hare having trouble with memory allocation on our JDV server (using Red Hat JBoss Data Virtualization - Version 6.3.0) for some reason memory gets allocated but never released. > For simple queries memory increases just a little, however when we make complex joins etc, we are seeing scenarios with 20GB+ allocated heap. > I wonder if there is any inspection tool for debugging what is consuming it in JDV. > Our main datasource is an Oracle DS, but we do have a MariaDB being used too. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4812) Processor is not exiting the join as soon as it's determined one side contains 0 rows

by Marcus Carvalho (JIRA)

[ https://issues.jboss.org/browse/TEIID-4812?page=com.atlassian.jira.plugin... ] Marcus Carvalho commented on TEIID-4812: ---------------------------------------- Hi Steven, do you know by the chance if there is any one-off patch to suggest to customer to improve the expected date for a solution? Thanks in advance for your time. > Processor is not exiting the join as soon as it's determined one side contains 0 rows > ------------------------------------------------------------------------------------- > > Key: TEIID-4812 > URL: https://issues.jboss.org/browse/TEIID-4812 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.12.8.6_3, 8.7.11.6_2 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 9.3, 9.2.2 > > > There is an issue with the processor during a join, it doesn't exit the join as soon as it's determined that one side of the join returns 0 rows. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4824) Add unique id as a configuration property in the Google Resource adapter

by Debbie Steigner (JIRA)

Debbie Steigner created TEIID-4824: -------------------------------------- Summary: Add unique id as a configuration property in the Google Resource adapter Key: TEIID-4824 URL: https://issues.jboss.org/browse/TEIID-4824 Project: Teiid Issue Type: Enhancement Affects Versions: 8.12.8.6_3 Reporter: Debbie Steigner Assignee: Steven Hawkins Currently, only the google spreadsheet name can be used in the Google Resource adapter instead of the unique id of the document. If there is more than one document with same name in multiple folders the wrong file may be picked up by the resource adapter. Is it possible to use unique document ID instead of spreadsheet name for google data source -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2017