[JBoss JIRA] (TEIIDDES-2112) Need to correct the generated MySQL DDL for Primary Keys
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2112?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2112:
--------------------------------------
Assignee: Barry LaFond
> Need to correct the generated MySQL DDL for Primary Keys
> --------------------------------------------------------
>
> Key: TEIIDDES-2112
> URL: https://issues.jboss.org/browse/TEIIDDES-2112
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.4
> Reporter: Mark Drilling
> Assignee: Barry LaFond
>
> The generated DDL for MySQL primary keys needs to be adjusted to account for the case where the user names their PK to PRIMARY.
> We currently generate DDL of the following form for MySQL
> ALTER TABLE <tableName>
> ADD CONSTRAINT <pkName>
> PRIMARY KEY (<colName>);
> For a key named PRIMARY this results in DDL that fails on MySQL. We should change the form for MySQL to be
> ALTER TABLE <tableName> ADD PRIMARY KEY (<colName>);
> On MySQL the PK is forced to be named PRIMARY, so its not possible to set the name anyway.
--
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, 1 month
[JBoss JIRA] (TEIIDDES-2112) Need to correct the generated MySQL DDL for Primary Keys
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2112?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2112:
-----------------------------------
Fix Version/s: 8.5
> Need to correct the generated MySQL DDL for Primary Keys
> --------------------------------------------------------
>
> Key: TEIIDDES-2112
> URL: https://issues.jboss.org/browse/TEIIDDES-2112
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.4
> Reporter: Mark Drilling
> Assignee: Barry LaFond
> Fix For: 8.5
>
>
> The generated DDL for MySQL primary keys needs to be adjusted to account for the case where the user names their PK to PRIMARY.
> We currently generate DDL of the following form for MySQL
> ALTER TABLE <tableName>
> ADD CONSTRAINT <pkName>
> PRIMARY KEY (<colName>);
> For a key named PRIMARY this results in DDL that fails on MySQL. We should change the form for MySQL to be
> ALTER TABLE <tableName> ADD PRIMARY KEY (<colName>);
> On MySQL the PK is forced to be named PRIMARY, so its not possible to set the name anyway.
--
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, 1 month
[JBoss JIRA] (TEIIDDES-2128) Error generating SQL for Flat File Procedure
by lightsail pro (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2128?page=com.atlassian.jira.plu... ]
lightsail pro commented on TEIIDDES-2128:
-----------------------------------------
Here is the stack trace for the flat file remote url error on teiid 8.7 and designer 8.5.0.Alpha1-v20140423-1406-B2577 on windows 7 64 bit, JBDS 7.1.1, Java 1.6.0_37 x64:
Got "x" sign on the data source view at the end of the wizard, preview button is greyed out automatically, then "x" disappear. There is exception in the server log. Here is the exception stack trace:
===========================================
eclipse.buildId=unknown
java.version=1.6.0_37
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments: -product com.jboss.jbds.product.product
Command-line arguments: -os win32 -ws win32 -arch x86_64 -product com.jboss.jbds.product.product
Error
Wed Apr 23 13:02:23 EDT 2014
java.lang.NullPointerException
at org.teiid.designer.runtime.DqpPlugin.handleNewModelEvent(DqpPlugin.java:274)
at org.teiid.designer.runtime.DqpPlugin$1.notifyAdd(DqpPlugin.java:227)
at org.teiid.designer.core.workspace.ModelWorkspaceManager.fire(ModelWorkspaceManager.java:631)
at org.teiid.designer.core.workspace.DeltaProcessor.fireNotification(DeltaProcessor.java:140)
at org.teiid.designer.core.workspace.DeltaProcessor.resourceChanged(DeltaProcessor.java:70)
at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285)
at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149)
at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:396)
at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1531)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2354)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)
at org.teiid.designer.transformation.ui.wizards.file.TeiidMetadataImportProcessor.execute(TeiidMetadataImportProcessor.java:97)
at org.teiid.designer.transformation.ui.wizards.file.TeiidMetadataImportWizard$1.run(TeiidMetadataImportWizard.java:179)
at org.teiid.designer.ui.common.util.UiUtil.runInSwtThread(UiUtil.java:492)
at org.teiid.designer.transformation.ui.wizards.file.TeiidMetadataImportWizard.finish(TeiidMetadataImportWizard.java:176)
at org.teiid.designer.ui.common.wizard.AbstractWizard.performFinish(AbstractWizard.java:356)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1057)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4170)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:826)
at org.eclipse.jface.window.Window.open(Window.java:802)
at org.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:152)
at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:279)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420)
at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
at org.eclipse.ui.internal.actions.CommandAction.run(CommandAction.java:171)
at org.eclipse.ui.actions.ImportResourcesAction.run(ImportResourcesAction.java:97)
at org.eclipse.ui.actions.BaseSelectionListenerAction.runWithEvent(BaseSelectionListenerAction.java:168)
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$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1057)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4170)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:140)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:611)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
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:354)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
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:636)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> Error generating SQL for Flat File Procedure
> --------------------------------------------
>
> Key: TEIIDDES-2128
> URL: https://issues.jboss.org/browse/TEIIDDES-2128
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Transformations
> Affects Versions: 8.5
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 8.5
>
>
> Follow Flat File import example and generated SQL only contains the following:
> <Missing message for key "ProcedureService.procedureServiceTextInvokeHttpTableSqlTemplate" in: org.teiid.runtime.client.messages>
> Debugging found: java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key ProcedureService.procedureServiceTextInvokeHttpTableSqlTemplate
--
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, 1 month
[JBoss JIRA] (TEIIDDES-2028) Teiid tooling fails to create metamodel for web service
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2028?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2028:
-----------------------------------
Fix Version/s: 8.6
(was: 8.5)
> Teiid tooling fails to create metamodel for web service
> -------------------------------------------------------
>
> Key: TEIIDDES-2028
> URL: https://issues.jboss.org/browse/TEIIDDES-2028
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.3
> Reporter: Van Halbert
> Assignee: Ted Jones
> Fix For: 8.6
>
>
> Description of problem:
> Unable to build metamodel for customer provided WSDL file. Simplified the web service to a single operation that uses three embedded schemas under wsdl types. Stack trace from NPE appears in console log and errors occur after wizard is executed. Screenshots for wizard, wsdl file, and stack trace are attached.
> I'm able to validate the WSDL and I can generate a web service from the WSDL within a dynamic web project using the web service wizard.
> Version-Release number of selected component (if applicable):
> JBDS 7.1, latest Teiid tooling from https://devstudio.jboss.com/updates/7.0-development/integration-stack/, DV 6.0.0.CR2
> How reproducible:
> Everytime
> Steps to Reproduce:
> 1. Create Teiid Model Project
> 2. Import WSDL under schemas folder
> 3. Use Teiid Metamodel wizard to consume WSDL
> see BZ for attachments.
--
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, 1 month
[JBoss JIRA] (TEIIDDES-1884) Enhanced support for the native query procedure
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1884?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1884:
-----------------------------------
Fix Version/s: 8.6
(was: 8.5)
> 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
> Fix For: 8.6
>
>
> 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
10 years, 1 month
[JBoss JIRA] (TEIIDDES-1657) Update and publish E2E Yahoo UDF Test Script as wiki document
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1657?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1657:
-----------------------------------
Fix Version/s: 8.6
(was: 8.5)
> Update and publish E2E Yahoo UDF Test Script as wiki document
> -------------------------------------------------------------
>
> Key: TEIIDDES-1657
> URL: https://issues.jboss.org/browse/TEIIDDES-1657
> Project: Teiid Designer
> Issue Type: Sub-task
> Components: Documentation
> Reporter: Barry LaFond
> Fix For: 8.6
>
> Attachments: TestUDF.jar, translator-yahoo-7.1.0.jar
>
>
> The E2E Yahoo UDF Test Script involves helping users understand and work with a custom translator as well as a User Defined Function.
> Develop a Wiki article that walks a user through the setup, modeling and testing of this use-case.
> Attached is the custom translator jar and the custom UDF jar.
> Note for 8.3, the notion of UDF's are now confined to View models. See TEIIDDES-1973 and TEIIDDES-1974 for changes and tweak the E2E script to reflect these changes.
--
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, 1 month
[JBoss JIRA] (TEIIDDES-1995) Add templates for OBJECTTABLE, TEXTABLE, etc
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1995?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1995:
----------------------------------------
Office discussions have led to more questions about this feature and how it should be implemented.
The nature of SQL definition in Designer really begs for providing a more robust/full set of SQL fragments to handle the special Language objects supported by the Teiid runtime and query parser framework.
TEXTTABLE, XMLTABLE, OBJECTTABLE, ARRAYTABLE would be a primary focus.
We could provide a small set of templates for each of these with variables/placeholders for the user to replace. Ultimately this begs for enhancing the code-completion framework. So all the formatting/BNF rules for these objects would have to be captured and implemented.... and that's not a small effort.
{code}
TEXTTABLE(expression [SELECTOR string] COLUMNS <COLUMN>, ... [NO ROW DELIMITER] [DELIMITER char] [(QUOTE|ESCAPE) char] [HEADER [integer]] [SKIP integer]) AS name
>> COLUMN := name (FOR ORDINALITY | datatype [WIDTH integer [NO TRIM]] [SELECTOR string integer])
>> see: https://docs.jboss.org/author/display/TEIID/FROM+Clause#FROMClause-TEXTTABLE
OBJECTTABLE([LANGUAGE lang] rowScript [PASSING val AS name ...] COLUMNS colName colType colScript [DEFAULT defaultExpr] ...) AS id
ARRAYTABLE(expression COLUMNS <COLUMN>, ...) AS name
>> COLUMN := name datatype
XMLTABLE([<NSP>,] xquery-expression [<PASSING>] [COLUMNS <COLUMN>, ... )] AS name
>> COLUMN := name (FOR ORDINALITY | (datatype [DEFAULT expression] [PATH string]))
{code}
Pushing to 8.7
> Add templates for OBJECTTABLE, TEXTABLE, etc
> --------------------------------------------
>
> Key: TEIIDDES-1995
> URL: https://issues.jboss.org/browse/TEIIDDES-1995
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Transformations
> Affects Versions: 8.4
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: 8.6
>
>
> Add templates for using OBJECTTABLE, TEXTTABLE, etc. to the the list of templates to apply to the transformation. Example:
> SELECT
> o.{colname}, o.{colname}
> FROM
> {ObjectTableName} as T,
> OBJECTTABLE('x' PASSING T.{ObjectColumnName}Object as x COLUMNS
> {colname} type 'teiid_row.{colname}', ….) as o
--
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, 1 month