March 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2445) Set connection profile action uses wrong driver info.

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2445?page=com.atlassian.jira.plu... ] Juraj Duráni updated TEIIDDES-2445: ----------------------------------- Steps to Reproduce: Import a new connection profile and change jar list - select Database Development perspective > Data Source Explorer > Import - right click to new profile > properties - click "Edit Driver Definition" - select JAR list and change the path Set connection profile - create a new Teiid Model Project - create a new Teiid Metadata Model - select Relational and Source Model - right click to the new source model and select Modeling > Set Connection Profile (select newly created connection profile) Check the driver info - right click to the source model - select Modeling > View Connection Profile Info - the jarList property contains old JAR path was: Import a new connection profile and change jar list - select Database Development perspective > Data Source Explorer > Import - right click to new profile > properties - click "Edit Driver Definition" - select JAR list and change the path Set connection profile - create a new Teiid Model Project - create a new Teiid Metadata Model - select Relational and Source Model - right click to the new source model and select Modeling > Set Connection Profile (select newly created connection profile) Check the driver info - right click to the source model - select Modeling > View Connection Profile Info - the jarList property contains old JAR path > Set connection profile action uses wrong driver info. > ----------------------------------------------------- > > Key: TEIIDDES-2445 > URL: https://issues.jboss.org/browse/TEIIDDES-2445 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.6.1 > Environment: JBDS: 7.1.1.GA > TD: 8.6.1.CR1 > OS: Win 7 > Reporter: Juraj Duráni > > If a new connection profile is imported (Database Development > Data Source explorer > Import) and its driver is changed afterward (jar list), then Set Connection Profile action sets connection profile to a source model with old jar-list-paths. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2445) Set connection profile action uses wrong driver info.

by Juraj Duráni (JIRA)

