[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.1
(was: 9.0)
> 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.1
>
>
> 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.1#6329)
9 years, 7 months
[JBoss JIRA] (TEIIDDES-2281) Usability: add auto bind option
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2281?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2281:
-----------------------------------
Fix Version/s: Future
This would take a fair amount of work and involve using the T-Editor's parser/resolver to find and replace projected symbols. Pushing to Future
> Usability: add auto bind option
> --------------------------------
>
> Key: TEIIDDES-2281
> URL: https://issues.jboss.org/browse/TEIIDDES-2281
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Transformations
> Affects Versions: 8.5.1
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: Future
>
>
> Provide the ability to do auto bind. This would be beneficial when the user is changing the names of the columns in the view (editing the table directly). The assumption here is the user wants to retain the binding when they are changing the name of a column.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months
[JBoss JIRA] (TEIIDDES-2315) User isn't able to add dataroles to original models when reuisng VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2315?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2315:
-----------------------------------
Fix Version/s: Future
> User isn't able to add dataroles to original models when reuisng VDB
> --------------------------------------------------------------------
>
> Key: TEIIDDES-2315
> URL: https://issues.jboss.org/browse/TEIIDDES-2315
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Editors
> Affects Versions: 8.3.3, 8.6
> Reporter: Matus Makovy
> Priority: Minor
> Fix For: Future
>
> Attachments: screenshot1.png, screenshot2.png
>
>
> When reusing VDB, the creator of new VDB isn't able to add dataroles to original VDB models.
> You can see import VDBs when you click on "Show Import VDBs", but you can not access models from this(old/original) VDB in order to set new Dataroles, old ones are ignored.
> Shouldn't be user able to add dataroles to old/original/imported models ?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months
[JBoss JIRA] (TEIIDDES-2355) Provide an option to import pushdown functions
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2355?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2355:
----------------------------------------
So how would Designer utilize the newly exposed info? I started DV6.1 ER3, deployed a SQL Server data source and checked import properties. Should there be a "Import Pushdown Functions" property available in this kit?
I'm also assuming that any pushdown functions would be defined similar to : *CREATE FOREIGN FUNCTION SCORE (val integer) RETURNS integer;* ?
> Provide an option to import pushdown functions
> ----------------------------------------------
>
> Key: TEIIDDES-2355
> URL: https://issues.jboss.org/browse/TEIIDDES-2355
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Teiid Integration
> Reporter: Steven Hawkins
>
> The import property importer.importPushdownFunctions can be set to have Teiid include the pushdown functions as part of the imported schema and there by the ddl used by designer. With TEIID-3098 will prevent there from being ambiguity from doing so (either from multiple models or from the pushdown functions). So Designer should allow users to import these functions if they wish (it could even be a default option).
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months
[JBoss JIRA] (TEIIDDES-2372) Remove Unused Utility Methods
by Dan Florian (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2372?page=com.atlassian.jira.plu... ]
Dan Florian resolved TEIIDDES-2372.
-----------------------------------
Resolution: Done
Merged PR into master branch.
> Remove Unused Utility Methods
> -----------------------------
>
> Key: TEIIDDES-2372
> URL: https://issues.jboss.org/browse/TEIIDDES-2372
> Project: Teiid Designer
> Issue Type: Task
> Components: komodo-common
> Affects Versions: Komodo
> Reporter: Dan Florian
> Assignee: Dan Florian
> Priority: Minor
> Fix For: Komodo
>
>
> Lots of utility classes with lots of methods have been copied over. There are 2 string utility classes. And the utility classes and not named in the same way. The unused methods should be commented out and uncommented as needed. The 2 string utility classes should be combined. And a naming convention for utility classes should be used.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months