January 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2368) Dynamic VDB deployment fails when using importer.importIndexes in the case of a index containing a hidden column

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2368?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2368. ----------------------------------- Fix Version/s: 8.3 Resolution: Done Added checks for null/unknown columns and ensured that non-Teiid runtime exceptions have their stacktrace logged as well. > Dynamic VDB deployment fails when using importer.importIndexes in the case of a index containing a hidden column > ---------------------------------------------------------------------------------------------------------------- > > Key: TEIID-2368 > URL: https://issues.jboss.org/browse/TEIID-2368 > Project: Teiid > Issue Type: Feature Request > Affects Versions: 8.2 > Reporter: Jack Ma > Assignee: Steven Hawkins > Fix For: 8.3 > > > We are trying to use dynamic VDB. For better performance, we use <property name="importer.importIndexes" value="true"/> to input the index for an oracle datasource. > > But vdb deployment failed with following error: > [TEIID60011 No column found with name SYS_NC00032$] > > Debugging through teiid code, it looks like that if the index contains the hidden column (like SYS_NC00032), then index loading failed, teiid was trying to call getColumnByName() for those hidden column which does not exist in the column map. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2364) Binding host interface with 0.0.0.0 fails to start JBOSS AS 7.1.1 successfully with Teiid 8.2 in domain mode

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2364?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2364: -------------------------------- Fix Version/s: 8.3 > Binding host interface with 0.0.0.0 fails to start JBOSS AS 7.1.1 successfully with Teiid 8.2 in domain mode > ------------------------------------------------------------------------------------------------------------ > > Key: TEIID-2364 > URL: https://issues.jboss.org/browse/TEIID-2364 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.2 > Environment: Ubuntu 10.04 Linux running on a VirtualCenter VM > Reporter: Jose Chavez > Assignee: Ramesh Reddy > Labels: 0.0.0.0, 8.2, Binding, JBOSS, Ports, Teiid, already, conflict, in, use > Fix For: 8.3 > > > After installing/extracting JBOSS AS 7.1.1 and overlaying Teiid 8.2 final on top, fix a couple of issues in the JBOSS_HOME/bin/scripts/teiid-domain-mode-install.cli, it looks like Teiid 8.3 Beta 1 has fixed these syntax issues. Anyway, once Teiid is down, start JBOSS AS using domain.sh -b=0.0.0.0 -bmanagement=0.0.0.0, this will start JBOSS like a champ, no problems. Now run the teiid-domain-mode-install.cli file, "./jboss-cli.sh --file=scripts/teiid-domain-mode-install.cli" from the JBOSS_HOME/bin directory, if there are no errors with the cli file you will see all the changes succeed, but if you scroll up you will see stack traces indicating "address already in use". You can stop JBOSS and then restart again binding to 0.0.0.0 to get a better view of all the errors as well. Based on my testing and analysis of ports I think the issue is with: > > tcp 0 0 hostname:54200 *:* LISTEN 14115/java > It looks like when JBOSS start successfully by binding to an external address I see these two ports are opened: > > tcp 0 0 hostname:54201 *:* LISTEN 14115/java > tcp 0 0 hostname:54202 *:* > > but when binding to 0.0.0.0 those do not get opened so my hunch is that the problem lies somewhere in this area. Also JDBC and ODBC teiid ports do not get opened in this case where as they do when binding to an external ip. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2369) Query plan for continuous execution should be refreshed after alter command

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2369?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2369: ---------------------------------- Issue Type: Enhancement (was: Bug) Priority: Minor (was: Major) Workaround Description: Restart the query after the alters. Workaround: Workaround Exists Complexity: Medium Component/s: Query Engine Forum Reference: https://community.jboss.org/thread/220761 > Query plan for continuous execution should be refreshed after alter command > --------------------------------------------------------------------------- > > Key: TEIID-2369 > URL: https://issues.jboss.org/browse/TEIID-2369 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 8.1 > Environment: Windows > Reporter: Sanjeev Gour > Assignee: Steven Hawkins > Priority: Minor > > When continuous queries are started on a view and the view is later altered, the change in the view definition is picked up. This is due to the query plan being cached at the time of initial execution. Following discussion contains more information- > https://community.jboss.org/thread/220761 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2369) Query plan for continuous execution should be refreshed after alter command

