April 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2482) Allow the use of the enhanced join for left outer joins

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2482?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2482. ----------------------------------- Resolution: Done Updated the logic to support using the inner side of an outer join as an index for the outer side. The logic for determining when to use an index was also improved so that the other side does not need fully buffered. It is also possible if the left side is fully buffered to reverse the iteration to improve buffer utilization, but that was not yet added. > Allow the use of the enhanced join for left outer joins > ------------------------------------------------------- > > Key: TEIID-2482 > URL: https://issues.jboss.org/browse/TEIID-2482 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4 > > > Left equi outer joins are currently only implemented using the full sort merge join and would benefit from using the enhanced merge when the inner side is relatively small. -- 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
0
0 / 0

[JBoss JIRA] (TEIID-2483) Error bring to connect to Teiid using 8.3 code in Designer against an 8.4 server

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIID-2483?page=com.atlassian.jira.plugin... ] Paul Richardson commented on TEIID-2483: ---------------------------------------- This is the exact place that things go wrong: The request in AdminFactory.getVDBs() is successful and since the server is in domain mode so moves onto to call AdminFactory.getDomainAwareList() It fails on these lines since serverGroups is assigned as 'undefined' {code:java} ModelNode serverGroups = operationResult.get("server-groups"); Set<String> serverGroupNames = serverGroups.keys(); {code} > Error bring to connect to Teiid using 8.3 code in Designer against an 8.4 server > -------------------------------------------------------------------------------- > > Key: TEIID-2483 > URL: https://issues.jboss.org/browse/TEIID-2483 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.4 > Reporter: Van Halbert > Assignee: Ramesh Reddy > > This is the stacktrace I got when testing the connection to Van's new cluster at > redhat-stl-eng3.usersys.redhat.com. > org.teiid.adminapi.AdminProcessingException: TEIID70036 java.lang.IllegalArgumentException > at org.teiid.adminapi.AdminFactory$AdminImpl.getVDBs(AdminFactory.java:1433) > at org.teiid.adminapi.AdminFactory$AdminImpl.getVDBs(AdminFactory.java:1) > at org.teiid83.runtime.ExecutionAdmin.refreshVDBs(ExecutionAdmin.java:658) > at org.teiid83.runtime.ExecutionAdmin.init(ExecutionAdmin.java:575) > at org.teiid83.runtime.ExecutionAdmin.<init>(ExecutionAdmin.java:136) > at org.teiid83.runtime.ExecutionAdminFactory.createExecutionAdmin(ExecutionAdminFactory.java:29) > at > org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getExecutionAdmin(TeiidRuntimeRegistry.java:102) > at org.teiid.designer.runtime.TeiidServer.connect(TeiidServer.java:212) > at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:232) > at org.teiid.designer.runtime.ui.server.RefreshServerAction$1.run(RefreshServerAction.java:58) > <snip> > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) > at org.eclipse.equinox.launcher.Main.run(Main.java:1438) > at org.eclipse.equinox.launcher.Main.main(Main.java:1414) > Caused by: java.lang.IllegalArgumentException > at org.jboss.dmr.ModelValue.getKeys(ModelValue.java:124) > at org.jboss.dmr.ModelNode.keys(ModelNode.java:1194) > at org.teiid.adminapi.AdminFactory$AdminImpl.getDomainAwareList(AdminFactory.java:1349) > at org.teiid.adminapi.AdminFactory$AdminImpl.getVDBs(AdminFactory.java:1430) > ... 48 more -- 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
0
0 / 0

