December 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2556) Dependent join pushdown with array type incorrect

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2556?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2556. --------------------------------- > Dependent join pushdown with array type incorrect > ------------------------------------------------- > > Key: TEIID-2556 > URL: https://issues.jboss.org/browse/TEIID-2556 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.1 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > When pushing a dependent join with source array type support, the resulting comparison uses a single parameter with a value index of -1. It should instead use an array of parameters with the correct indexes. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2129) Reduce the number of datasource listeners

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2129?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2129. --------------------------------- > Reduce the number of datasource listeners > ----------------------------------------- > > Key: TEIID-2129 > URL: https://issues.jboss.org/browse/TEIID-2129 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Affects Versions: 8.1 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > As a follow on to TEIID-2121 it would be good to have a single listener per vdb rather than for each source used by the vdb. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2706) Cache hint for resultset cache in user query doesn't work

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2706?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2706. --------------------------------- > Cache hint for resultset cache in user query doesn't work > --------------------------------------------------------- > > Key: TEIID-2706 > URL: https://issues.jboss.org/browse/TEIID-2706 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7.7 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > I enabled TRACE logging and Command Logging to see if the Resultset Cache was being used on my queries. If I use the ResultSetCacheMode=true on connection string you can see Teiid using the cache instead of pulling from source again: > This is displayed the first time the query is run, it's loading the Cache: > 2013-10-18 07:17:52,951 TRACE [org.teiid.PROCESSOR] Adding to global/distributed cache Cache Entry<tR+M2n5wIwzI=bqt2@teiid-security> params:null sql:select * from SmallA > This displays the subsequent times the same query is run and you will not see source queries: > 2013-10-18 07:19:21,115 TRACE [org.teiid.PROCESSOR] Cache hit for Cache Entry<tR+M2n5wIwzI=bqt2@teiid-security> params:null sql:select * from SmallA > But if I remove the connection string and just try using the Cache Hint /*+ cache*/ you see nothing in the logs in regards to the Cache loading or being used on the second query, you still see Teiid pulling the results from the source. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2588) create temp table with not null column toString not correct

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2588?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2588. --------------------------------- > create temp table with not null column toString not correct > ----------------------------------------------------------- > > Key: TEIID-2588 > URL: https://issues.jboss.org/browse/TEIID-2588 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > There is no space between the column type and the not null constraint. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2566) standalone-teiid.xml and the CLI scripts point to different caches in the teiid subsystem

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2566?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2566. --------------------------------- > standalone-teiid.xml and the CLI scripts point to different caches in the teiid subsystem > ----------------------------------------------------------------------------------------- > > Key: TEIID-2566 > URL: https://issues.jboss.org/browse/TEIID-2566 > Project: Teiid > Issue Type: Quality Risk > Components: Build/Kits > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Minor > Fix For: 8.4.1, 8.5 > > > In the standalone-teiid.xml configuration, teiid subsystem: > <resultset-cache infinispan-container="teiid" name="resultset"/> > <preparedplan-cache infinispan-container="teiid" name="preparedplan"/> > In the CLI script, it contains the following: > /subsystem=teiid:add(async-thread-pool=teiid-async, resultset-cache-infinispan-container=teiid-cache, preparedplan-cache-infinispan-container=teiid-cache, policy-decider-module=org.jboss.teiid) > and looks like the following when loaded: > <resultset-cache infinispan-container="teiid-cache"/> > <preparedplan-cache infinispan-container="teiid-cache"/> > -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2744) Windows 2008 ODBC Driver works but throwing exceptions on Teiid Server

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2744?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2744. --------------------------------- > Windows 2008 ODBC Driver works but throwing exceptions on Teiid Server > ---------------------------------------------------------------------- > > Key: TEIID-2744 > URL: https://issues.jboss.org/browse/TEIID-2744 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 8.4.1 > Environment: Windows 2008 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Blocker > > When running ODBC driver on windows, the querying works but weird WARNinig is showed in the server console. > The warning message: > 03:31:58,965 WARN [org.teiid.PROCESSOR] (Worker1_QueryProcessorQueue5) TEIID30020 Processing exception for request xS0DtHsdmG7n.9 'TEIID31100 Parsing error: Encountered "('\"customer\"' AS [*]regclass[*])" at line 1, column 106. > Was expecting: "string" | "varbinary" | "varchar" | "boolean" | "byte" | "tinyint" | "short" | "smallint" | "char" | "integer" ...'. Originally QueryParserException QueryParser.java:215. Enable more detailed logging to see the entire stacktrace. > See BZ for more details. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2592) Parsing error

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2592?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2592. --------------------------------- > Parsing error > ------------- > > Key: TEIID-2592 > URL: https://issues.jboss.org/browse/TEIID-2592 > Project: Teiid > Issue Type: Bug > Environment: psql (8.4.13, server 8.1.4) > Reporter: Simon Green > Assignee: Steven Hawkins > > Using EngVDBR, I tried the following query, and received an error > EngVDBR=> SELECT name FROM Bugzilla.products WHERE classification_id = 5 AND id NOT IN (SELECT product_id FROM Bugzilla.milestones WHERE value != '---');ERROR: Parsing error: Encountered "SELECT product_id FROM Bugzilla.milestones WHERE value" at line 1, column 79. > However, the following query worked as expected: > SELECT name FROM Bugzilla.products WHERE classification_id = 5 AND id NOT IN (SELECT product_id FROM Bugzilla.milestones WHERE milestones.value != '---'); > The first query is valid, and thus I think it is a bug in 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2573) Default source sql for varbinary in JDBC is incorrect

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2573?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2573. --------------------------------- > Default source sql for varbinary in JDBC is incorrect > ----------------------------------------------------- > > Key: TEIID-2573 > URL: https://issues.jboss.org/browse/TEIID-2573 > Project: Teiid > Issue Type: Bug > Components: Connector API > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > The SQLConversionVisitor does not properly handle varbinary literals and instead treats them as string literals. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2512) Allow chaining of Metadata Repositories with multiple <metadata> elements in vdb.xml

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2512?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2512. --------------------------------- > Allow chaining of Metadata Repositories with multiple <metadata> elements in vdb.xml > ------------------------------------------------------------------------------------ > > Key: TEIID-2512 > URL: https://issues.jboss.org/browse/TEIID-2512 > Project: Teiid > Issue Type: Enhancement > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > Currently when chaining the multiple Metadata Repositories in VDB.xml they are defined using a comma separated list on <metadata> element. Any "context" specific value is submitted via "TEXT" element under <metadata>. > However with above only one TEXT value can be defined, and if multiple repositories need to use the TEXT value there is no way to distinguish who is the owner of the data. > A Enhancement is required to be able to define multiple <metadata> elements in the vdb.xml to chain the repositories instead using the comma separated list. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2641) improve transaction handling in procedures

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2641?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2641. --------------------------------- > improve transaction handling in procedures > ------------------------------------------ > > Key: TEIID-2641 > URL: https://issues.jboss.org/browse/TEIID-2641 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.2 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.4.1, 8.5 > > > Atomic blocks do not have well-defined handling w.r.t. variable assignments and the implicit return cursor. In both cases the affects are currently non-atomic - the last assignment/cursor is effective even. > Also exception handling in an atomic block must result in an exception being thrown to guarantee the entire block atomicity. -- 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

11 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2013