[JBoss JIRA] (TEIIDDES-1257) When in transformation editor, enable the ability to right click on an invalid function and create it
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1257?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1257:
-----------------------------------
Attachment: undefined-function-example-sql.png
select-view-model-for-function-dialog.png
select-source-model-for-function-dialog.png
create-user-defined-function-wizard.png
create-source-function-wizard.png
create-function-select-type-dialog.png
…
[View More] create-function-action.png
> When in transformation editor, enable the ability to right click on an invalid function and create it
> -----------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1257
> URL: https://issues.jboss.org/browse/TEIIDDES-1257
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Transformations
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: 8.5
>
> Attachments: create-function-action.png, create-function-select-type-dialog.png, create-source-function-wizard.png, create-user-defined-function-wizard.png, select-source-model-for-function-dialog.png, select-view-model-for-function-dialog.png, undefined-function-example-sql.png
>
>
> When users are creating views (tables exists), they cut-n-paste a query in. But it contains database specific procedures/functions. It would a nice feature to enable the right click on the invalid procedure and allow it to be created, because the metadata is there to define the parameters. The only unknown is the result, but opening the function editor at this time could allow for setting that.
--
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
[View Less]
11 years
[JBoss JIRA] (TEIIDDES-2095) Changes for Generated Rest War
by Ted Jones (JIRA)
Ted Jones created TEIIDDES-2095:
-----------------------------------
Summary: Changes for Generated Rest War
Key: TEIIDDES-2095
URL: https://issues.jboss.org/browse/TEIIDDES-2095
Project: Teiid Designer
Issue Type: Feature Request
Components: Web Services Support
Affects Versions: 8.3.1
Reporter: Ted Jones
Assignee: Ted Jones
Fix For: 8.3.2, 8.5
Need to upgrade RESTEasy …
[View More]war, add resteasy.document.expand.entity.references as context parameter (set to false), and change logic to not delete the json.jar when the RESTEasy jars are not included in the war.
--
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
[View Less]
11 years
[JBoss JIRA] (TEIIDDES-2094) Support for dynamic extension metadata
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIIDDES-2094:
--------------------------------------
Summary: Support for dynamic extension metadata
Key: TEIIDDES-2094
URL: https://issues.jboss.org/browse/TEIIDDES-2094
Project: Teiid Designer
Issue Type: Enhancement
Components: Import/Export
Reporter: Ramesh Reddy
Priority: Critical
Currently when Teiid core implements a new translator or customer/user implements …
[View More]a custom translator that has extension metadata, before they can use the translator in Designer to do some modeling, they need to define MED and register it.
With completion of TEIID-2904, in Teiid 8.7, a Admin api method can be used to interrogate the extension metadata properties defined for a translator.
Currently if user uses Teiid Connection importer with any new translator, it ignores all the extension metadata properties and removes them from the returned DDL that Designer did not recognize. That is really bad for custom connectors, because the VDB will not work properly once it is deployed back to Teiid Server.
I propose to devise a way to generate a dynamic MED for the purposes of current metadata import of the source and use it during the import and not ignore those extension metadata properties.
Depending upon implementation detail, we can also read the translators and their extension metadata support during the initial connection time and create all the required MEDs and register them.
--
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
[View Less]
11 years
[JBoss JIRA] (TEIIDDES-2093) Populate the "import" properties defined for translator
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIIDDES-2093:
--------------------------------------
Summary: Populate the "import" properties defined for translator
Key: TEIIDDES-2093
URL: https://issues.jboss.org/browse/TEIIDDES-2093
Project: Teiid Designer
Issue Type: Enhancement
Components: Import/Export
Affects Versions: 8.2
Reporter: Ramesh Reddy
Fix For: 8.5
With TEIID-2904, Teiid 8.7 will contain a …
[View More]facility to retrieve the import properties for a translator that are used to customize the metadata import process through Admin API.
Teiid Connection importer needs currently is designed to add ad-hoc import properties, and this can be enhanced to populate with this dynamic list, so that user does not have to search through documents for these import properties.
--
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
[View Less]
11 years