[JBoss JIRA] (TEIID-2483) Error bring to connect to Teiid using 8.3 code in Designer against an 8.4 server

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2483?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2483: --------------------------------------- You can see in the stack that this exception is coming from getDomainAwareList when it's resolving the result. There are two possibilities: Either this is an issue with domain mode - this operation with the same 8.3/8.4 setup should be retried in standalone Or it could be because the 8.4 VDBModelMetadata has changed (metadata status was added to models) - in which case this operation should be retried in domain mode with 8.4/8.4 to see if it's a version compatibility issue. If it's the former we'll need to find a fix on the Teiid side. If it's the latter, then I'm not sure what the options are (again with the working assumption that we've not guaranteed admin compatibility across versions). > Error bring to connect to Teiid using 8.3 code in Designer against an 8.4 server > -------------------------------------------------------------------------------- > > Key: TEIID-2483 > URL: https://issues.jboss.org/browse/TEIID-2483 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.4 > Reporter: Van Halbert > Assignee: Ramesh Reddy > > This is the stacktrace I got when testing the connection to Van's new cluster at > redhat-stl-eng3.usersys.redhat.com. > org.teiid.adminapi.AdminProcessingException: TEIID70036 java.lang.IllegalArgumentException > at org.teiid.adminapi.AdminFactory$AdminImpl.getVDBs(AdminFactory.java:1433) > at org.teiid.adminapi.AdminFactory$AdminImpl.getVDBs(AdminFactory.java:1) > at org.teiid83.runtime.ExecutionAdmin.refreshVDBs(ExecutionAdmin.java:658) > at org.teiid83.runtime.ExecutionAdmin.init(ExecutionAdmin.java:575) > at org.teiid83.runtime.ExecutionAdmin.<init>(ExecutionAdmin.java:136) > at org.teiid83.runtime.ExecutionAdminFactory.createExecutionAdmin(ExecutionAdminFactory.java:29) > at > org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getExecutionAdmin(TeiidRuntimeRegistry.java:102) > at org.teiid.designer.runtime.TeiidServer.connect(TeiidServer.java:212) > at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:232) > at org.teiid.designer.runtime.ui.server.RefreshServerAction$1.run(RefreshServerAction.java:58) > <snip> > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) > at org.eclipse.equinox.launcher.Main.run(Main.java:1438) > at org.eclipse.equinox.launcher.Main.main(Main.java:1414) > Caused by: java.lang.IllegalArgumentException > at org.jboss.dmr.ModelValue.getKeys(ModelValue.java:124) > at org.jboss.dmr.ModelNode.keys(ModelNode.java:1194) > at org.teiid.adminapi.AdminFactory$AdminImpl.getDomainAwareList(AdminFactory.java:1349) > at org.teiid.adminapi.AdminFactory$AdminImpl.getVDBs(AdminFactory.java:1430) > ... 48 more -- 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
0
0 / 0

[JBoss JIRA] (TEIID-2483) Error bring to connect to Teiid using 8.3 code in Designer against an 8.4 server

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIID-2483?page=com.atlassian.jira.plugin... ] Barry LaFond commented on TEIID-2483: ------------------------------------- The getVDBs() admin method below hasn't changed between 8.3 and 8.4, so the exception could be coming from *this.connection.execute(request);* or *Util.isSuccess(outcome)* ? {code} @Override public List<? extends VDB> getVDBs() throws AdminException { final ModelNode request = buildRequest("teiid", "list-vdbs");//$NON-NLS-1$ //$NON-NLS-2$ try { ModelNode outcome = this.connection.execute(request); if (Util.isSuccess(outcome)) { return getDomainAwareList(outcome, VDBMetadataMapper.INSTANCE); } } catch (Exception e) { throw new AdminProcessingException(AdminPlugin.Event.TEIID70036, e); } return Collections.emptyList(); } {code} > Error bring to connect to Teiid using 8.3 code in Designer against an 8.4 server > -------------------------------------------------------------------------------- > > Key: TEIID-2483 > URL: https://issues.jboss.org/browse/TEIID-2483 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.4 > Reporter: Van Halbert > Assignee: Ramesh Reddy > > This is the stacktrace I got when testing the connection to Van's new cluster at > redhat-stl-eng3.usersys.redhat.com. > org.teiid.adminapi.AdminProcessingException: TEIID70036 java.lang.IllegalArgumentException > at org.teiid.adminapi.AdminFactory$AdminImpl.getVDBs(AdminFactory.java:1433) > at org.teiid.adminapi.AdminFactory$AdminImpl.getVDBs(AdminFactory.java:1) > at org.teiid83.runtime.ExecutionAdmin.refreshVDBs(ExecutionAdmin.java:658) > at org.teiid83.runtime.ExecutionAdmin.init(ExecutionAdmin.java:575) > at org.teiid83.runtime.ExecutionAdmin.<init>(ExecutionAdmin.java:136) > at org.teiid83.runtime.ExecutionAdminFactory.createExecutionAdmin(ExecutionAdminFactory.java:29) > at > org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getExecutionAdmin(TeiidRuntimeRegistry.java:102) > at org.teiid.designer.runtime.TeiidServer.connect(TeiidServer.java:212) > at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:232) > at org.teiid.designer.runtime.ui.server.RefreshServerAction$1.run(RefreshServerAction.java:58) > <snip> > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) > at org.eclipse.equinox.launcher.Main.run(Main.java:1438) > at org.eclipse.equinox.launcher.Main.main(Main.java:1414) > Caused by: java.lang.IllegalArgumentException > at org.jboss.dmr.ModelValue.getKeys(ModelValue.java:124) > at org.jboss.dmr.ModelNode.keys(ModelNode.java:1194) > at org.teiid.adminapi.AdminFactory$AdminImpl.getDomainAwareList(AdminFactory.java:1349) > at org.teiid.adminapi.AdminFactory$AdminImpl.getVDBs(AdminFactory.java:1430) > ... 48 more -- 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
0
0 / 0

