[JBoss JIRA] (TEIIDDES-1009) Improve Designer "Metadata from Text files on file system" import option
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1009?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration updated TEIIDDES-1009:
----------------------------------------------
Bugzilla Update: Perform
> Improve Designer "Metadata from Text files on file system" import option
> ------------------------------------------------------------------------
>
> Key: TEIIDDES-1009
> URL: https://issues.jboss.org/browse/TEIIDDES-1009
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Import/Export
> Affects Versions: 7.4
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Labels: eds
> Fix For: 8.0
>
>
> Currently, this importer is very limited on the data that can be imported. i.e. on columns you can only import: Name, Datatype, Length and Description. All the Model, Table and Column properties should be available to import. Nullability, Cardinality, Precision, Comments, etc.
> Also, change name to "Metadata from Flat or Text File" to distinguish it from "Metadata from Teiid Metadata File"
--
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, 3 months
[JBoss JIRA] (TEIIDDES-1009) Improve Designer "Metadata from Text files on file system" import option
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1009?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration updated TEIIDDES-1009:
----------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=780722, https://bugzilla.redhat.com/show_bug.cgi?id=780723
> Improve Designer "Metadata from Text files on file system" import option
> ------------------------------------------------------------------------
>
> Key: TEIIDDES-1009
> URL: https://issues.jboss.org/browse/TEIIDDES-1009
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Import/Export
> Affects Versions: 7.4
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Labels: eds
> Fix For: 8.0
>
>
> Currently, this importer is very limited on the data that can be imported. i.e. on columns you can only import: Name, Datatype, Length and Description. All the Model, Table and Column properties should be available to import. Nullability, Cardinality, Precision, Comments, etc.
> Also, change name to "Metadata from Flat or Text File" to distinguish it from "Metadata from Teiid Metadata File"
--
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, 3 months
[JBoss JIRA] (TEIIDDES-1215) Clicking button to expand SQL in transformation editor gets UnhandledEventLoopException
by Paul Nittel (JIRA)
Paul Nittel created TEIIDDES-1215:
-------------------------------------
Summary: Clicking button to expand SQL in transformation editor gets UnhandledEventLoopException
Key: TEIIDDES-1215
URL: https://issues.jboss.org/browse/TEIIDDES-1215
Project: Teiid Designer
Issue Type: Bug
Components: Transformations
Affects Versions: 7.6
Environment: Fedora 16, JBDS 5.0.0 M5, Teiid Designer 7.6
Reporter: Paul Nittel
Fix For: 7.7
Attachments: ExpandSqlException_MPS.zip
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, 3 months
[JBoss JIRA] (TEIIDDES-1232) SWT Thread access error in Transformation Editor.
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-1232:
--------------------------------------
Summary: SWT Thread access error in Transformation Editor.
Key: TEIIDDES-1232
URL: https://issues.jboss.org/browse/TEIIDDES-1232
Project: Teiid Designer
Issue Type: Bug
Components: Editors, Transformations
Affects Versions: 7.6, 7.7
Reporter: Barry LaFond
Processing the results of a new JDBC Import into View model, the following error occurred. Need to wrap updateUpdateTabs() within the SWT thread
org.eclipse.swt.SWTException: Invalid thread access
at org.eclipse.swt.SWT.error(SWT.java:4282)
at org.eclipse.swt.SWT.error(SWT.java:4197)
at org.eclipse.swt.SWT.error(SWT.java:4168)
at org.eclipse.swt.widgets.Widget.error(Widget.java:466)
at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:404)
at org.eclipse.swt.custom.CTabItem.setImage(CTabItem.java:358)
at com.metamatrix.modeler.transformation.ui.editors.TransformationObjectEditorPage.updateUpdateTabs(TransformationObjectEditorPage.java:1138)
at com.metamatrix.modeler.transformation.ui.editors.TransformationObjectEditorPage.setEditorContent(TransformationObjectEditorPage.java:1116)
at com.metamatrix.modeler.transformation.ui.editors.TransformationObjectEditorPage.handleTransformationStatusChangeEvent(TransformationObjectEditorPage.java:1612)
at com.metamatrix.modeler.transformation.ui.editors.TransformationObjectEditorPage.processEvent(TransformationObjectEditorPage.java:2606)
--
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, 3 months
[JBoss JIRA] (TEIIDDES-1229) CLONE - Add support for a comparable binary type
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1229?page=com.atlassian.jira.plu... ]
Steven Hawkins updated TEIIDDES-1229:
-------------------------------------
Assignee: (was: Steven Hawkins)
Forum Reference: http://community.jboss.org/message/630976#630976 (was: http://community.jboss.org/message/630976#630976)
Teiid has now decoupled itself from using the built-in datatype information in the system vdb. Teiid Designer will need to either pull built-in type information from Teiid or it will need to update the built-in datatype xsd(s) to add a varbinary type. See the comments and the associated Teiid issue for more info.
> CLONE - Add support for a comparable binary type
> ------------------------------------------------
>
> Key: TEIIDDES-1229
> URL: https://issues.jboss.org/browse/TEIIDDES-1229
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Teiid Integration
> Reporter: Steven Hawkins
> Fix For: 8.0
>
>
> Teiid currently lacks a binary/varbinary type. Since we have both blob/clob, it would be natural to also introduce a varbinary analog to string. It would be a comparable type and need an escape syntax for entering literals. Translators would need to be modified to account for binary literals.
> See the forum post for current workarounds. We also as a one off have previously allowed clob types to be comparable, see also TEIID-1248. Another approach would by to allow clob/blob to comparable in Teiid, but possibly not at the source as per the searchability metadata. We would still need to support an escape syntax and modify translators to use native type information and the appropriate literal format. The advantage of this latter approach is that there is nothing more that designer must do to support this case. The most practical benefit from introducing a varbinary type would be in having a better size estimate (it would be limited to 8000 bytes) for buffering.
--
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, 3 months
[JBoss JIRA] (TEIIDDES-1229) CLONE - Add support for a comparable binary type
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1229?page=com.atlassian.jira.plu... ]
Steven Hawkins moved TEIID-1913 to TEIIDDES-1229:
-------------------------------------------------
Project: Teiid Designer (was: Teiid)
Key: TEIIDDES-1229 (was: TEIID-1913)
Component/s: Teiid Integration
(was: Query Engine)
Fix Version/s: 8.0
(was: 8.0)
> CLONE - Add support for a comparable binary type
> ------------------------------------------------
>
> Key: TEIIDDES-1229
> URL: https://issues.jboss.org/browse/TEIIDDES-1229
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Teiid Integration
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.0
>
>
> Teiid currently lacks a binary/varbinary type. Since we have both blob/clob, it would be natural to also introduce a varbinary analog to string. It would be a comparable type and need an escape syntax for entering literals. Translators would need to be modified to account for binary literals.
> See the forum post for current workarounds. We also as a one off have previously allowed clob types to be comparable, see also TEIID-1248. Another approach would by to allow clob/blob to comparable in Teiid, but possibly not at the source as per the searchability metadata. We would still need to support an escape syntax and modify translators to use native type information and the appropriate literal format. The advantage of this latter approach is that there is nothing more that designer must do to support this case. The most practical benefit from introducing a varbinary type would be in having a better size estimate (it would be limited to 8000 bytes) for buffering.
--
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, 3 months