[JBoss JIRA] (TEIIDDES-1829) Add Dynamic Parameter Capability to REST Connection Profile
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1829?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-1829:
--------------------------------
Attachment: new_ws_cp.png
edit_ws_cp.png
> Add Dynamic Parameter Capability to REST Connection Profile
> -----------------------------------------------------------
>
> Key: TEIIDDES-1829
> URL: https://issues.jboss.org/browse/TEIIDDES-1829
> Project: Teiid Designer
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Web Services Support
> Affects Versions: 8.2
> Reporter: Ted Jones
> Assignee: Ted Jones
> Fix For: 8.6, 8.5.1
>
> Attachments: add_parameter_dialog.png, edit_ws_cp.png, new_ws_cp.png
>
>
> Currently the REST CP just takes a URL, potentially with parameters included. Need to add an option for dynamic parameters including URI and/or query string. As parameters are added, we should generate a preview of the full URL. Something like: {code} http://{host}:{port}/restservice/books/book?parm1=value1&parm2=value2.) {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (TEIIDDES-1829) Add Dynamic Parameter Capability to REST Connection Profile
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1829?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-1829:
--------------------------------
Attachment: (was: REST CP.png)
> Add Dynamic Parameter Capability to REST Connection Profile
> -----------------------------------------------------------
>
> Key: TEIIDDES-1829
> URL: https://issues.jboss.org/browse/TEIIDDES-1829
> Project: Teiid Designer
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Web Services Support
> Affects Versions: 8.2
> Reporter: Ted Jones
> Assignee: Ted Jones
> Fix For: 8.6, 8.5.1
>
> Attachments: add_parameter_dialog.png
>
>
> Currently the REST CP just takes a URL, potentially with parameters included. Need to add an option for dynamic parameters including URI and/or query string. As parameters are added, we should generate a preview of the full URL. Something like: {code} http://{host}:{port}/restservice/books/book?parm1=value1&parm2=value2.) {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[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 reassigned TEIIDDES-1884:
--------------------------------------
Assignee: Barry LaFond
> 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
> Security Level: Public(Everyone can see)
> Components: Teiid Integration
> Reporter: Steven Hawkins
> Assignee: Barry LaFond
> Fix For: 8.6
>
> Attachments: create-relational-native-query-procedure-result-set-panel.png, native-query-procedure-in-diagram.png, select-procedure-type-dialog.png
>
>
> 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 was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[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 resolved TEIIDDES-1884.
------------------------------------
Resolution: Done
Done
> 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
> Security Level: Public(Everyone can see)
> Components: Teiid Integration
> Reporter: Steven Hawkins
> Fix For: 8.6
>
> Attachments: create-relational-native-query-procedure-result-set-panel.png, native-query-procedure-in-diagram.png, select-procedure-type-dialog.png
>
>
> 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 was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[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:
-----------------------------------
Attachment: native-query-procedure-in-diagram.png
create-relational-native-query-procedure-result-set-panel.png
select-procedure-type-dialog.png
> 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
> Security Level: Public(Everyone can see)
> Components: Teiid Integration
> Reporter: Steven Hawkins
> Fix For: 8.6
>
> Attachments: create-relational-native-query-procedure-result-set-panel.png, native-query-procedure-in-diagram.png, select-procedure-type-dialog.png
>
>
> 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 was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (TEIIDDES-2206) Oracle DDL Importer should handle comment statements
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2206?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-2206:
----------------------------------------
I do not think JDBC metadata supplies comments, so there is no such support at least now. As per this JIRA, it is separate issue. This case is some one provided you a Oracle DDL, not Oracle connection info to read the metadata from. So, you will be still depend on Modeshape parsing libraries.
> Oracle DDL Importer should handle comment statements
> ----------------------------------------------------
>
> Key: TEIIDDES-2206
> URL: https://issues.jboss.org/browse/TEIIDDES-2206
> Project: Teiid Designer
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Import/Export
> Affects Versions: 8.5
> Reporter: Mark Drilling
> Fix For: 8.6
>
> Attachments: order_test_ddl.txt
>
>
> Request that Oracle DDL comment statements be processed. Use the comment for the object description. Currently the DDL parser does not handle this statement type.
> See attached DDL for an example.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[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 commented on TEIIDDES-1884:
----------------------------------------
So reading back over the discussion...
1) Create a third source *Procedure...* action option
* Procedure
* Source Function
* *Native Query Procedure*
2) Native Query Procedure structure containing...
* 0 or more input parameters (defined by the user)
* Result set with a single *output* column with *object* data type (user can edit/change the column name)
> 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
> Security Level: Public(Everyone can see)
> 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 was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months