[JBoss JIRA] (TEIIDDES-2289) Usability: Add option on VDB editor to deploy VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2289?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2289:
-----------------------------------
Fix Version/s: 9.2
(was: 9.1)
> Usability: Add option on VDB editor to deploy VDB
> --------------------------------------------------
>
> Key: TEIIDDES-2289
> URL: https://issues.jboss.org/browse/TEIIDDES-2289
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: VDB & Execution
> Affects Versions: 8.5.1
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Priority: Minor
> Fix For: 9.2
>
>
> Since deploying a VDB is what its all about when you're creating the VDB, why not add an option on the VDB editor, so that right after you synch or add models, you can easily deploy the VDB. 3 clicks to deploy every time for something that's done when editing VDB's, should be quick.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-1949) Unable to create function from the reconciler
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1949?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1949:
-----------------------------------
Fix Version/s: 9.2
(was: 9.1)
> Unable to create function from the reconciler
> ----------------------------------------------
>
> Key: TEIIDDES-1949
> URL: https://issues.jboss.org/browse/TEIIDDES-1949
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dialogs
> Affects Versions: 8.3
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Priority: Minor
> Fix For: 9.2
>
>
> Description of problem: Trying to create a function to concatenate last and first names, but nothing would return from dialog after pressing OK. Looking in the log, NPE was found:
> java.lang.NullPointerException
> at org.teiid.query.function.FunctionTree.getFunction(FunctionTree.java:386)
> at org.teiid.query.function.FunctionLibrary.findFunction(FunctionLibrary.java:141)
> at org.teiid.query.function.FunctionLibrary.findFunction(FunctionLibrary.java:1)
> at org.teiid.designer.transformation.ui.reconciler.ReconcilerPanel.syncFunction(ReconcilerPanel.java:725)
> at org.teiid.designer.transformation.ui.reconciler.ReconcilerPanel.expressionButtonPressed(ReconcilerPanel.java:681)
> at org.teiid.designer.transformation.ui.reconciler.ReconcilerPanel$6.widgetSelected(ReconcilerPanel.java:364)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2003) Usability - In a model, group by types (i.e, Table, procedure, etc.)
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2003?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2003:
-----------------------------------
Fix Version/s: Komodo
(was: 9.1)
> Usability - In a model, group by types (i.e, Table, procedure, etc.)
> --------------------------------------------------------------------
>
> Key: TEIIDDES-2003
> URL: https://issues.jboss.org/browse/TEIIDDES-2003
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling
> Affects Versions: 8.3
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: Komodo
>
>
> From a usability standpoint, and when working with large models, it would good to group by type (i.e, Table, procedure, etc.) when laying out a model in the tree on the left.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2109) Create a Connections context menu group next to Modeling group
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2109?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2109:
-----------------------------------
Fix Version/s: 9.2
(was: 9.1)
> Create a Connections context menu group next to Modeling group
> --------------------------------------------------------------
>
> Key: TEIIDDES-2109
> URL: https://issues.jboss.org/browse/TEIIDDES-2109
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling, Views
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 9.2
>
> Attachments: connection-action-menu.png
>
>
> For source models, the Modeling action now contains a number of connection or translator related actions that really don't have anything to do with modeling.
> * Create a *Connection* menu group and place below *Modeling* group
> * Move the following actions to the *Connection* group
> ** Create Data Source
> ** Edit Translator Overrides
> ** Remove Connection Info
> ** Set Connection Profile
> ** Set Translator Name
> ** View Connection Profile Info
> * Maybe group these into Translator/Profile actions with separators
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2265) Allow MultiSelect Columns for creation of indexes
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2265?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2265:
-----------------------------------
Fix Version/s: 9.2
(was: 9.1)
> Allow MultiSelect Columns for creation of indexes
> -------------------------------------------------
>
> Key: TEIIDDES-2265
> URL: https://issues.jboss.org/browse/TEIIDDES-2265
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Modeling
> Reporter: Tom Johnston
> Assignee: Barry LaFond
> Fix For: 9.2
>
>
> I just realized a pain point.
> I have a need to create a number of indexes on views (as they are going to be materialized) but there seems no easy way but one by one.
> I envision the following:
> Multi-select columns (in Model explorer OR Table editor ) and click Modeling and choose Create index (also UK and PK I would think) .. suggest a 'template' (i.e. tableName_ColumnName_IX (auto add 1...x if something or more than one exists) If I choose 2 cols from one table then a check to create one or multiple (default to multiple)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2252) Add preference to importers to specify which characters should be substituted for
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2252?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2252:
-----------------------------------
Fix Version/s: 9.2
(was: 9.1)
> Add preference to importers to specify which characters should be substituted for
> ---------------------------------------------------------------------------------
>
> Key: TEIIDDES-2252
> URL: https://issues.jboss.org/browse/TEIIDDES-2252
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Affects Versions: 8.5
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: 9.2
>
>
> Add a preference that would allow the user to specify a set of characters that should be replaced by another character.
> This enhancement will resolve the issue when ModeShape metadata is being imported using the Teiid Connection importer, and will allow the user to substitute the colon for an underscore. But would also be available for any other data source that would have need for this type of substitution.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-1732) Stream line steps to implement all the steps around materialization
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1732?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1732:
-----------------------------------
Fix Version/s: 9.2
(was: 9.1)
> Stream line steps to implement all the steps around materialization
> --------------------------------------------------------------------
>
> Key: TEIIDDES-1732
> URL: https://issues.jboss.org/browse/TEIIDDES-1732
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling
> Affects Versions: 8.2
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: 9.2
>
>
> Would like to stream line the steps to putting materialization to work. Example:
> - Right mouse click on view, select materialization
> - present wizard to walk thru the following options:
> - create physical table based on selected view/table (export/import of ddl is supported, but would like the table automatically created)
> - put name of mat table into the selected table/view to be materialized
> - [optional] export DDL (file system or clipboard)
> - [optional] create procedure that has the "select into" for refreshing
> Having the procedure provides the immediate ability to call to refresh, without having to remember what tables. Also, with the feature of native queries, could add the truncate call to clear the table.
> Once thru this wizard, (I think) everything is in place to do materialization for the specified table.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 8 months