by Sanjeev Gour (JIRA)

Sanjeev Gour created TEIID-2369: ----------------------------------- Summary: Query plan for continuous execution should be refreshed after alter command Key: TEIID-2369 URL: https://issues.jboss.org/browse/TEIID-2369 Project: Teiid Issue Type: Bug Affects Versions: 8.1 Environment: Windows Reporter: Sanjeev Gour Assignee: Steven Hawkins When continuous queries are started on a view and the view is later altered, the change in the view definition is picked up. This is due to the query plan being cached at the time of initial execution. Following discussion contains more information- https://community.jboss.org/thread/220761 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2364) Binding host interface with 0.0.0.0 fails to start JBOSS AS 7.1.1 successfully with Teiid 8.2 in domain mode

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2364?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2364: ---------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > Binding host interface with 0.0.0.0 fails to start JBOSS AS 7.1.1 successfully with Teiid 8.2 in domain mode > ------------------------------------------------------------------------------------------------------------ > > Key: TEIID-2364 > URL: https://issues.jboss.org/browse/TEIID-2364 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.2 > Environment: Ubuntu 10.04 Linux running on a VirtualCenter VM > Reporter: Jose Chavez > Assignee: Ramesh Reddy > Labels: 0.0.0.0, 8.2, Binding, JBOSS, Ports, Teiid, already, conflict, in, use > > After installing/extracting JBOSS AS 7.1.1 and overlaying Teiid 8.2 final on top, fix a couple of issues in the JBOSS_HOME/bin/scripts/teiid-domain-mode-install.cli, it looks like Teiid 8.3 Beta 1 has fixed these syntax issues. Anyway, once Teiid is down, start JBOSS AS using domain.sh -b=0.0.0.0 -bmanagement=0.0.0.0, this will start JBOSS like a champ, no problems. Now run the teiid-domain-mode-install.cli file, "./jboss-cli.sh --file=scripts/teiid-domain-mode-install.cli" from the JBOSS_HOME/bin directory, if there are no errors with the cli file you will see all the changes succeed, but if you scroll up you will see stack traces indicating "address already in use". You can stop JBOSS and then restart again binding to 0.0.0.0 to get a better view of all the errors as well. Based on my testing and analysis of ports I think the issue is with: > > tcp 0 0 hostname:54200 *:* LISTEN 14115/java > It looks like when JBOSS start successfully by binding to an external address I see these two ports are opened: > > tcp 0 0 hostname:54201 *:* LISTEN 14115/java > tcp 0 0 hostname:54202 *:* > > but when binding to 0.0.0.0 those do not get opened so my hunch is that the problem lies somewhere in this area. Also JDBC and ODBC teiid ports do not get opened in this case where as they do when binding to an external ip. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2368) Dynamic VDB deployment fails when using importer.importIndexes in the case of a index containing a hidden column

by SBS JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2368?page=com.atlassian.jira.plugin... ] SBS JIRA Integration updated TEIID-2368: ---------------------------------------- Forum Reference: https://community.jboss.org/message/795305#795305 > Dynamic VDB deployment fails when using importer.importIndexes in the case of a index containing a hidden column > ---------------------------------------------------------------------------------------------------------------- > > Key: TEIID-2368 > URL: https://issues.jboss.org/browse/TEIID-2368 > Project: Teiid > Issue Type: Feature Request > Affects Versions: 8.2 > Reporter: Jack Ma > Assignee: Steven Hawkins > > We are trying to use dynamic VDB. For better performance, we use <property name="importer.importIndexes" value="true"/> to input the index for an oracle datasource. > > But vdb deployment failed with following error: > [TEIID60011 No column found with name SYS_NC00032$] > > Debugging through teiid code, it looks like that if the index contains the hidden column (like SYS_NC00032), then index loading failed, teiid was trying to call getColumnByName() for those hidden column which does not exist in the column map. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2368) Dynamic VDB deployment fails when using importer.importIndexes in the case of a index containing a hidden column

