April 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2295) Quick start to demonstrate how to use Native Query capability

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2295?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2295: ------------------------------------ The dynamicvdb-datafederation quick start will be updated to demonstrate the native query support. > Quick start to demonstrate how to use Native Query capability > ------------------------------------------------------------- > > Key: TEIID-2295 > URL: https://issues.jboss.org/browse/TEIID-2295 > Project: Teiid > Issue Type: Feature Request > Components: Build/Kits > Reporter: Van Halbert > Assignee: Van Halbert > > Create a quick start that demonstrates using the Native Query support. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2295) Quick start to demonstrate how to use Native Query capability

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2295?page=com.atlassian.jira.plugin... ] Work on TEIID-2295 started by Van Halbert. > Quick start to demonstrate how to use Native Query capability > ------------------------------------------------------------- > > Key: TEIID-2295 > URL: https://issues.jboss.org/browse/TEIID-2295 > Project: Teiid > Issue Type: Feature Request > Components: Build/Kits > Reporter: Van Halbert > Assignee: Van Halbert > > Create a quick start that demonstrates using the Native Query support. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2478) incomplete with pushdown

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2478?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2478: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=958211 > incomplete with pushdown > ------------------------ > > Key: TEIID-2478 > URL: https://issues.jboss.org/browse/TEIID-2478 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4 > > > If all the with clauses are not fully pushed, but is still pushable, the resulting query plan will contain incomplete references to the clauses. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2483) Error trying 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: --------------------------------------- Van/Barry, this should only effect domain mode. You should continue whatever testing you need in standalone for the time being. I don't have an ETA, but this will be addressed in 8.4. > Error trying 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 > Fix For: 8.4 > > > 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2483) Error trying 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: ------------------------------------- Note the getVDBs() method call is used by designer to manage the contents of Teiid's VDB folder in the server view and to verify a VDB is deployed in order to allow and continue with Execute VDB action. If this bug isn't fixed, Designer 8.2 really can't update to Teiid 8.4 code-base > Error trying 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 > Fix For: 8.4 > > > 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2289) Create quickstart to demonstrate using Hive/Hadoop

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2289?page=com.atlassian.jira.plugin... ] Work on TEIID-2289 stopped by Van Halbert. > Create quickstart to demonstrate using Hive/Hadoop > -------------------------------------------------- > > Key: TEIID-2289 > URL: https://issues.jboss.org/browse/TEIID-2289 > Project: Teiid > Issue Type: Feature Request > Components: Build/Kits > Reporter: Van Halbert > Assignee: Van Halbert > > Create a quick start that can demonstrate using Hive/Hadoop. This will contain instructions for setting up Hadoop. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2456) Create quick start to demonstrate using persisted costing information from a repository

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2456?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2456: ------------------------------------ Here's the quick start overview of what will be performed: - Use default H2 database and setup JNDI reference - run DDL to create the table to persist stats: - extend the default MetadataRepository logic, so that the stats will be pulled from the H2 database, above. - deploy a vdb that fronts the H2 database - use the Hibernate quick start as an example of providing CRUD access to H2 database This would demonstrate the how the Metadata Repository can be extended to persist the stats, and provide the Teiid runtime engine access to up-to-date stats. The demo would allow the person to enter the stats, run a sql test and see the cardinality was being used, by viewing the QueryPlan. The next step on this would be to add a mechanism for reading the stats from a datasource and updating the stats table. And then providing a scheduler to update the stats on an ongoing basis. > Create quick start to demonstrate using persisted costing information from a repository > --------------------------------------------------------------------------------------- > > Key: TEIID-2456 > URL: https://issues.jboss.org/browse/TEIID-2456 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Reporter: Van Halbert > Assignee: Van Halbert > > Create a quick start that will demonstrate Teiid obtaining costing information at runtime from a repository. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2456) Create quick start to demonstrate using persisted costing information from a repository

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2456?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2456: ------------------------------------ After reading TEIID-245, not sure how much this quick start will be useful depending on the impact of this jira. > Create quick start to demonstrate using persisted costing information from a repository > --------------------------------------------------------------------------------------- > > Key: TEIID-2456 > URL: https://issues.jboss.org/browse/TEIID-2456 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Reporter: Van Halbert > Assignee: Van Halbert > > Create a quick start that will demonstrate Teiid obtaining costing information at runtime from a repository. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2363) proactive buffering not occurring for the inner side of an outer join on "MERGE JOIN (SORT/ALREADY_SORTED)"

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2363?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2363. ----------------------------------- Fix Version/s: 8.4 (was: 8.3) Resolution: Done Partially resolved for 8.3 (only in the case of right side sorts). Adding the missing prefetch to fully resolved in 8.4. > proactive buffering not occurring for the inner side of an outer join on "MERGE JOIN (SORT/ALREADY_SORTED)" > ----------------------------------------------------------------------------------------------------------- > > Key: TEIID-2363 > URL: https://issues.jboss.org/browse/TEIID-2363 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 7.7.2 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 7.7.6, 8.4 > > > The issue here is this is an outer join and the inner side (the already sorted side) will be buffered regardless. Current logic does not catch blocked exceptions from one side and pro-actively buffer the other - rather we are serially performing the sort and then continue with the loading of the inner side > For inner joins there is a clear trade-off between execution speed and buffering so this behavior may have to be hint or config driven for non-dependent non-outer joins. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2363) proactive buffering not occurring for the inner side of an outer join on "MERGE JOIN (SORT/ALREADY_SORTED)"

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2363?page=com.atlassian.jira.plugin... ] Steven Hawkins reopened TEIID-2363: ----------------------------------- Reopening. The original fix actually addressed the x/SORT - not x/ALREADY_SORTED. With TEIID-2482 this case should largely be rendered moot as the enhanced merge join logic will be consulted first. > proactive buffering not occurring for the inner side of an outer join on "MERGE JOIN (SORT/ALREADY_SORTED)" > ----------------------------------------------------------------------------------------------------------- > > Key: TEIID-2363 > URL: https://issues.jboss.org/browse/TEIID-2363 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 7.7.2 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 8.3, 7.7.6 > > > The issue here is this is an outer join and the inner side (the already sorted side) will be buffered regardless. Current logic does not catch blocked exceptions from one side and pro-actively buffer the other - rather we are serially performing the sort and then continue with the loading of the inner side > For inner joins there is a clear trade-off between execution speed and buffering so this behavior may have to be hint or config driven for non-dependent non-outer joins. -- 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

10 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2013