[JBoss JIRA] (TEIIDDES-1118) Add/Remove operations on a VDB should block other operations on the VDB
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1118?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-1118:
---------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 781035|https://bugzilla.redhat.com/show_bug.cgi?id=781035] from MODIFIED to ON_QA
> Add/Remove operations on a VDB should block other operations on the VDB
> -----------------------------------------------------------------------
>
> Key: TEIIDDES-1118
> URL: https://issues.jboss.org/browse/TEIIDDES-1118
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 7.4.2
> Reporter: Marc Shirley
> Assignee: Mark Drilling
> Fix For: 7.7.2, 8.0
>
>
> As adding/removing objects from a VDB results in filesystem operations of adding/removing indexes, this should result in a blocking of additional operations against the VDB. If latency with the filesystem is large enough (for example, on a network filesystem) and no blocking is performed, multiple operations can be performed on the VDB resulting in the below exception:
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.lang.ArrayIndexOutOfBoundsException: 0
> at org.teiid.designer.vdb.VdbModelEntry.synchronizeModelEntry(VdbModelEntry.java:435)
> at org.teiid.designer.vdb.Vdb.addModelEntry(Vdb.java:244)
> at com.metamatrix.modeler.internal.vdb.ui.editor.VdbEditor$25.selected(VdbEditor.java:1709)
> at com.metamatrix.ui.table.TableAndToolBar$2.run(TableAndToolBar.java:79)
> 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:1053)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
> at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
> 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:369)
> 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:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1384)
--
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
12 years, 6 months
[JBoss JIRA] (TEIIDDES-1885) DDL importer problems for both source and view models
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1885?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration updated TEIIDDES-1885:
----------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1016553
> DDL importer problems for both source and view models
> ------------------------------------------------------
>
> Key: TEIIDDES-1885
> URL: https://issues.jboss.org/browse/TEIIDDES-1885
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.2
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 8.3
>
> Attachments: stdcust.ddl
>
>
> When Importing from DDL to create a new view model (DDL File >> Source or View model), the following problems appear:
> a) when choosing auto-select for dialect, the wizard raises the difference panel after hitting Next with generic "Error encountered importing DDL" message and a "No difference report was found" message.
> b) when leaving auto-select unchecked for dialect, clicking Next produces a DDL failed to parse error (as well as a 'No difference report was found" error.
> The DDL in question works in JBDS 6 and earlier.
> Version-Release number of selected component (if applicable):
> JBDS 7 with JBDSIS 7 beta 4
> How reproducible:
> Consistent.
> Steps to Reproduce:
> Import attached DDL via importer.
> see: https://bugzilla.redhat.com/show_bug.cgi?id=1016553
--
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
12 years, 6 months
[JBoss JIRA] (TEIIDDES-1885) DDL importer problems for both source and view models
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1885?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1885:
-----------------------------------
Description:
When Importing from DDL to create a new view model (DDL File >> Source or View model), the following problems appear:
a) when choosing auto-select for dialect, the wizard raises the difference panel after hitting Next with generic "Error encountered importing DDL" message and a "No difference report was found" message.
b) when leaving auto-select unchecked for dialect, clicking Next produces a DDL failed to parse error (as well as a 'No difference report was found" error.
The DDL in question works in JBDS 6 and earlier.
Version-Release number of selected component (if applicable):
JBDS 7 with JBDSIS 7 beta 4
How reproducible:
Consistent.
Steps to Reproduce:
Import attached DDL via importer.
see: https://bugzilla.redhat.com/show_bug.cgi?id=1016553
was:
When Importing from DDL to create a new view model (DDL File >> Source or View model), the following problems appear:
a) when choosing auto-select for dialect, the wizard raises the difference panel after hitting Next with generic "Error encountered importing DDL" message and a "No difference report was found" message.
b) when leaving auto-select unchecked for dialect, clicking Next produces a DDL failed to parse error (as well as a 'No difference report was found" error.
The DDL in question works in JBDS 6 and earlier.
Version-Release number of selected component (if applicable):
JBDS 7 with JBDSIS 7 beta 4
How reproducible:
Consistent.
Steps to Reproduce:
Import attached DDL via importer.
> DDL importer problems for both source and view models
> ------------------------------------------------------
>
> Key: TEIIDDES-1885
> URL: https://issues.jboss.org/browse/TEIIDDES-1885
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.2
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 8.3
>
> Attachments: stdcust.ddl
>
>
> When Importing from DDL to create a new view model (DDL File >> Source or View model), the following problems appear:
> a) when choosing auto-select for dialect, the wizard raises the difference panel after hitting Next with generic "Error encountered importing DDL" message and a "No difference report was found" message.
> b) when leaving auto-select unchecked for dialect, clicking Next produces a DDL failed to parse error (as well as a 'No difference report was found" error.
> The DDL in question works in JBDS 6 and earlier.
> Version-Release number of selected component (if applicable):
> JBDS 7 with JBDSIS 7 beta 4
> How reproducible:
> Consistent.
> Steps to Reproduce:
> Import attached DDL via importer.
> see: https://bugzilla.redhat.com/show_bug.cgi?id=1016553
--
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
12 years, 6 months
[JBoss JIRA] (TEIIDDES-1885) DDL importer problems for both source and view models
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1885?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1885:
-----------------------------------
Attachment: stdcust.ddl
> DDL importer problems for both source and view models
> ------------------------------------------------------
>
> Key: TEIIDDES-1885
> URL: https://issues.jboss.org/browse/TEIIDDES-1885
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.2
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 8.3
>
> Attachments: stdcust.ddl
>
>
> When Importing from DDL to create a new view model (DDL File >> Source or View model), the following problems appear:
> a) when choosing auto-select for dialect, the wizard raises the difference panel after hitting Next with generic "Error encountered importing DDL" message and a "No difference report was found" message.
> b) when leaving auto-select unchecked for dialect, clicking Next produces a DDL failed to parse error (as well as a 'No difference report was found" error.
> The DDL in question works in JBDS 6 and earlier.
> Version-Release number of selected component (if applicable):
> JBDS 7 with JBDSIS 7 beta 4
> How reproducible:
> Consistent.
> Steps to Reproduce:
> Import attached DDL via importer.
--
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
12 years, 6 months
[JBoss JIRA] (TEIIDDES-1885) DDL importer problems for both source and view models
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1885?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1885:
-----------------------------------
Summary: DDL importer problems for both source and view models (was: DDL Importer Issues)
> DDL importer problems for both source and view models
> ------------------------------------------------------
>
> Key: TEIIDDES-1885
> URL: https://issues.jboss.org/browse/TEIIDDES-1885
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.2
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 8.3
>
>
> When Importing from DDL to create a new view model (DDL File >> Source or View model), the following problems appear:
> a) when choosing auto-select for dialect, the wizard raises the difference panel after hitting Next with generic "Error encountered importing DDL" message and a "No difference report was found" message.
> b) when leaving auto-select unchecked for dialect, clicking Next produces a DDL failed to parse error (as well as a 'No difference report was found" error.
> The DDL in question works in JBDS 6 and earlier.
> Version-Release number of selected component (if applicable):
> JBDS 7 with JBDSIS 7 beta 4
> How reproducible:
> Consistent.
> Steps to Reproduce:
> Import attached DDL via importer.
--
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
12 years, 6 months
[JBoss JIRA] (TEIIDDES-1885) DDL Importer Issues
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-1885:
--------------------------------------
Summary: DDL Importer Issues
Key: TEIIDDES-1885
URL: https://issues.jboss.org/browse/TEIIDDES-1885
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 8.2
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 8.3
When Importing from DDL to create a new view model (DDL File >> Source or View model), the following problems appear:
a) when choosing auto-select for dialect, the wizard raises the difference panel after hitting Next with generic "Error encountered importing DDL" message and a "No difference report was found" message.
b) when leaving auto-select unchecked for dialect, clicking Next produces a DDL failed to parse error (as well as a 'No difference report was found" error.
The DDL in question works in JBDS 6 and earlier.
Version-Release number of selected component (if applicable):
JBDS 7 with JBDSIS 7 beta 4
How reproducible:
Consistent.
Steps to Reproduce:
Import attached DDL via importer.
--
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
12 years, 6 months
[JBoss JIRA] (TEIIDDES-1884) Enhanced support for the native query procedure
by Steven Hawkins (JIRA)
Steven Hawkins created TEIIDDES-1884:
----------------------------------------
Summary: Enhanced support for the native query procedure
Key: TEIIDDES-1884
URL: https://issues.jboss.org/browse/TEIIDDES-1884
Project: Teiid Designer
Issue Type: Feature Request
Components: Teiid Integration
Reporter: Steven Hawkins
Teiid translators can expose a procedure to execute arbitrary source queries. When operating with a dynamic vdb the appropriate metadata is automatically made available to the engine, but in Designer the user must manually add a procedure definition. For many users this is a difficult process - see the forum link.
The complications here are that the procedure is selectively enabled and is allowed to have different names based upon the translator properties.
The general procedure form is:
create foreign procedure native (query in string, params in object varidaic) returns table(row_value object)
--
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
12 years, 6 months
[JBoss JIRA] (TEIIDDES-1870) OData Importing issues
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1870?page=com.atlassian.jira.plu... ]
Ramesh Reddy updated TEIIDDES-1870:
-----------------------------------
Assignee: Barry LaFond (was: Ramesh Reddy)
> OData Importing issues
> ----------------------
>
> Key: TEIIDDES-1870
> URL: https://issues.jboss.org/browse/TEIIDDES-1870
> Project: Teiid Designer
> Issue Type: Bug
> Components: Extension Framework, Import/Export
> Affects Versions: 8.2
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Fix For: 8.3
>
>
> After fixing the TEIID-2673, I have failed to import the OData metadata correctly. Upon some investigation here are some issues that needs to be fixed on the Designer
> 1) MED specified for OData properties are incomplete. Please add following properties
> Namespace URI:http://www.jboss.org/teiiddesigner/ext/odata/2012
> Namespace: teiid_odata
> # LinkTables - String/optional
> # HttpMethod - String/optional
> # JoinColumn - String/optional
> # EntityType - String/optional
> # ComplexType - String/optional
> # ColumnGroup - String/optional
> 2) When the "name space" based properties are returned in the DDL from Teiid, none of the properties are correctly being resolved. Bigger issue is they are being ignored, Designer should fail here with error message saying that "extension property match not found" and force users to define or select a MED that matches with all the properties
> 3) Mark the OData not built-in, so that it allows the user to edit the allowed properties list until we have the feature fully worked as expected.
--
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
12 years, 6 months