by Jack Ma (JIRA)

Jack Ma created TEIID-2368: ------------------------------ Summary: Dynamic VDB deployment fails when using importer.importIndexes in the case of a index containing a hidden column Key: TEIID-2368 URL: https://issues.jboss.org/browse/TEIID-2368 Project: Teiid Issue Type: Feature Request Affects Versions: 8.2 Reporter: Jack Ma Assignee: Steven Hawkins We are trying to use dynamic VDB. For better performance, we use <property name="importer.importIndexes" value="true"/> to input the index for an oracle datasource. But vdb deployment failed with following error: [TEIID60011 No column found with name SYS_NC00032$] Debugging through teiid code, it looks like that if the index contains the hidden column (like SYS_NC00032), then index loading failed, teiid was trying to call getColumnByName() for those hidden column which does not exist in the column map. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-196) Support creation of temp tables on physical sources.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-196?page=com.atlassian.jira.plugin.... ] Steven Hawkins reassigned TEIID-196: ------------------------------------ Assignee: Steven Hawkins > Support creation of temp tables on physical sources. > ---------------------------------------------------- > > Key: TEIID-196 > URL: https://issues.jboss.org/browse/TEIID-196 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Query Engine > Affects Versions: 6.0.0 > Reporter: Ken Johnson > Assignee: Steven Hawkins > Fix For: 8.3 > > > This is a multi-part request. > First, the system should support creation of temporary tables using a physical backing store rather than buffer manger. Given multi-pass SQL's heavy use of temp tables, buffer manager can easily be overloaded with large interim results stored in temp tables. > Second, this should be a user-configurable behavior. For example, user might be able to choose a system-level or session-level default from among: > -- memory/cache > -- a source represented by a connector binding > -- a distinct temp source defined with it's own connection parameters (possibly another schema in the repository DB instance) > Ideally default selectoin should be override-able at temp table creation time through a DDL extension > In the case where multiple temp tables have been created on a source via connector, the query planner should recognize this and leverage pushdown to the temp store when later query passes access multiple temp tables. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-196) Support creation of temp tables on physical sources.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-196?page=com.atlassian.jira.plugin.... ] Work on TEIID-196 started by Steven Hawkins. > Support creation of temp tables on physical sources. > ---------------------------------------------------- > > Key: TEIID-196 > URL: https://issues.jboss.org/browse/TEIID-196 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Query Engine > Affects Versions: 6.0.0 > Reporter: Ken Johnson > Assignee: Steven Hawkins > Fix For: 8.3 > > > This is a multi-part request. > First, the system should support creation of temporary tables using a physical backing store rather than buffer manger. Given multi-pass SQL's heavy use of temp tables, buffer manager can easily be overloaded with large interim results stored in temp tables. > Second, this should be a user-configurable behavior. For example, user might be able to choose a system-level or session-level default from among: > -- memory/cache > -- a source represented by a connector binding > -- a distinct temp source defined with it's own connection parameters (possibly another schema in the repository DB instance) > Ideally default selectoin should be override-able at temp table creation time through a DDL extension > In the case where multiple temp tables have been created on a source via connector, the query planner should recognize this and leverage pushdown to the temp store when later query passes access multiple temp tables. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2367) sql server / sybase dependent parameter defaults too high

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2367?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2367. ----------------------------------- Resolution: Done Set the defaults max predicates/max in size for sql server to 2/1000 and sybase to 8/250 > sql server / sybase dependent parameter defaults too high > --------------------------------------------------------- > > Key: TEIID-2367 > URL: https://issues.jboss.org/browse/TEIID-2367 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector > Affects Versions: 7.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.3 > > > Our defaults for sybase/sql server are too high. Sybase is typically limited to 2048 entries (although it looks like the latest adaptive server may be 32k). While sql server should be 2100. -- 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, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2013