Juraj Duráni created TEIIDDES-2445: -------------------------------------- Summary: Set connection profile action uses wrong driver info. Key: TEIIDDES-2445 URL: https://issues.jboss.org/browse/TEIIDDES-2445 Project: Teiid Designer Issue Type: Bug Affects Versions: 8.6.1 Environment: JBDS: 7.1.1.GA TD: 8.6.1.CR1 OS: Win 7 Reporter: Juraj Duráni If a new connection profile is imported (Database Development > Data Source explorer > Import) and its driver is changed afterward (jar list), then Set Connection Profile action sets connection profile to a source model with old jar-list-paths. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2379) A view should not be allowed to set the materialization target to itself

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2379?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2379: ---------------------------------------- This is partially fixed for Properties View. Pushing to 9.0.2/9.1 to add logic to prevent editing these types of properties in the Table Editor > A view should not be allowed to set the materialization target to itself > ------------------------------------------------------------------------ > > Key: TEIIDDES-2379 > URL: https://issues.jboss.org/browse/TEIIDDES-2379 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.6 > Reporter: Steven Hawkins > Assignee: Barry LaFond > Fix For: 9.0, 9.0.2, 8.6.2 > > > A user inadvertently set the materialization target to itself and received a recursive planning exception at runtime. Designer should prevent this if possible (ideally it would prevent any materialization target that results in a cycle). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2379) A view should not be allowed to set the materialization target to itself

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2379?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2379: ----------------------------------- Fix Version/s: 9.0.2 8.6.2 (was: 8.6.1) (was: 9.0.1) > A view should not be allowed to set the materialization target to itself > ------------------------------------------------------------------------ > > Key: TEIIDDES-2379 > URL: https://issues.jboss.org/browse/TEIIDDES-2379 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.6 > Reporter: Steven Hawkins > Assignee: Barry LaFond > Fix For: 9.0, 9.0.2, 8.6.2 > > > A user inadvertently set the materialization target to itself and received a recursive planning exception at runtime. Designer should prevent this if possible (ideally it would prevent any materialization target that results in a cycle). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2347) Undeploying a Dynamic VDB results in TeiidAdminProcessing exception

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2347?page=com.atlassian.jira.plu... ] Andrej Šmigala closed TEIIDDES-2347. ------------------------------------ Verified in 8.6.1.CR1 and 9.0.1 > Undeploying a Dynamic VDB results in TeiidAdminProcessing exception > ------------------------------------------------------------------- > > Key: TEIIDDES-2347 > URL: https://issues.jboss.org/browse/TEIIDDES-2347 > Project: Teiid Designer > Issue Type: Bug > Components: Patch Release, Teiid Integration, VDB & Execution > Affects Versions: 8.6 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 9.0, 8.6.1 > > > 1) Deploy a Dynamic VDB on a server > 2) Select in Designer Servier view and select "Undeploy VDB" > 3) Get following uncaught exception: > {code} > !ENTRY org.teiid.designer.dqp.ui 2 0 2014-09-22 15:53:57.594 > !MESSAGE Error undeploying VDB: Portfolio > !STACK 0 > org.teiid.adminapi.AdminProcessingException: {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014807: Management resource '[(\"deployment\" => \"Portfolio.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) > {code} > We're only catching "OperationFormatException" format exception. maybe we should catch this type too and display to user? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2374) New Procedure Wizard's source function option doesn't set FUNCTION = true correctly

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2374?page=com.atlassian.jira.plu... ] Andrej Šmigala closed TEIIDDES-2374. ------------------------------------ Verified in 8.6.1.CR1 and 9.0.1 > New Procedure Wizard's source function option doesn't set FUNCTION = true correctly > ------------------------------------------------------------------------------------ > > Key: TEIIDDES-2374 > URL: https://issues.jboss.org/browse/TEIIDDES-2374 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.6 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 9.0, 8.6.1 > > > Noticed that creating a source function doesn't set the Funtion == TRUE correctly. Looks like the handling of the radio boxes is incorrect. > Same is true for Virtual model procedure wizard. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2356) Import DDL file from workspace location does not work. File not found

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2356?page=com.atlassian.jira.plu... ] Andrej Šmigala closed TEIIDDES-2356. ------------------------------------ Verified in 8.6.1.CR1 and 9.0.1 > Import DDL file from workspace location does not work. File not found > --------------------------------------------------------------------- > > Key: TEIIDDES-2356 > URL: https://issues.jboss.org/browse/TEIIDDES-2356 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release > Affects Versions: 8.6 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 9.0, 8.6.1 > > > Trying to import a DDL file from a workspace location cannot find the designated file. > The workspace relative path is shown and stored in the DdlImporter and combo-box text, however, the importer expects an existing Java File location. > Need to convert the selected IResource/IFile to a file and use that path instead: > >>> final File realFile = choice.getLocation().toFile(); -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2324) Rest Importer: Use invokeHTTP procedure with Named Parameters

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2324?page=com.atlassian.jira.plu... ] Matus Makovy commented on TEIIDDES-2324: ---------------------------------------- verified TD 8.6.1.CR1 > Rest Importer: Use invokeHTTP procedure with Named Parameters > ------------------------------------------------------------- > > Key: TEIIDDES-2324 > URL: https://issues.jboss.org/browse/TEIIDDES-2324 > Project: Teiid Designer > Issue Type: Enhancement > Affects Versions: 8.6 > Reporter: Ramesh Reddy > Assignee: Ted Jones > Fix For: 9.0, 8.6.1, 9.0.1 > > > When generating the transformation for rest procedure, in the invokeHTTP procedure, use named procedures. aka like > invokeHTTP (action=>'GET', endpoint=>qp, stream=>'true') > this way one can avoid putting the null parametes, as well as if there are additional parameters added to invokeHTTP as did in TEIID-3016 the generated procedure will be error free for next versions. I did see one error here with Teiid 8.9 Alpha, which is logged as TEIID-3107 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2288) "Starting JBoss EAP 6.1+...e Server" stays 0% on Windows

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2288?page=com.atlassian.jira.plu... ] Matus Makovy commented on TEIIDDES-2288: ---------------------------------------- tested with TD 8.6.1.CR1 - no problems > "Starting JBoss EAP 6.1+...e Server" stays 0% on Windows > -------------------------------------------------------- > > Key: TEIIDDES-2288 > URL: https://issues.jboss.org/browse/TEIIDDES-2288 > Project: Teiid Designer > Issue Type: Bug > Components: Eclipse Integration > Affects Versions: 8.3.3 > Environment: - Windows > - JDK 1.7.0_62 > - JDV 6.0.0 > - JBDS 7.1.0 > - JBDS-7.1.1/jbdevstudio-integration-stack-updatesite-7.0.2.GA.zip > Reporter: Hisanobu Okuda > Assignee: Paul Richardson > Fix For: 9.0, 8.6.1, 9.0.1 > > > A server status "Starting JBoss EAP 6.1+...e Server" which is shown in the right-bottom in the JBDS window stays 0%, when clicking "Restart the server (Ctrl+Alt+R)" button, and does not go to 100%. The issue occurs on only Windows, but not on Linux. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2165) User can not use '.' for VDB name in order to version the VDB

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2165?page=com.atlassian.jira.plu... ] Matus Makovy commented on TEIIDDES-2165: ---------------------------------------- verified TD 8.6.1.CR1 > User can not use '.' for VDB name in order to version the VDB > ------------------------------------------------------------- > > Key: TEIIDDES-2165 > URL: https://issues.jboss.org/browse/TEIIDDES-2165 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.3.2 > Reporter: Van Halbert > Assignee: Barry LaFond > Priority: Blocker > Fix For: 9.0, 8.6.1, 9.0.1 > > > User can not use '.' for VDB name. > According to the Official document[1], user should be able to use '.' to specify the version for VDB. > [1]Administration_and_Configuration_Guide:11.2. Set the VDB Version > https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Data_Vir... > Version-Release number of selected component (if applicable): > Steps to Reproduce: > 1. Create a new VDB named "test1.1" > Actual results: > error occurs. Please check attached screenshot named vdb_versioning_error.png > Expected results: > User can use '.' for VDB name. > Additional info: > Teiid Designer 8.3.2.Final-v20140328-2123-B54 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues March 2015