[JBoss JIRA] (TEIID-2483) Error bring to connect to Teiid using 8.3 code in Designer against an 8.4 server

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2483?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2483: --------------------------------------- I don't believe there is currently an expectation that the admin interface is supposed to be forward/backwards compatible. > Error bring to connect to Teiid using 8.3 code in Designer against an 8.4 server > -------------------------------------------------------------------------------- > > Key: TEIID-2483 > URL: https://issues.jboss.org/browse/TEIID-2483 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.4 > Reporter: Van Halbert > Assignee: Ramesh Reddy > > This is the stacktrace I got when testing the connection to Van's new cluster at > redhat-stl-eng3.usersys.redhat.com. > org.teiid.adminapi.AdminProcessingException: TEIID70036 java.lang.IllegalArgumentException > at org.teiid.adminapi.AdminFactory$AdminImpl.getVDBs(AdminFactory.java:1433) > at org.teiid.adminapi.AdminFactory$AdminImpl.getVDBs(AdminFactory.java:1) > at org.teiid83.runtime.ExecutionAdmin.refreshVDBs(ExecutionAdmin.java:658) > at org.teiid83.runtime.ExecutionAdmin.init(ExecutionAdmin.java:575) > at org.teiid83.runtime.ExecutionAdmin.<init>(ExecutionAdmin.java:136) > at org.teiid83.runtime.ExecutionAdminFactory.createExecutionAdmin(ExecutionAdminFactory.java:29) > at > org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getExecutionAdmin(TeiidRuntimeRegistry.java:102) > at org.teiid.designer.runtime.TeiidServer.connect(TeiidServer.java:212) > at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:232) > at org.teiid.designer.runtime.ui.server.RefreshServerAction$1.run(RefreshServerAction.java:58) > <snip> > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) > at org.eclipse.equinox.launcher.Main.run(Main.java:1438) > at org.eclipse.equinox.launcher.Main.main(Main.java:1414) > Caused by: java.lang.IllegalArgumentException > at org.jboss.dmr.ModelValue.getKeys(ModelValue.java:124) > at org.jboss.dmr.ModelNode.keys(ModelNode.java:1194) > at org.teiid.adminapi.AdminFactory$AdminImpl.getDomainAwareList(AdminFactory.java:1349) > at org.teiid.adminapi.AdminFactory$AdminImpl.getVDBs(AdminFactory.java:1430) > ... 48 more -- 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
0
0 / 0

[JBoss JIRA] (TEIID-2483) Error bring to connect to Teiid using 8.3 code in Designer against an 8.4 server

by Van Halbert (JIRA)

