February 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1605) Unable to call a function that is defined within a package in oracle

by Van Halbert (JIRA)

Unable to call a function that is defined within a package in oracle -------------------------------------------------------------------- Key: TEIID-1605 URL: https://issues.jboss.org/browse/TEIID-1605 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 7.1.1 Reporter: Van Halbert Assignee: Steven Hawkins Unable to call a function that is defined within a package in oracle. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1635) Error resolving a procedure invocation w/o a resultset in a procedure

by Steven Hawkins (JIRA)

Error resolving a procedure invocation w/o a resultset in a procedure --------------------------------------------------------------------- Key: TEIID-1635 URL: https://issues.jboss.org/browse/TEIID-1635 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.4 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.4.1 If a procedure that has return/out parameters without a resultset is invoked in a procedure it will fail to resolve unless parameter is assigned. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
3
0 / 0

[JBoss JIRA] (TEIID-1813) EDS performance tests shows a performance degradation against SOA-P 5.1.0.GA in case of selecting from XML datasource

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1813?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1813. --------------------------------- > EDS performance tests shows a performance degradation against SOA-P 5.1.0.GA in case of selecting from XML datasource > ---------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-1813 > URL: https://issues.jboss.org/browse/TEIID-1813 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 7.4.1 > Reporter: Pavel Macik > Assignee: Steven Hawkins > Fix For: 7.6 > > Attachments: perf.vdb > > > The eds_xmlfile_select scenario shows ~30% performance degradation in select queries from XML datasource. > See the "(EDS) Files select - Charts" sheet of the document at [1] for details. > [1] https://docspace.corp.redhat.com/docs/DOC-56368 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-1917) Teiid VDB Previous Version not accessible

by Gautam Banerjee (JIRA)

Gautam Banerjee created TEIID-1917: -------------------------------------- Summary: Teiid VDB Previous Version not accessible Key: TEIID-1917 URL: https://issues.jboss.org/browse/TEIID-1917 Project: Teiid Issue Type: Bug Components: AdminApi Affects Versions: 7.6 Reporter: Gautam Banerjee Assignee: Steven Hawkins There can be multiple VDBs of different versions deployed and we can connect to a specific version (documentation says that). But if we connect to a version 1 vdb, then deploy a version 2 vdb of same name, then once the version 2 vdb starts deploying we are not able to connect to version 1 vdb and a meaage comes VDB "Name" version "1" does not exist. Am I missing something? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
15
0 / 0

[JBoss JIRA] (TEIID-1907) SQLStringVisitor should create call visitNode on Select

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1907?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1907. --------------------------------- > SQLStringVisitor should create call visitNode on Select > ------------------------------------------------------- > > Key: TEIID-1907 > URL: https://issues.jboss.org/browse/TEIID-1907 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.5 > Environment: Fedora 16, JBDS 5.0.0 M5, Teiid Designer 7.6 > Reporter: Paul Nittel > Assignee: Steven Hawkins > Fix For: 7.7, 8.0 > > > Here's what I get: > eclipse.buildId=unknown > java.version=1.6.0_22 > java.vendor=Sun Microsystems Inc. > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.jbds.product.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.jbds.product.product > Error > Wed Jan 18 16:35:12 CST 2012 > Unhandled event loop exception > java.lang.NullPointerException > at com.metamatrix.query.internal.ui.sqleditor.component.QueryDisplayComponent.expandSelect(QueryDisplayComponent.java:586) > at com.metamatrix.modeler.transformation.ui.editors.sqleditor.SqlEditorPanel.expandCurrentSelect(SqlEditorPanel.java:1872) > at com.metamatrix.modeler.transformation.ui.editors.sqleditor.SqlEditorPanelWrapper.expandCurrentSelect(SqlEditorPanelWrapper.java:161) > at com.metamatrix.modeler.transformation.ui.editors.sqleditor.actions.ExpandSelect.doRun(ExpandSelect.java:48) > at com.metamatrix.ui.actions.AbstractAction$1.run(AbstractAction.java:537) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at com.metamatrix.ui.actions.AbstractAction.run(AbstractAction.java:540) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) > at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:452) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209) > at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) > at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) > at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) > at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) > at org.eclipse.equinox.launcher.Main.run(Main.java:1410) > at org.eclipse.equinox.launcher.Main.main(Main.java:1386) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-1833) Add documentation for the delegating translator

