[JBoss JIRA] (TEIIDDES-1811) Can't import Procedure parameters to source model in Teiid Designer
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1811?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1811:
-----------------------------------
Description:
Usually if we have some changes in source VDB, after we update the source model in designer, we will see the changes.
But for procedure, if we add a new procedure in source VDB, after update SM, we only can see the procedure, but can't see the paramenters of that procedure. We have to manually add them.
In this way, in the future, every time when we update our SM, our procedures parameters will be gone, we have to add them manually.
According to Ramesh -- "That sounds like Designer bug to me. You should log a JIRA with Teiid Designer."
Thanks.
See: https://community.jboss.org/message/830569
was:
Usually if we have some changes in source VDB, after we update the source model in designer, we will see the changes.
But for procedure, if we add a new procedure in source VDB, after update SM, we only can see the procedure, but can't see the paramenters of that procedure. We have to manually add them.
In this way, in the future, every time when we update our SM, our procedures parameters will be gone, we have to add them manually.
According to Ramesh -- "That sounds like Designer bug to me. You should log a JIRA with Teiid Designer."
Thanks.
> Can't import Procedure parameters to source model in Teiid Designer
> -------------------------------------------------------------------
>
> Key: TEIIDDES-1811
> URL: https://issues.jboss.org/browse/TEIIDDES-1811
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.1
> Environment: Windows, eclipse JUNO, Teiid Designer 8.2 alpha1
> Reporter: Jing Li
> Priority: Critical
> Fix For: 8.2
>
>
> Usually if we have some changes in source VDB, after we update the source model in designer, we will see the changes.
>
> But for procedure, if we add a new procedure in source VDB, after update SM, we only can see the procedure, but can't see the paramenters of that procedure. We have to manually add them.
> In this way, in the future, every time when we update our SM, our procedures parameters will be gone, we have to add them manually.
> According to Ramesh -- "That sounds like Designer bug to me. You should log a JIRA with Teiid Designer."
> Thanks.
> See: https://community.jboss.org/message/830569
--
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
10 years, 9 months
[JBoss JIRA] (TEIIDDES-1813) Restart of Designer and JBoss Server does not always reconnect to Teiid Server
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1813?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1813:
----------------------------------------
If user creates Server via Teiid Designer New Server actions and the resulting Teiid instance has a Display name, then restart + preview works
If user creates Server via JBoss Servers View then the resulting Teiid instance will have no display name.
* *Click this link to create a new server...* link
* *right-click New > Server...* action
* *File > New > Other... > Server > Server...* action
So should be able to reproduce this in IDE
> Restart of Designer and JBoss Server does not always reconnect to Teiid Server
> ------------------------------------------------------------------------------
>
> Key: TEIIDDES-1813
> URL: https://issues.jboss.org/browse/TEIIDDES-1813
> Project: Teiid Designer
> Issue Type: Bug
> Components: Usability
> Affects Versions: 8.2
> Reporter: Paul Richardson
> Assignee: Paul Richardson
> Fix For: 8.2
>
>
> Cases where restarting Designer and the configured JBoss Server, fails to reconnect to the Teiid Server. This leaves the user with the expectation that everything is fine, until an operation is conducted, eg. preview, where the server is necessary, resulting in 'no running server messages'.
> Further details and use-case [here|https://community.jboss.org/message/830573#830573].
--
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
10 years, 9 months
[JBoss JIRA] (TEIIDDES-1811) Can't import Procedure parameters to source model in Teiid Designer
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1811?page=com.atlassian.jira.plu... ]
Barry LaFond edited comment on TEIIDDES-1811 at 7/30/13 5:26 PM:
-----------------------------------------------------------------
1) if procedure is defined as Function == TRUE it'll be interpreted as a pushdown/source function. The current data tools jdbc metadata does not have a "folder" for these types of procedures.
2) Create a simple procedure and the procedure was viewable in Data Tools explorer (Stored Procedure) but did not see parameters
* Generated the DDL for that procedure in datatools explorer and it appeared to know about the parameters:
{code:xml}
--<ScriptOptions statementTerminator=";"/>
CREATE PROCEDURE PushdownFunction (
INOUT inParam VARCHAR(4000),
IN returnParam VARCHAR(4000))
NOT DETERMINISTIC
NO_SQL;
{code}
was (Author: blafond):
1) if procedure is defined as Function == TRUE it'll be interpreted as a pushdown/source function. The current data tools jdbc metadata does not have a "folder" for these types of procedures.
2) Create a simple procedure and the procedure was viewable in Data Tools explorer but did not see parameters
* Generated the DDL for that procedure in datatools explorer and it appeared to know about the parameters:
{code:xml}
--<ScriptOptions statementTerminator=";"/>
CREATE PROCEDURE PushdownFunction (
INOUT inParam VARCHAR(4000),
IN returnParam VARCHAR(4000))
NOT DETERMINISTIC
NO_SQL;
{code}
> Can't import Procedure parameters to source model in Teiid Designer
> -------------------------------------------------------------------
>
> Key: TEIIDDES-1811
> URL: https://issues.jboss.org/browse/TEIIDDES-1811
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.1
> Environment: Windows, eclipse JUNO, Teiid Designer 8.2 alpha1
> Reporter: Jing Li
> Priority: Critical
> Fix For: 8.2
>
>
> Usually if we have some changes in source VDB, after we update the source model in designer, we will see the changes.
>
> But for procedure, if we add a new procedure in source VDB, after update SM, we only can see the procedure, but can't see the paramenters of that procedure. We have to manually add them.
> In this way, in the future, every time when we update our SM, our procedures parameters will be gone, we have to add them manually.
> According to Ramesh -- "That sounds like Designer bug to me. You should log a JIRA with Teiid Designer."
> Thanks.
--
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
10 years, 9 months
[JBoss JIRA] (TEIIDDES-1811) Can't import Procedure parameters to source model in Teiid Designer
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1811?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1811:
----------------------------------------
1) if procedure is defined as Function == TRUE it'll be interpreted as a pushdown/source function. The current data tools jdbc metadata does not have a "folder" for these types of procedures.
2) Create a simple procedure and the procedure was viewable in Data Tools explorer but did not see parameters
* Generated the DDL for that procedure in datatools explorer and it appeared to know about the parameters:
{code:xml}
--<ScriptOptions statementTerminator=";"/>
CREATE PROCEDURE PushdownFunction (
INOUT inParam VARCHAR(4000),
IN returnParam VARCHAR(4000))
NOT DETERMINISTIC
NO_SQL;
{code}
> Can't import Procedure parameters to source model in Teiid Designer
> -------------------------------------------------------------------
>
> Key: TEIIDDES-1811
> URL: https://issues.jboss.org/browse/TEIIDDES-1811
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.1
> Environment: Windows, eclipse JUNO, Teiid Designer 8.2 alpha1
> Reporter: Jing Li
> Priority: Critical
> Fix For: 8.2
>
>
> Usually if we have some changes in source VDB, after we update the source model in designer, we will see the changes.
>
> But for procedure, if we add a new procedure in source VDB, after update SM, we only can see the procedure, but can't see the paramenters of that procedure. We have to manually add them.
> In this way, in the future, every time when we update our SM, our procedures parameters will be gone, we have to add them manually.
> According to Ramesh -- "That sounds like Designer bug to me. You should log a JIRA with Teiid Designer."
> Thanks.
--
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
10 years, 9 months
[JBoss JIRA] (TEIIDDES-1719) UDF jar path is required for SalesForce Function Model
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1719?page=com.atlassian.jira.plu... ]
Mark Drilling resolved TEIIDDES-1719.
-------------------------------------
Resolution: Done
> UDF jar path is required for SalesForce Function Model
> ------------------------------------------------------
>
> Key: TEIIDDES-1719
> URL: https://issues.jboss.org/browse/TEIIDDES-1719
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 8.1
> Environment: JBDS 6.0.GA, Teiid Designer 8.1.Beta
> Reporter: Lucie Fabrikova
> Assignee: Mark Drilling
> Fix For: 8.2
>
> Attachments: sf.xmi
>
>
> I created new source model by importing data from metamatrix demo SalesForce test account. On last page of importer, I checked the "Create a procedure for the GetUpdated operation." and "Create a procedure for the GetUpdated operation." Then I tried to generate a function model by following steps; the functional model is invalid.
> Steps to reproduce:
> 1. right-click the sf.xmi: Modelling > Create SalesForce Function Model
> 2. Error log: missing UDF jar path
--
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
10 years, 9 months
[JBoss JIRA] (TEIIDDES-1719) UDF jar path is required for SalesForce Function Model
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1719?page=com.atlassian.jira.plu... ]
Mark Drilling commented on TEIIDDES-1719:
-----------------------------------------
Retested:
- Imported model from salesforce - selected to create the GetUpdate / GetDeleted procedures on last page of importer. No validation errors after import.
- Generated the 'includes' and 'excludes' procedure functions via the 'Modeling > Add Salesforce Pushdown Functions' action.
- Verified the includes and excludes functions worked correctly when used in a Query.
> UDF jar path is required for SalesForce Function Model
> ------------------------------------------------------
>
> Key: TEIIDDES-1719
> URL: https://issues.jboss.org/browse/TEIIDDES-1719
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 8.1
> Environment: JBDS 6.0.GA, Teiid Designer 8.1.Beta
> Reporter: Lucie Fabrikova
> Assignee: Mark Drilling
> Fix For: 8.2
>
> Attachments: sf.xmi
>
>
> I created new source model by importing data from metamatrix demo SalesForce test account. On last page of importer, I checked the "Create a procedure for the GetUpdated operation." and "Create a procedure for the GetUpdated operation." Then I tried to generate a function model by following steps; the functional model is invalid.
> Steps to reproduce:
> 1. right-click the sf.xmi: Modelling > Create SalesForce Function Model
> 2. Error log: missing UDF jar path
--
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
10 years, 9 months
[JBoss JIRA] (TEIIDDES-1812) Remove Result Actions are not working on SQL Results View
by Mark Drilling (JIRA)
Mark Drilling created TEIIDDES-1812:
---------------------------------------
Summary: Remove Result Actions are not working on SQL Results View
Key: TEIIDDES-1812
URL: https://issues.jboss.org/browse/TEIIDDES-1812
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution, Views
Affects Versions: 8.2
Reporter: Mark Drilling
After running several preview queries, I attempted to remove some of the items from the SQL Results history list. The context and toolbar 'Remove Result' and 'Remove All' actions had no effect - results were not removed.
--
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
10 years, 9 months