[JBoss JIRA] (TEIIDDES-2783) Need to add support for parsing OPTIONS in procedure statements
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2783?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-2783.
----------------------------------
Resolution: Done
re-closing after target version changes
> Need to add support for parsing OPTIONS in procedure statements
> ---------------------------------------------------------------
>
> Key: TEIIDDES-2783
> URL: https://issues.jboss.org/browse/TEIIDDES-2783
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, ModeShape Integration, Patch Release
> Reporter: Barry LaFond
> Assignee: Dan Florian
> Labels: release_notes, verified_jbdsis-9.0.0.Beta
> Fix For: 10.0
>
>
> The procedure DDL syntax supports OPTIONS() clause for procedure, parameter, result set, result set columns and datatype (RETURNS) clause.
> CreateProcedureParser.parseReturnsClause() is not processing any OPTIONS() for procedure when RETURNS is just a datatype. See: https://docs.jboss.org/author/display/TEIID/BNF+for+SQL+Grammar#BNFforSQL...
> Should be able to parse the following and set the EMF *Description* (Annotation) value when imported into Designer
> {code}
> CREATE FOREIGN PROCEDURE ProcedureWithRS (
> newParameter_1 string(4000) OPTIONS(ANNOTATION 'parameter 1 description'),
> newParameter_2 string(4000)
> ) RETURNS string(255) OPTIONS(ANNOTATION 'Example')
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (TEIIDDES-2589) The model extension definition "relational" found in model is a different version than the one in the registry.
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2589?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-2589.
----------------------------------
Resolution: Done
re-closing after target version changes
> The model extension definition "relational" found in model is a different version than the one in the registry.
> ---------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2589
> URL: https://issues.jboss.org/browse/TEIIDDES-2589
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Patch Release
> Affects Versions: 9.0, 9.0.1, 9.1, 9.0.2
> Reporter: Lukas Mro
> Assignee: Barry LaFond
> Labels: release_notes, verified_jbdsis-9.0.0.Beta
> Fix For: 10.0, 9.2.1
>
>
> After importing model from TD 8.1.0 to 9.X.X two types of errors occures
> 3 types of errors occures:
> 1. The model extension definition "rest" found in model is not registered in workspace -> this one can be autofix
> 2. The model extension definition "relational" found in model is a different version than the one in the registry -> This one do not have fix
> 3. java.lang.StringIndexOutOfBoundsException: String index out of range: 1
> -> this one do not have fix
> I`m not sure what should i send you, AMA :)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (TEIIDDES-2435) [Usability] The default user when connecting to server should be blanked out
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2435?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-2435.
----------------------------------
Resolution: Done
re-closing after target version changes
> [Usability] The default user when connecting to server should be blanked out
> ----------------------------------------------------------------------------
>
> Key: TEIIDDES-2435
> URL: https://issues.jboss.org/browse/TEIIDDES-2435
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Patch Release, Teiid Integration
> Affects Versions: 9.0.1
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Labels: release_notes, verified_jbdsis-9.0.0.Beta
> Fix For: 10.0, 9.2.1
>
>
> In old versions of the Teiid server, the username "user" was the default. However, with newer versions, there is no default installed user. The person installing has to set that username. Therefore, its requested that the username in Teiid Designer be blanked our so that it eliminates confusion with prior versions.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (TEIIDDES-2723) Properties lost when importing from dynamic VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2723?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-2723.
----------------------------------
Resolution: Done
re-closing after target version changes
> Properties lost when importing from dynamic VDB
> -----------------------------------------------
>
> Key: TEIIDDES-2723
> URL: https://issues.jboss.org/browse/TEIIDDES-2723
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Patch Release, VDB & Execution
> Affects Versions: 9.0.4
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Labels: release_notes, verified_jbdsis-9.0.0.Beta
> Fix For: 10.0, 9.2.1
>
> Attachments: CustomPropertyVdb-vdb.xml, vdb-editor-model-summary.png
>
>
> When importing a -vdb.xml, the properties are not imported. This includes both properties defined in the vdb root, as well as properties defined in the models (not sure where would those be imported though).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (TEIIDDES-2736) Expose all the materialized properties that Teiid supports for configuration
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2736?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-2736.
----------------------------------
Resolution: Done
re-closing after target version changes
> Expose all the materialized properties that Teiid supports for configuration
> ----------------------------------------------------------------------------
>
> Key: TEIIDDES-2736
> URL: https://issues.jboss.org/browse/TEIIDDES-2736
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Modeling, ModeShape Integration, Patch Release, Teiid Integration
> Affects Versions: 9.2
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Labels: release_notes, verified_jbdsis-9.0.0.Beta
> Fix For: 10.0, 9.2.1
>
>
> When changing a view to be materialized, should expose all the possible properties that can be configured to control the materialized process. Maybe this is a usability issue, for which I'm not seeing what's there, but its not obvious.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (TEIIDDES-2750) Cannot launch the Create Data Source in the Guides
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2750?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-2750.
----------------------------------
Resolution: Done
re-closing after target version changes
> Cannot launch the Create Data Source in the Guides
> --------------------------------------------------
>
> Key: TEIIDDES-2750
> URL: https://issues.jboss.org/browse/TEIIDDES-2750
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dialogs
> Affects Versions: 9.0.4
> Reporter: Matej Kralik
> Assignee: Andrej Šmigala
> Priority: Critical
> Labels: release_notes, verified_jbdsis-9.0.0.Beta
> Fix For: 10.0, 9.2.1
>
>
> When I try create data sources in guides action sets, show me NullPointerException. Probably it should displayed error message that there is no connection profile. I've tried it again with work space where i had had configure some connection profile, it was be fine and showed me create data source wizard.
> The same error happens when I have tried to create data source through servers view.
> Exception stack Trace :
> java.lang.NullPointerException
> at org.teiid.designer.runtime.ui.connection.CreateDataSourceWizard.createDialogArea(CreateDataSourceWizard.java:411)
> at org.eclipse.jface.dialogs.TitleAreaDialog.createContents(TitleAreaDialog.java:161)
> at org.eclipse.jface.window.Window.create(Window.java:435)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1101)
> at org.eclipse.jface.window.Window.open(Window.java:797)
> at org.teiid.designer.runtime.ui.connection.CreateDataSourceAction.run(CreateDataSourceAction.java:152)
> at org.teiid.designer.runtime.ui.views.TeiidServerActionProvider$7.run(TeiidServerActionProvider.java:364)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:519)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (TEIIDDES-2771) Cannot edit Native Type extension property for procedure parameter with OUT direction
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2771?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-2771.
----------------------------------
Resolution: Done
re-closing after target version changes
> Cannot edit Native Type extension property for procedure parameter with OUT direction
> -------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2771
> URL: https://issues.jboss.org/browse/TEIIDDES-2771
> Project: Teiid Designer
> Issue Type: Bug
> Components: Extension Framework, Modeling
> Affects Versions: 9.0.5
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Priority: Critical
> Labels: release_notes, verified_jbdsis-8.0.6, verified_jbdsis-9.0.0.Beta
> Fix For: 10.0, 9.0.6, 9.2.1
>
>
> Selecting an OUT parameter and editing the string ends up with empty string, so it's not getting set.
> Found that RelationalModelExtensionAssistant.setPropertyValue() wasn't properly checking for NATIVE_TYPE property, so the value was never getting set. Should be simple fix. Verified that once enabled, this property is getting indexed correctly in RuntimeAdapter.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (TEIIDDES-2700) DDL Export logic does not add non-relational extension properties to the DDL OPTIONS() clause
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2700?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-2700.
----------------------------------
Resolution: Done
re-closing after target version changes
> DDL Export logic does not add non-relational extension properties to the DDL OPTIONS() clause
> ---------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2700
> URL: https://issues.jboss.org/browse/TEIIDDES-2700
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs, Import/Export, Patch Release
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Priority: Blocker
> Labels: release_notes, verified_jbdsis-9.0.0.Beta
> Fix For: 10.0, 9.2.1
>
>
> Trying to Export the attached salesforce XMI model, the salesforce extension properties are not included in the OPTIONS() clause.
> TeiidModelToDdlGenerator.getTableOptions() method is only adding standard relational properties and not looking via the extension assistant framework.
> May need to add a method on the assistant API like *protected Properties getTeiidDdlOptions(BaseTable table)* which would make it clear what the methed returned
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (TEIIDDES-2706) Constraint value ignored in Row Filter dialog
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2706?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-2706.
----------------------------------
Resolution: Done
re-closing after target version changes
> Constraint value ignored in Row Filter dialog
> ---------------------------------------------
>
> Key: TEIIDDES-2706
> URL: https://issues.jboss.org/browse/TEIIDDES-2706
> Project: Teiid Designer
> Issue Type: Bug
> Components: Patch Release, VDB & Execution
> Affects Versions: 9.0.4
> Reporter: Andrej Šmigala
> Assignee: Andrej Šmigala
> Priority: Minor
> Labels: release_notes, verified_jbdsis-9.0.0.Beta
> Fix For: 10.0, 9.2.1
>
> Attachments: Screenshot from 2015-11-02 10-00-55.png, Screenshot from 2015-11-02 10-01-07.png
>
>
> When adding a new row filter, unchecking the Constraint checkbox in the Add Row Filter Definition dialog does not set the constraint property to false.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months