by Steven Hawkins (Created) (JIRA)

Add documentation for the delegating translator ----------------------------------------------- Key: TEIID-1833 URL: https://issues.jboss.org/browse/TEIID-1833 Project: Teiid Issue Type: Quality Risk Components: Documentation Affects Versions: 7.4 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 7.6 The delegating translator framework is not well documented. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
2
0 / 0

[JBoss JIRA] (TEIID-964) Must pushdown functions in select clause

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-964?page=com.atlassian.jira.plugin.... ] Steven Hawkins closed TEIID-964. -------------------------------- > Must pushdown functions in select clause > ---------------------------------------- > > Key: TEIID-964 > URL: https://issues.jboss.org/browse/TEIID-964 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 7.6 > > > (F_ATM_REPORT_TYPE is a DB function) > SELECT F_ATM_REPORT_TYPE (BUS_LINE_CODE) FROM ... > Will not have the function pushed down if it only appears in the select clause. The planner must check if a function is pushdown only when it appears in the select clause and determine a source to push it to. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-987) Problem regarding how often availability is called on the Facet

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-987?page=com.atlassian.jira.plugin.... ] Steven Hawkins closed TEIID-987. -------------------------------- > Problem regarding how often availability is called on the Facet > --------------------------------------------------------------- > > Key: TEIID-987 > URL: https://issues.jboss.org/browse/TEIID-987 > Project: Teiid > Issue Type: Bug > Components: Jopr Plugin > Affects Versions: 7.0 > Reporter: Van Halbert > Assignee: Ted Jones > Fix For: 8.0 > > > There's a problem where the Facet (resource) availability is being checked about 5 times consecutively for every resource. There is an embedded jopr issue regarding this issue (EMBJOPR-129) > However, until this can be fixed, we might have to add a system property to handle how often to allow availability to be checked to limit the calls. Otherwise, this could a large processing overhead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-1805) Allow no_unnest to apply to views/subquery from clauses

by Steven Hawkins (Created) (JIRA)

Allow no_unnest to apply to views/subquery from clauses ------------------------------------------------------- Key: TEIID-1805 URL: https://issues.jboss.org/browse/TEIID-1805 Project: Teiid Issue Type: Enhancement Components: Query Engine Affects Versions: 7.6 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.6 The no_unnest hint should also control view flattening behavior to prevent the optimizer from removing a view. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
2
0 / 0

[JBoss JIRA] (TEIID-1949) AssertionError with Teiid order by over pushed group by

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-1949: ------------------------------------- Summary: AssertionError with Teiid order by over pushed group by Key: TEIID-1949 URL: https://issues.jboss.org/browse/TEIID-1949 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.6 Reporter: Steven Hawkins Assignee: Steven Hawkins With a user query similar to: SELECT DB.Address, DB.City, count(*) as Count FROM "Emp"."persons" as DB GROUP BY DB.Address, DB.City ORDER BY DB.City If the grouping is pushed, but the order by is not an AssertionError will occur: java.lang.AssertionError: Assertion failed. at org.teiid.core.util.Assertion.failed(Assertion.java:73) at org.teiid.core.util.Assertion.assertTrue(Assertion.java:68) at org.teiid.core.util.Assertion.assertTrue(Assertion.java:60) at org.teiid.query.processor.relational.SortUtility.<init>(SortUtility.java:145) It does not occur if neither or both are pushed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2012