[JBoss JIRA] (TEIIDDES-1751) Using Database Developer, requires running server in order to connect using Teiid JDBC driver
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1751?page=com.atlassian.jira.plu... ]
Barry LaFond moved JBDS-2655 to TEIIDDES-1751:
----------------------------------------------
Project: Teiid Designer (was: Developer Studio (JBoss Developer Studio))
Key: TEIIDDES-1751 (was: JBDS-2655)
Workflow: jira (was: GIT Pull Request workflow )
Component/s: Datatools Integration
(was: teiid)
Security: (was: Public)
> Using Database Developer, requires running server in order to connect using Teiid JDBC driver
> ---------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1751
> URL: https://issues.jboss.org/browse/TEIIDDES-1751
> Project: Teiid Designer
> Issue Type: Bug
> Components: Datatools Integration
> Reporter: Van Halbert
>
> When using Database Developer, created a new datasource (added Teiid JDBC driver from the file system) to connect to a EAP server running Teiid. I would have expected the connection to Teiid to operate as any other jdbc driver and other SQL tools, but in order to connect, I was required to setup a server in JBDS and start it. Which shouldn't be needed in order to make a jdbc connection to an external database.
--
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
11 years
[JBoss JIRA] (TEIIDDES-1719) UDF jar path is required for SalesForce Function Model
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1719?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1719:
----------------------------------------
Implemented changes/fix from above comment.
Just need to test
> 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: Barry LaFond
> 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
11 years
[JBoss JIRA] (TEIIDDES-1719) UDF jar path is required for SalesForce Function Model
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1719?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-1719:
--------------------------------------
Assignee: Barry LaFond (was: Mark Drilling)
> 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: Barry LaFond
> 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
11 years
[JBoss JIRA] (TEIIDDES-1750) Deleting model object with closed editor results in ArrayIndexOutOfBounds exception
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-1750:
--------------------------------------
Summary: Deleting model object with closed editor results in ArrayIndexOutOfBounds exception
Key: TEIIDDES-1750
URL: https://issues.jboss.org/browse/TEIIDDES-1750
Project: Teiid Designer
Issue Type: Bug
Components: Modeling
Affects Versions: 8.1
Reporter: Barry LaFond
Assignee: Paul Richardson
Priority: Critical
Fix For: 8.2
With no model editors open, select a Table in a model in the explorer and click DELETE key.
Results in: ava.lang.ArrayIndexOutOfBoundsException: 0
at org.teiid.designer.core.refactor.ObjectDeleteCommand.getModelResource(ObjectDeleteCommand.java:184)
at org.teiid.designer.core.refactor.ObjectDeleteCommand.checkDependentResources(ObjectDeleteCommand.java:228)
at org.teiid.designer.core.refactor.ObjectDeleteCommand.execute(ObjectDeleteCommand.java:350)
at org.teiid.designer.ui.actions.workers.DeleteWorker$1.execute(DeleteWorker.java:206)
at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Looks like the action may be getting it's selection updated during the async process of opening the editor so the Model get's selected instead of the original table
--
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
11 years
[JBoss JIRA] (TEIIDDES-1719) UDF jar path is required for SalesForce Function Model
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1719?page=com.atlassian.jira.plu... ]
Barry LaFond edited comment on TEIIDDES-1719 at 6/5/13 1:45 PM:
----------------------------------------------------------------
Actually, Salesforce has excludes() and includes() pushdown/source functions that were modeled via this action.
http://help.salesforce.com/help/doc/en/filter_operators.htm
We'll need to re-visit this action and refactor the built functions so Teiid knows they are pushdown functions....
Fix...
* Change action to "Add Salesforce includes()/excludes() pushdown functions"
* Add option in importer to "Add includes()/excludes() pushdown functions
* Change CreateSalesForceFunctionsAction.run() method to add new "procedures" rather then create new Function model with scalar functions.
was (Author: blafond):
Actually, Salesforce has excludes() and includes() pushdown/source functions that were modeled via this action.
http://help.salesforce.com/help/doc/en/filter_operators.htm
We'll need to re-visit this action and refactor the built functions so Teiid knows they are pushdown functions....
> 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
11 years
[JBoss JIRA] (TEIIDDES-1719) UDF jar path is required for SalesForce Function Model
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1719?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1719:
----------------------------------------
Actually, Salesforce has excludes() and includes() pushdown/source functions that were modeled via this action.
http://help.salesforce.com/help/doc/en/filter_operators.htm
We'll need to re-visit this action and refactor the built functions so Teiid knows they are pushdown functions....
> 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
11 years
[JBoss JIRA] (TEIIDDES-1748) Account for Data Source Type Names Change in Teiid 8.4
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1748?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-1748:
--------------------------------
Fix Version/s: 8.2
> Account for Data Source Type Names Change in Teiid 8.4
> ------------------------------------------------------
>
> Key: TEIIDDES-1748
> URL: https://issues.jboss.org/browse/TEIIDDES-1748
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Teiid Integration
> Affects Versions: 8.2
> Reporter: Ted Jones
> Fix For: 8.2
>
>
> Teiid changed the data source source type names in 8.4 which prevents Designer from creating some data sources.
> Prior to 8.4: [teiid-local, teiid-connector-file.rar, teiid, teiid-connector-salesforce.rar, teiid-connector-infinispan.rar, teiid-connector-ldap.rar, teiid-connector-ws.rar, teiid-connector-google.rar, h2]
> 8.4: [teiid-local, teiid, google, ldap, infinispan, file, salesforce, mongodb, webservice, h2]
> Need to account for this difference.
--
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
11 years