Van Halbert created TEIID-2483: ---------------------------------- Summary: Error bring to connect to Teiid using 8.3 code in Designer against an 8.4 server Key: TEIID-2483 URL: https://issues.jboss.org/browse/TEIID-2483 Project: Teiid Issue Type: Bug Components: AdminApi Affects Versions: 8.4 Reporter: Van Halbert Assignee: Ramesh Reddy This is the stacktrace I got when testing the connection to Van's new cluster at redhat-stl-eng3.usersys.redhat.com. org.teiid.adminapi.AdminProcessingException: TEIID70036 java.lang.IllegalArgumentException at org.teiid.adminapi.AdminFactory$AdminImpl.getVDBs(AdminFactory.java:1433) at org.teiid.adminapi.AdminFactory$AdminImpl.getVDBs(AdminFactory.java:1) at org.teiid83.runtime.ExecutionAdmin.refreshVDBs(ExecutionAdmin.java:658) at org.teiid83.runtime.ExecutionAdmin.init(ExecutionAdmin.java:575) at org.teiid83.runtime.ExecutionAdmin.<init>(ExecutionAdmin.java:136) at org.teiid83.runtime.ExecutionAdminFactory.createExecutionAdmin(ExecutionAdminFactory.java:29) at org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getExecutionAdmin(TeiidRuntimeRegistry.java:102) at org.teiid.designer.runtime.TeiidServer.connect(TeiidServer.java:212) at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:232) at org.teiid.designer.runtime.ui.server.RefreshServerAction$1.run(RefreshServerAction.java:58) <snip> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) at org.eclipse.equinox.launcher.Main.run(Main.java:1438) at org.eclipse.equinox.launcher.Main.main(Main.java:1414) Caused by: java.lang.IllegalArgumentException at org.jboss.dmr.ModelValue.getKeys(ModelValue.java:124) at org.jboss.dmr.ModelNode.keys(ModelNode.java:1194) at org.teiid.adminapi.AdminFactory$AdminImpl.getDomainAwareList(AdminFactory.java:1349) at org.teiid.adminapi.AdminFactory$AdminImpl.getVDBs(AdminFactory.java:1430) ... 48 more -- 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
0
0 / 0

[JBoss JIRA] (TEIID-2482) Allow the use of the enhanced join for left outer joins

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2482: ------------------------------------- Summary: Allow the use of the enhanced join for left outer joins Key: TEIID-2482 URL: https://issues.jboss.org/browse/TEIID-2482 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.4 Left equi outer joins are currently only implemented using the full sort merge join and would benefit from using the enhanced merge when the inner side is relatively small. -- 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
0
0 / 0

[JBoss JIRA] (TEIID-2365) Reduce the usage of output names on the server side

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2365?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2365: ---------------------------------- Fix Version/s: 8.5 (was: 8.4) > Reduce the usage of output names on the server side > --------------------------------------------------- > > Key: TEIID-2365 > URL: https://issues.jboss.org/browse/TEIID-2365 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.5 > > > Parsed objects retain much of the original parse string, which is generally unnecessary on the server side. The use of output names should reduced to unnecessary memory consumption. -- 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
0
0 / 0

[JBoss JIRA] (TEIID-2407) Support temporary table on commit behavior

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2407?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2407: ---------------------------------- Fix Version/s: 8.5 (was: 8.4) > Support temporary table on commit behavior > ------------------------------------------ > > Key: TEIID-2407 > URL: https://issues.jboss.org/browse/TEIID-2407 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.5 > > > Now that our temporary tables are transactionally aware we should support the on commit clause. > Our current default for on commit is effectively "preserve rows", which is contrary to the sql specification. We should also offer delete rows and possible drop (similar to pg sql). -- 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
0
0 / 0

[JBoss JIRA] (TEIID-2365) Reduce the usage of output names on the server side

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2365?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2365: --------------------------------------- One simple possibility would be to use the string pool in the parser token manager override. > Reduce the usage of output names on the server side > --------------------------------------------------- > > Key: TEIID-2365 > URL: https://issues.jboss.org/browse/TEIID-2365 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.4 > > > Parsed objects retain much of the original parse string, which is generally unnecessary on the server side. The use of output names should reduced to unnecessary memory consumption. -- 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
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2013