August 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2639) Internally generated and user submitted anonymous blocks can't access temp tables from the surrounding scope

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2639?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2639: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1000623|https://bugzilla.redhat.com/show_bug.cgi?id=1000623] from NEW to ASSIGNED > Internally generated and user submitted anonymous blocks can't access temp tables from the surrounding scope > ------------------------------------------------------------------------------------------------------------ > > Key: TEIID-2639 > URL: https://issues.jboss.org/browse/TEIID-2639 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.5 > > > While the blocks are resolved against the surrounding scope, when executed the procedure plan shields them from seeing the higher level scopes just as when a real procedure is executed. This results in temporary table 'temp' not found exceptions, for example with a non-simple view v and the delete: > delete from v where e2 = (select max(e2) from temp as z where e3 = z.e3) -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2639) Internally generated and user submitted anonymous blocks can't access temp tables from the surrounding scope

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2639?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2639: --------------------------------------- I'm referring to internally generated anon procedure blocks for update processing not normal procedures. > Internally generated and user submitted anonymous blocks can't access temp tables from the surrounding scope > ------------------------------------------------------------------------------------------------------------ > > Key: TEIID-2639 > URL: https://issues.jboss.org/browse/TEIID-2639 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.5 > > > While the blocks are resolved against the surrounding scope, when executed the procedure plan shields them from seeing the higher level scopes just as when a real procedure is executed. This results in temporary table 'temp' not found exceptions, for example with a non-simple view v and the delete: > delete from v where e2 = (select max(e2) from temp as z where e3 = z.e3) -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2639) Internally generated and user submitted anonymous blocks can't access temp tables from the surrounding scope

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2639?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2639: ------------------------------------- Shouldn't higher level scoped temp tables visible in nested levels in named procedures? > Internally generated and user submitted anonymous blocks can't access temp tables from the surrounding scope > ------------------------------------------------------------------------------------------------------------ > > Key: TEIID-2639 > URL: https://issues.jboss.org/browse/TEIID-2639 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.5 > > > While the blocks are resolved against the surrounding scope, when executed the procedure plan shields them from seeing the higher level scopes just as when a real procedure is executed. This results in temporary table 'temp' not found exceptions, for example with a non-simple view v and the delete: > delete from v where e2 = (select max(e2) from temp as z where e3 = z.e3) -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2639) Internally generated and user submitted anonymous blocks can't access temp tables from the surrounding scope

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2639: ------------------------------------- Summary: Internally generated and user submitted anonymous blocks can't access temp tables from the surrounding scope Key: TEIID-2639 URL: https://issues.jboss.org/browse/TEIID-2639 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.5 While the blocks are resolved against the surrounding scope, when executed the procedure plan shields them from seeing the higher level scopes just as when a real procedure is executed. This results in temporary table 'temp' not found exceptions, for example with a non-simple view v and the delete: delete from v where e2 = (select max(e2) from temp as z where e3 = z.e3) -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2638) CLI Scripts are incorrectly referencing the cache within the cache container, should reference cache container

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2638?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2638. --------------------------------- Resolution: Done Never mind what I said, sorry about confusion. Looks like, based on the "base" result name I was deriving the replication name as we need both. Original commit is fine. Corrected now. > CLI Scripts are incorrectly referencing the cache within the cache container, should reference cache container > -------------------------------------------------------------------------------------------------------------- > > Key: TEIID-2638 > URL: https://issues.jboss.org/browse/TEIID-2638 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 8.4, 8.4.1 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Fix For: 8.4.1, 8.5 > > > The domain and standalone cli scripts need to have the following lines corrected: > /profile=ha/subsystem=teiid:add(async-thread-pool=teiid-async, distributed-cache-jgroups-stack=udp, resultset-cache-infinispan-container=resultset-repl, preparedplan-cache-infinispan-container=preparedplan, policy-decider-module=org.jboss.teiid) > /subsystem=teiid:add(async-thread-pool=teiid-async, resultset-cache-infinispan-container=resultset, preparedplan-cache-infinispan-container=preparedplan, policy-decider-module=org.jboss.teiid) > so that the cache containers map to teiid-cache, and not the cache within the container. This isn't seen in the standalone-teiid.xml, cause those settings to do point to the "teiid" cache container. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2638) CLI Scripts are incorrectly referencing the cache within the cache container, should reference cache container

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2638?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-2638: ---------------------------------- Assignee: Ramesh Reddy (was: Van Halbert) > CLI Scripts are incorrectly referencing the cache within the cache container, should reference cache container > -------------------------------------------------------------------------------------------------------------- > > Key: TEIID-2638 > URL: https://issues.jboss.org/browse/TEIID-2638 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 8.4, 8.4.1 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Fix For: 8.4.1, 8.5 > > > The domain and standalone cli scripts need to have the following lines corrected: > /profile=ha/subsystem=teiid:add(async-thread-pool=teiid-async, distributed-cache-jgroups-stack=udp, resultset-cache-infinispan-container=resultset-repl, preparedplan-cache-infinispan-container=preparedplan, policy-decider-module=org.jboss.teiid) > /subsystem=teiid:add(async-thread-pool=teiid-async, resultset-cache-infinispan-container=resultset, preparedplan-cache-infinispan-container=preparedplan, policy-decider-module=org.jboss.teiid) > so that the cache containers map to teiid-cache, and not the cache within the container. This isn't seen in the standalone-teiid.xml, cause those settings to do point to the "teiid" cache container. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2638) CLI Scripts are incorrectly referencing the cache within the cache container, should reference cache container

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2638?page=com.atlassian.jira.plugin... ] Van Halbert edited comment on TEIID-2638 at 8/22/13 5:23 PM: ------------------------------------------------------------- Also, there was a new name=value (resultset-cache-name=teiid-cache) added to the following: /profile=ha/subsystem=teiid:add(async-thread-pool=teiid-async, distributed-cache-jgroups-stack=udp, resultset-cache-infinispan-container=teiid-cache, resultset-cache-name=teiid-cache, preparedplan-cache-infinispan-container=teiid-cache, policy-decider-module=org.jboss.teiid) And I don't see this in standalone script, are they suppose to be different? was (Author: van.halbert): Also, there was a new name=value (resultset-cache-name=teiid-cache) added to the following: /profile=ha/subsystem=teiid:add(async-thread-pool=teiid-async, distributed-cache-jgroups-stack=udp, resultset-cache-infinispan-container=resultset-repl, preparedplan-cache-infinispan-container=preparedplan, policy-decider-module=org.jboss.teiid) And I don't see this in standalone script, are they suppose to be different? > CLI Scripts are incorrectly referencing the cache within the cache container, should reference cache container > -------------------------------------------------------------------------------------------------------------- > > Key: TEIID-2638 > URL: https://issues.jboss.org/browse/TEIID-2638 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 8.4, 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.4.1, 8.5 > > > The domain and standalone cli scripts need to have the following lines corrected: > /profile=ha/subsystem=teiid:add(async-thread-pool=teiid-async, distributed-cache-jgroups-stack=udp, resultset-cache-infinispan-container=resultset-repl, preparedplan-cache-infinispan-container=preparedplan, policy-decider-module=org.jboss.teiid) > /subsystem=teiid:add(async-thread-pool=teiid-async, resultset-cache-infinispan-container=resultset, preparedplan-cache-infinispan-container=preparedplan, policy-decider-module=org.jboss.teiid) > so that the cache containers map to teiid-cache, and not the cache within the container. This isn't seen in the standalone-teiid.xml, cause those settings to do point to the "teiid" cache container. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2638) CLI Scripts are incorrectly referencing the cache within the cache container, should reference cache container

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2638?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2638: ------------------------------------ Also, there was a new name=value (resultset-cache-name=teiid-cache) added to the following: /profile=ha/subsystem=teiid:add(async-thread-pool=teiid-async, distributed-cache-jgroups-stack=udp, resultset-cache-infinispan-container=resultset-repl, preparedplan-cache-infinispan-container=preparedplan, policy-decider-module=org.jboss.teiid) And I don't see this in standalone script, are they suppose to be different? > CLI Scripts are incorrectly referencing the cache within the cache container, should reference cache container > -------------------------------------------------------------------------------------------------------------- > > Key: TEIID-2638 > URL: https://issues.jboss.org/browse/TEIID-2638 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 8.4, 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.4.1, 8.5 > > > The domain and standalone cli scripts need to have the following lines corrected: > /profile=ha/subsystem=teiid:add(async-thread-pool=teiid-async, distributed-cache-jgroups-stack=udp, resultset-cache-infinispan-container=resultset-repl, preparedplan-cache-infinispan-container=preparedplan, policy-decider-module=org.jboss.teiid) > /subsystem=teiid:add(async-thread-pool=teiid-async, resultset-cache-infinispan-container=resultset, preparedplan-cache-infinispan-container=preparedplan, policy-decider-module=org.jboss.teiid) > so that the cache containers map to teiid-cache, and not the cache within the container. This isn't seen in the standalone-teiid.xml, cause those settings to do point to the "teiid" cache container. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2638) CLI Scripts are incorrectly referencing the cache within the cache container, should reference cache container

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2638?page=com.atlassian.jira.plugin... ] Van Halbert reopened TEIID-2638: -------------------------------- > CLI Scripts are incorrectly referencing the cache within the cache container, should reference cache container > -------------------------------------------------------------------------------------------------------------- > > Key: TEIID-2638 > URL: https://issues.jboss.org/browse/TEIID-2638 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 8.4, 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.4.1, 8.5 > > > The domain and standalone cli scripts need to have the following lines corrected: > /profile=ha/subsystem=teiid:add(async-thread-pool=teiid-async, distributed-cache-jgroups-stack=udp, resultset-cache-infinispan-container=resultset-repl, preparedplan-cache-infinispan-container=preparedplan, policy-decider-module=org.jboss.teiid) > /subsystem=teiid:add(async-thread-pool=teiid-async, resultset-cache-infinispan-container=resultset, preparedplan-cache-infinispan-container=preparedplan, policy-decider-module=org.jboss.teiid) > so that the cache containers map to teiid-cache, and not the cache within the container. This isn't seen in the standalone-teiid.xml, cause those settings to do point to the "teiid" cache container. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2638) CLI Scripts are incorrectly referencing the cache within the cache container, should reference cache container

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2638?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2638: ------------------------------------ Tried with latest domain cli script committed to 8.4.x, and it still fails with: [Server:server-one] JBAS014775: New missing/unsatisfied dependencies: [Server:server-one] service jboss.infinispan.teiid-cache.resultset-repl-repl (missing) dependents: [service jboss.teiid.cache.resultset] [Server:server-one] > CLI Scripts are incorrectly referencing the cache within the cache container, should reference cache container > -------------------------------------------------------------------------------------------------------------- > > Key: TEIID-2638 > URL: https://issues.jboss.org/browse/TEIID-2638 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 8.4, 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.4.1, 8.5 > > > The domain and standalone cli scripts need to have the following lines corrected: > /profile=ha/subsystem=teiid:add(async-thread-pool=teiid-async, distributed-cache-jgroups-stack=udp, resultset-cache-infinispan-container=resultset-repl, preparedplan-cache-infinispan-container=preparedplan, policy-decider-module=org.jboss.teiid) > /subsystem=teiid:add(async-thread-pool=teiid-async, resultset-cache-infinispan-container=resultset, preparedplan-cache-infinispan-container=preparedplan, policy-decider-module=org.jboss.teiid) > so that the cache containers map to teiid-cache, and not the cache within the container. This isn't seen in the standalone-teiid.xml, cause those settings to do point to the "teiid" cache container. -- 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, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2013