April 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2840) More control over TTL Snapshot Refresh

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2840?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2840. --------------------------------- > More control over TTL Snapshot Refresh > --------------------------------------- > > Key: TEIID-2840 > URL: https://issues.jboss.org/browse/TEIID-2840 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 7.7.8 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 8.7 > > > The ttl load to may need to be changed to a blocking load or some configuration options provided to prevent stale reads after a certain time limit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2701) Don't proactively close source executions under a transaction scope higher than request

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2701?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2701. --------------------------------- > Don't proactively close source executions under a transaction scope higher than request > --------------------------------------------------------------------------------------- > > Key: TEIID-2701 > URL: https://issues.jboss.org/browse/TEIID-2701 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 7.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.6, 7.7.9 > > > Under a transaction we are always closing source executions that are typically held open for lobs. While this is basically required in the request scope (as close is too late for a commit - the client would not receive a failure notification), it should not be needed in the other transaction scopes. > For lobs that are not readable after close currently will be seen as unreabable values from Teiid. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2856) IP address incorrectly exposed via SECURITY logger

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2856?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2856. --------------------------------- > IP address incorrectly exposed via SECURITY logger > -------------------------------------------------- > > Key: TEIID-2856 > URL: https://issues.jboss.org/browse/TEIID-2856 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.5 > Environment: RHEL6 linux 2.6.32-431.1.2.el6.x86_64 #1 SMP Sun Nov 24 09:37:37 EST 2013 x86_64 x86_64 x86_64 GNU/Linux > jbossas-standalone 7.2.1 6.Final_redhat_10.1.ep6.el6 > Reporter: Marco Grigull > Assignee: Steven Hawkins > Fix For: 8.7 > > > After configuring a logger for org.teiid.SECURITY debug level, fields for IP address information appears to be supplied by the client and not observed from the connection itself (odbc connections). It is reported as null for psql based connections. > This had previously been reported as TEIID-1586 and TEIID-1672 . IT still presents an issue where audit trail is required. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2707) proactive buffering on an enhanced sort merge left outer join results in an assertionerror

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2707?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2707. --------------------------------- > proactive buffering on an enhanced sort merge left outer join results in an assertionerror > ------------------------------------------------------------------------------------------ > > Key: TEIID-2707 > URL: https://issues.jboss.org/browse/TEIID-2707 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.6, 7.7.9 > > > The proactive buffering logic with particular blocking patterns is not correct. Namely the setting of the buffer to forward only prevents re-reading which results in an AssertionError. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2836) Retreived records less than actual when data is stored in EBCDIC

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2836?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2836. --------------------------------- > Retreived records less than actual when data is stored in EBCDIC > ---------------------------------------------------------------- > > Key: TEIID-2836 > URL: https://issues.jboss.org/browse/TEIID-2836 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > > One of views in my vdb joins a table in DB2 on z/OS which has EBCDIC data with other table in Oracle which has SJIS data. It returns records less than actual. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2733) TEIID-2633 goes too far

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2733?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2733. --------------------------------- > TEIID-2633 goes too far > ----------------------- > > Key: TEIID-2733 > URL: https://issues.jboss.org/browse/TEIID-2733 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 8.4.1, 8.5, 7.7.8 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.6 > > > TEIID-2633 can have a negative performance impact if discovered transitive criteria is removed that could help filter more rows from a multi-column dependent join. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2683) Proactive eviction of new batches reduces forward-only performance

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2683?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2683. --------------------------------- > Proactive eviction of new batches reduces forward-only performance > ------------------------------------------------------------------ > > Key: TEIID-2683 > URL: https://issues.jboss.org/browse/TEIID-2683 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.6 > > > With TEIID-2429 to improve performance under heavy buffer load the cleaner was made more proactive in evicting new batches. In streaming scenarios this results in a lot of unnecessary buffering as the batches are likely to be held only for a short time. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2747) Wrong results with merge join SORT_DISTINCT with a full sort that is distinct beyond the join columns

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2747?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2747. --------------------------------- > Wrong results with merge join SORT_DISTINCT with a full sort that is distinct beyond the join columns > ----------------------------------------------------------------------------------------------------- > > Key: TEIID-2747 > URL: https://issues.jboss.org/browse/TEIID-2747 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 8.4.1, 8.6 > > > To speed up processing of a sort merge join we attempt to eliminate extra comparisons by detecting if the equi-join column values are distinct. In plans where the sorted values are distinct beyond the equi-join values such that the equi-join column values are non-distinct, then incorrect results can be returned. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2889) MongoDB translator fails to deploy

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2889?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2889. --------------------------------- > MongoDB translator fails to deploy > ---------------------------------- > > Key: TEIID-2889 > URL: https://issues.jboss.org/browse/TEIID-2889 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 8.7 > Reporter: Tom Arnold > Assignee: Ramesh Reddy > Labels: 8.7, Beta2, mongodb > Fix For: 8.7 > > > I am building Teiid from GIT master. I noticed that the MongoDB translator failed to deploy. Upon further investigation I found that the module.xml was looking for a different version of the MongoDB Java driver than what was packaged. > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <module xmlns="urn:jboss:module:1.0" name="org.jboss.teiid.translator.mongodb.api"> > <resources> > <resource-root path="mongodb-api-8.7.0.Beta2-SNAPSHOT.jar" /> > <resource-root path="mongo-java-driver-2.11.1.jar" /> > </resources> > <dependencies> > <module name="javax.api"/> > <module name="javax.resource.api"/> > <module name="org.jboss.teiid.common-core" /> > <module name="org.jboss.teiid.api" /> > </dependencies> > </module> > {code} > > {code} > mongo-java-driver-2.7.3.jar > {code} > {code} > git clean -fdx > git reset --hard > mvn clean install -P release -s settings.xml -DskipTests > {code} > Building just the translator, I see that 2.11.1 and 2.7.3 get pulled down. I've been doing greps and cannot find what is pulling in the older version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2626) If a column type is not set, null values will be written into persisted batches

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2626?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2626. --------------------------------- > If a column type is not set, null values will be written into persisted batches > ------------------------------------------------------------------------------- > > Key: TEIID-2626 > URL: https://issues.jboss.org/browse/TEIID-2626 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.5 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 8.4.1, 8.5, 7.7.9 > > > The buffer manager will choose the null serializer if a column type is not set. This is not expected to happen, but test code can be sloppy which isn't evident if the weak reference cache is working effectively. > However there is one place in the code that is effected, which is the internally generated partitionId column on any window function expression with a non-empty over clause. This means that on systems with limited memory and or poor performing weak references no results for the window function may be returned. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2014