November 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Commented: (TEIID-1355) adminshell.bat cannot read script from stdin

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/browse/TEIID-1355?page=com.atlassian.jira.plugin.s... ] Ramesh Reddy commented on TEIID-1355: ------------------------------------- I am not sure what you us do here, escaping is OS dependent. Executing the single statement is the behaviour of the Groovy shell. If you want you can add your script to a file then execute adminshell.bat load file.groovy > adminshell.bat cannot read script from stdin > -------------------------------------------- > > Key: TEIID-1355 > URL: https://jira.jboss.org/browse/TEIID-1355 > Project: Teiid > Issue Type: Bug > Components: Tools > Affects Versions: 7.1 > Environment: windows > Reporter: Aleksandar Kostadinov > > On windows adminshell doesn't read script if supplied on stdin. It looks like it is reading from terminal (unlike adminshell on linux). I see that one can supply expression as first argument to adminshell but it seems to accept only a single expression and additionally complex expressions are a hell to escape properly. > Assuming adminshell is intended to be used for automating administrative tasks, it needs a straightforward way to execute scripts non-interactively so current behavior on windows needs to be fixed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-1355) adminshell.bat cannot read script from stdin

by Aleksandar Kostadinov (JIRA)

[ https://jira.jboss.org/browse/TEIID-1355?page=com.atlassian.jira.plugin.s... ] Aleksandar Kostadinov moved SOA-2569 to TEIID-1355: --------------------------------------------------- Project: Teiid (was: JBoss Enterprise SOA Platform) Key: TEIID-1355 (was: SOA-2569) Affects Version/s: 7.1 (was: 5.1.0.ER4) Security: (was: Public) Component/s: Tools (was: EDS) > adminshell.bat cannot read script from stdin > -------------------------------------------- > > Key: TEIID-1355 > URL: https://jira.jboss.org/browse/TEIID-1355 > Project: Teiid > Issue Type: Bug > Components: Tools > Affects Versions: 7.1 > Environment: windows > Reporter: Aleksandar Kostadinov > > On windows adminshell doesn't read script if supplied on stdin. It looks like it is reading from terminal (unlike adminshell on linux). I see that one can supply expression as first argument to adminshell but it seems to accept only a single expression and additionally complex expressions are a hell to escape properly. > Assuming adminshell is intended to be used for automating administrative tasks, it needs a straightforward way to execute scripts non-interactively so current behavior on windows needs to be fixed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-1000) Dependent Join in Virtual Model not pushing criteria to both sources

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-1000?page=com.atlassian.jira.plugin.s... ] Steven Hawkins resolved TEIID-1000. ----------------------------------- Fix Version/s: (was: 8.0) Resolution: Won't Fix upon reexamining this issue it's not clear to me what the customer expectation was. Since this is using a NOT IN, in general a dependent join based upon the subquery is not an option. A more specific case could be that for a non-correlated NOT IN we use stats to guess at the set size and if sufficiently small we perform the subquery, then if it actually is smaller than the max in of the dependent side, then perform a dependent join. Another possibility is that if this is not an optional join scenario, then it would not be possible to push the subquery criteria to the source (if it is an optional join scenario an earlier change now allows subqueries to be pushed through views). Another is that like criteria and the costing stats to should trigger a dependent join. Without having the stats it's impossible it's hard to know if we are making the right decision. Given the age of the issue and the narrow applicability of the first scenario I'm inclined to mark as not fixed. > Dependent Join in Virtual Model not pushing criteria to both sources > -------------------------------------------------------------------- > > Key: TEIID-1000 > URL: https://jira.jboss.org/browse/TEIID-1000 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > > Sample models are attached. User query is: > SELECT * FROM v_TV_SHOWS.v_SHOWS_ACTORS2 > WHERE SHOW_NAME LIKE '%E%' AND > NOT ACTOR_SHOW_ID IN (SELECT ACTOR_SHOW_ID FROM v_TV_SHOWS.v_SHOWS_ACTORS2 WHERE ACTOR_NAME = 'MALCOLM JAMAL-WARNER') > OPTION DEBUG and MMProcess.log are attached. > Customer complaint is that the query contains criteria on ACTOR_NAME and ACTOR_SHOW_ID which is coming from Oracle and on SHOW_NAME which is coming from SQL Server. In the query plan, there is a SELECT node that does not have criteria to Oracle. Instead it is SELECT * which pulls all records. Customer tables are huge so this is an issue for them. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-89) Data roles should account for the ability to create temp tables

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-89?page=com.atlassian.jira.plugin.sys... ] Steven Hawkins commented on TEIID-89: ------------------------------------- Reserving a name though is a breaking change. > Data roles should account for the ability to create temp tables > --------------------------------------------------------------- > > Key: TEIID-89 > URL: https://jira.jboss.org/browse/TEIID-89 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Optional > Fix For: 7.3 > > > Defect Tracker #24698: Data roles should account for creating temp tables. Right now all temp table creation is allowed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-89) Data roles should account for the ability to create temp tables

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/browse/TEIID-89?page=com.atlassian.jira.plugin.sys... ] Ramesh Reddy commented on TEIID-89: ----------------------------------- "." seems confusing, I think internal name is un-ambiguous. > Data roles should account for the ability to create temp tables > --------------------------------------------------------------- > > Key: TEIID-89 > URL: https://jira.jboss.org/browse/TEIID-89 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Optional > Fix For: 7.3 > > > Defect Tracker #24698: Data roles should account for creating temp tables. Right now all temp table creation is allowed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-89) Data roles should account for the ability to create temp tables

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-89?page=com.atlassian.jira.plugin.sys... ] Steven Hawkins commented on TEIID-89: ------------------------------------- I propose that the ability to create/drop session (and eventually globally scoped) temp tables will use '.' as the resource name. Alternatively we could reserve the internal name for the temp space "__TEMP__". Create would be represented by the create permission on "." and drop would be the delete permission on ".". There would will also need to be a system property to set the default for temp table access. VDBs created prior to this change will likely need to have default create/delete permissions for temp tables. > Data roles should account for the ability to create temp tables > --------------------------------------------------------------- > > Key: TEIID-89 > URL: https://jira.jboss.org/browse/TEIID-89 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Optional > Fix For: 7.3 > > > Defect Tracker #24698: Data roles should account for creating temp tables. Right now all temp table creation is allowed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-89) Data roles should account for the ability to create temp tables

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-89?page=com.atlassian.jira.plugin.sys... ] Steven Hawkins updated TEIID-89: -------------------------------- Affects Version/s: 6.0.0 (was: 8.x) Complexity: Low Affects: [Documentation (Ref Guide, User Guide, etc.), Release Notes] > Data roles should account for the ability to create temp tables > --------------------------------------------------------------- > > Key: TEIID-89 > URL: https://jira.jboss.org/browse/TEIID-89 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Optional > Fix For: 7.3 > > > Defect Tracker #24698: Data roles should account for creating temp tables. Right now all temp table creation is allowed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-1353) Intermittent, recurring problem with EDS adminshell - seeing NPE - with [org.jboss.resource.connectionmanager.NoTxConnectionManager] exception maybe 20% of the time

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/browse/TEIID-1353?page=com.atlassian.jira.plugin.s... ] Ramesh Reddy commented on TEIID-1353: ------------------------------------- By the way, if look at the log, it shows the shutdown sequence, so I doubt it is happening 20% of time as claimed in JIRA description. If you dispute, please re-open with re-producible use case. > Intermittent, recurring problem with EDS adminshell - seeing NPE - with [org.jboss.resource.connectionmanager.NoTxConnectionManager] exception maybe 20% of the time > -------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-1353 > URL: https://jira.jboss.org/browse/TEIID-1353 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.1.1 > Reporter: Len DiMaggio > Priority: Minor > > Seeing this about one time in 5 performing a query and then disconnecting a JDBC and admin connection. Will attacher server.log and pointer to test code. > Logging this as a minor issue as there does not seem to be any functional impact, but the server.log message may concern users. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-1353) Intermittent, recurring problem with EDS adminshell - seeing NPE - with [org.jboss.resource.connectionmanager.NoTxConnectionManager] exception maybe 20% of the time

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/browse/TEIID-1353?page=com.atlassian.jira.plugin.s... ] Ramesh Reddy resolved TEIID-1353. --------------------------------- Resolution: Rejected Looks like this *only* occurs during the shutdown sequence. The data source connection manager pool is stopped and a event is not yet notified to the Managed Connection, so Teiid sends closedConnection event to the pool, but it has no way to cleanup properly as "stopService" is already called on it. This is avoided by fixing the JBoss AS connector to code check if the shutdown process is in progress by adding a null check. At any rate this is not a Teiid bug. Please open JIRA with JBoss AS. > Intermittent, recurring problem with EDS adminshell - seeing NPE - with [org.jboss.resource.connectionmanager.NoTxConnectionManager] exception maybe 20% of the time > -------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-1353 > URL: https://jira.jboss.org/browse/TEIID-1353 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.1.1 > Reporter: Len DiMaggio > Priority: Minor > > Seeing this about one time in 5 performing a query and then disconnecting a JDBC and admin connection. Will attacher server.log and pointer to test code. > Logging this as a minor issue as there does not seem to be any functional impact, but the server.log message may concern users. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-1353) Intermittent, recurring problem with EDS adminshell - seeing NPE - with [org.jboss.resource.connectionmanager.NoTxConnectionManager] exception maybe 20% of the time

by Van Halbert (JIRA)

[ https://jira.jboss.org/browse/TEIID-1353?page=com.atlassian.jira.plugin.s... ] Van Halbert moved SOA-2560 to TEIID-1353: ----------------------------------------- Project: Teiid (was: JBoss Enterprise SOA Platform) Key: TEIID-1353 (was: SOA-2560) Affects Version/s: 7.1.1 (was: 5.1.0.ER3) Security: (was: Public) Component/s: Server (was: EDS) > Intermittent, recurring problem with EDS adminshell - seeing NPE - with [org.jboss.resource.connectionmanager.NoTxConnectionManager] exception maybe 20% of the time > -------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-1353 > URL: https://jira.jboss.org/browse/TEIID-1353 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.1.1 > Reporter: Len DiMaggio > Priority: Minor > > Seeing this about one time in 5 performing a query and then disconnecting a JDBC and admin connection. Will attacher server.log and pointer to test code. > Logging this as a minor issue as there does not seem to be any functional impact, but the server.log message may concern users. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2010