[JBoss JIRA] (TEIIDDES-2524) Enable DDL importer to import Teiid CREATE VIRTUAL PROCEDURE DDL
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2524?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2524:
-----------------------------------
Fix Version/s: 9.0.5
> Enable DDL importer to import Teiid CREATE VIRTUAL PROCEDURE DDL
> ----------------------------------------------------------------
>
> Key: TEIIDDES-2524
> URL: https://issues.jboss.org/browse/TEIIDDES-2524
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 9.2, 9.0.5
>
> Attachments: TEIIDDES-2524_work_in_progress.zip
>
>
> in 9.1, we've added ability to set SQL for imported *CREATE VIEW ....* ddl via ddl importer.
> for 9.2 we'll add ability to import *CREATE VIRTUAL PROCEDURE...* ddl.
> This case is a little more complex since the SQL defined in a procedure transformation will include just the BEGIN .... END part of the SQL, so there's an additional step required to extract the relevant SQL string and apply it to the transformation
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (TEIIDDES-2524) Enable DDL importer to import Teiid CREATE VIRTUAL PROCEDURE DDL
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2524?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2524:
--------------------------------------
Assignee: Barry LaFond
> Enable DDL importer to import Teiid CREATE VIRTUAL PROCEDURE DDL
> ----------------------------------------------------------------
>
> Key: TEIIDDES-2524
> URL: https://issues.jboss.org/browse/TEIIDDES-2524
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 9.2
>
> Attachments: TEIIDDES-2524_work_in_progress.zip
>
>
> in 9.1, we've added ability to set SQL for imported *CREATE VIEW ....* ddl via ddl importer.
> for 9.2 we'll add ability to import *CREATE VIRTUAL PROCEDURE...* ddl.
> This case is a little more complex since the SQL defined in a procedure transformation will include just the BEGIN .... END part of the SQL, so there's an additional step required to extract the relevant SQL string and apply it to the transformation
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (TEIIDDES-2346) Deployment and undepoyment of Dynamic VDBs is not yet supported
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2346?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2346:
-----------------------------------
Fix Version/s: 9.0.5
> Deployment and undepoyment of Dynamic VDBs is not yet supported
> ---------------------------------------------------------------
>
> Key: TEIIDDES-2346
> URL: https://issues.jboss.org/browse/TEIIDDES-2346
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.6
> Reporter: Barry LaFond
> Fix For: 9.2, 9.0.5
>
>
> Attempted to *undeploy* a dynamic VDB on my server and Designer threw an exception. (see below)
> We should detect dynamic VDBs in our local VDB cache and maybe display differently (decoration) as well as dissallow Undeploy VDB on selection, or call the approprieate method *undeployDynamicVdb()* instead.
> {code}
> org.teiid.adminapi.AdminProcessingException: {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014807: Management resource '[(\"deployment\" => \"DynamicProducts.vdb\")]' not found"}}
> at org.teiid.runtime.client.admin.v8.Admin8Factory$AdminImpl.execute(Admin8Factory.java:548)
> at org.teiid.runtime.client.admin.v8.Admin8Factory$AdminImpl.undeploy(Admin8Factory.java:782)
> at org.teiid.runtime.client.admin.v8.Admin8Spec.undeploy(Admin8Spec.java:73)
> at org.teiid.runtime.client.admin.ExecutionAdmin.undeployVdb(ExecutionAdmin.java:773)
> at org.teiid.designer.runtime.TeiidServer.undeployVdb(TeiidServer.java:669)
> at org.teiid.designer.runtime.ui.views.TeiidServerActionProvider$4.run(TeiidServerActionProvider.java:236)
> {code}
> 1) ExecutionAdmin.undeployVdb() calls: *adminSpec.undeploy(admin, appendVdbExtension(vdbName), vdb.getVersion())*, so this call is assuming a *.vdb* extension, which fails for dynamic VDBs.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (TEIIDDES-2493) Check for spaces in the parent directory Flat File connection importer
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2493?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2493:
-----------------------------------
Fix Version/s: 9.0.5
(was: 9.0.4)
> Check for spaces in the parent directory Flat File connection importer
> ----------------------------------------------------------------------
>
> Key: TEIIDDES-2493
> URL: https://issues.jboss.org/browse/TEIIDDES-2493
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Reporter: Ramesh Reddy
> Assignee: Mark Drilling
> Fix For: 9.0.5, 9.3
>
>
> Add a check to make sure there are no spaces in the ParentDirectory or root directory path when Flat File Connection Profile is chosen.
> ====================
> The problem is manifested on the server when attempting to query the datasource. On datasource creation, the resource adapter is written to the standalone.xml like this.
> {code:java}
> <config-property name="ParentDirectory">
> /home/mdrilling/My Dir/data
> </config-property>
> {code}
> The embedded space in the ParentDirectory property value is problematic.
> Need to determine whether to (1) disallow a path with spaces or (2) allow it, replacing the space with the appropriate control code ie {code:java} {code} - like this
> {code:java}
> <config-property name="ParentDirectory">
> /home/mdrilling/My Dir/data
> </config-property>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (TEIIDDES-2493) Check for spaces in the parent directory Flat File connection importer
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2493?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2493:
-----------------------------------
Fix Version/s: 9.3
(was: 9.2)
> Check for spaces in the parent directory Flat File connection importer
> ----------------------------------------------------------------------
>
> Key: TEIIDDES-2493
> URL: https://issues.jboss.org/browse/TEIIDDES-2493
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Reporter: Ramesh Reddy
> Assignee: Mark Drilling
> Fix For: 9.0.4, 9.3
>
>
> Add a check to make sure there are no spaces in the ParentDirectory or root directory path when Flat File Connection Profile is chosen.
> ====================
> The problem is manifested on the server when attempting to query the datasource. On datasource creation, the resource adapter is written to the standalone.xml like this.
> {code:java}
> <config-property name="ParentDirectory">
> /home/mdrilling/My Dir/data
> </config-property>
> {code}
> The embedded space in the ParentDirectory property value is problematic.
> Need to determine whether to (1) disallow a path with spaces or (2) allow it, replacing the space with the appropriate control code ie {code:java} {code} - like this
> {code:java}
> <config-property name="ParentDirectory">
> /home/mdrilling/My Dir/data
> </config-property>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months