November 2017 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-3151) OData4 specific MXD is not found

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3151?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-3151: ----------------------------------- Fix Version/s: 11.1.1 > OData4 specific MXD is not found > --------------------------------- > > Key: TEIIDDES-3151 > URL: https://issues.jboss.org/browse/TEIIDDES-3151 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 11.1 > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Priority: Blocker > Fix For: 11.1.1 > > Attachments: odata4.mxd > > > While working on the case I found that there is no "odata4" specific MXD nor the current odata MXD is updated with newer properties for the V4. Since server uses the same namespace the current one needs to be updated. > A sample MXD (minus the namespace) is attached. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3149) Teiid Connection Importer - JNDI name must begin with the java:/ prefix

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3149?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-3149: -------------------------------------- Assignee: Barry LaFond > Teiid Connection Importer - JNDI name must begin with the java:/ prefix > ----------------------------------------------------------------------- > > Key: TEIIDDES-3149 > URL: https://issues.jboss.org/browse/TEIIDDES-3149 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 11.1 > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Priority: Critical > Fix For: 11.1.1 > > > When trying to import metadata from a odata4 source, the Teiid Connection Importer says > JNDI name must begin with the java:/ prefix > but there is no property with that name defined, not one automatically generated -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3149) Teiid Connection Importer - JNDI name must begin with the java:/ prefix

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3149?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-3149: ----------------------------------- Fix Version/s: 11.1.1 > Teiid Connection Importer - JNDI name must begin with the java:/ prefix > ----------------------------------------------------------------------- > > Key: TEIIDDES-3149 > URL: https://issues.jboss.org/browse/TEIIDDES-3149 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 11.1 > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Priority: Critical > Fix For: 11.1.1 > > > When trying to import metadata from a odata4 source, the Teiid Connection Importer says > JNDI name must begin with the java:/ prefix > but there is no property with that name defined, not one automatically generated -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3150) Teiid Connection Importer - Provide a way to refresh the existing "datasources"

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3150?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-3150: ---------------------------------------- [~rareddy] The Refresh action is exposed in the JBoss Server view and I've extended it and added as a toolbar button on the new Connections view. > Teiid Connection Importer - Provide a way to refresh the existing "datasources" > -------------------------------------------------------------------------------- > > Key: TEIIDDES-3150 > URL: https://issues.jboss.org/browse/TEIIDDES-3150 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 11.1 > Reporter: Ramesh Reddy > > Currently, there is no way to refresh the available data sources in the Teiid Connection Importer unless the user goes to Servers tab, and disconnects and reconnects. There needs to a way refresh or just latest data sources when this wizard is invoked. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3152) VDB does not have MXD based properties

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3152?page=com.atlassian.jira.plu... ] Ramesh Reddy updated TEIIDDES-3152: ----------------------------------- Description: After adding a custom MXD (see TEIIDDES-3151), if you import a DDL that makes use of the MXD properties, the model will show the properties in "Extensions" in left side panel. However, when creating a .vdb or dynamic VDB these properties not exported at all in the resulting VDB Attached a sample DDL file, but same would apply if I use Teiid Connection Importer too. was:After adding a custom MXD (see TEIIDDES-3151), if you import a DDL that makes use of the MXD properties, the model will show the properties in "Extensions" in left side panel. However, when creating a .vdb or dynamic VDB these properties not exported at all in the resulting VDB > VDB does not have MXD based properties > -------------------------------------- > > Key: TEIIDDES-3152 > URL: https://issues.jboss.org/browse/TEIIDDES-3152 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 11.1 > Reporter: Ramesh Reddy > Priority: Blocker > Attachments: sample.ddl > > > After adding a custom MXD (see TEIIDDES-3151), if you import a DDL that makes use of the MXD properties, the model will show the properties in "Extensions" in left side panel. However, when creating a .vdb or dynamic VDB these properties not exported at all in the resulting VDB > Attached a sample DDL file, but same would apply if I use Teiid Connection Importer too. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3152) VDB does not have MXD based properties

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIIDDES-3152: -------------------------------------- Summary: VDB does not have MXD based properties Key: TEIIDDES-3152 URL: https://issues.jboss.org/browse/TEIIDDES-3152 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 11.1 Reporter: Ramesh Reddy Priority: Blocker Attachments: sample.ddl After adding a custom MXD (see TEIIDDES-3151), if you import a DDL that makes use of the MXD properties, the model will show the properties in "Extensions" in left side panel. However, when creating a .vdb or dynamic VDB these properties not exported at all in the resulting VDB -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3152) VDB does not have MXD based properties

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3152?page=com.atlassian.jira.plu... ] Ramesh Reddy updated TEIIDDES-3152: ----------------------------------- Attachment: sample.ddl > VDB does not have MXD based properties > -------------------------------------- > > Key: TEIIDDES-3152 > URL: https://issues.jboss.org/browse/TEIIDDES-3152 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 11.1 > Reporter: Ramesh Reddy > Priority: Blocker > Attachments: sample.ddl > > > After adding a custom MXD (see TEIIDDES-3151), if you import a DDL that makes use of the MXD properties, the model will show the properties in "Extensions" in left side panel. However, when creating a .vdb or dynamic VDB these properties not exported at all in the resulting VDB -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3151) OData4 specific MXD is not found

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3151?page=com.atlassian.jira.plu... ] Ramesh Reddy updated TEIIDDES-3151: ----------------------------------- Attachment: odata4.mxd > OData4 specific MXD is not found > --------------------------------- > > Key: TEIIDDES-3151 > URL: https://issues.jboss.org/browse/TEIIDDES-3151 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 11.1 > Reporter: Ramesh Reddy > Priority: Blocker > Attachments: odata4.mxd > > > While working on the case I found that there is no "odata4" specific MXD nor the current odata MXD is updated with newer properties for the V4. Since server uses the same namespace the current one needs to be updated. > A sample MXD (minus the namespace) is attached. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3151) OData4 specific MXD is not found

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIIDDES-3151: -------------------------------------- Summary: OData4 specific MXD is not found Key: TEIIDDES-3151 URL: https://issues.jboss.org/browse/TEIIDDES-3151 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 11.1 Reporter: Ramesh Reddy Priority: Blocker While working on the case I found that there is no "odata4" specific MXD nor the current odata MXD is updated with newer properties for the V4. Since server uses the same namespace the current one needs to be updated. A sample MXD (minus the namespace) is attached. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3150) Teiid Connection Importer - Provide a way to refresh the existing "datasources"

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3150?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-3150: ---------------------------------------- I do not believe I saw a refresh button, where is this located? I tried on right click on the server, and on the wizard. If there is a toolbar not right click, that is a possibility, but I would think if there a toolbar, then it should also be on right click. > Teiid Connection Importer - Provide a way to refresh the existing "datasources" > -------------------------------------------------------------------------------- > > Key: TEIIDDES-3150 > URL: https://issues.jboss.org/browse/TEIIDDES-3150 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 11.1 > Reporter: Ramesh Reddy > > Currently, there is no way to refresh the available data sources in the Teiid Connection Importer unless the user goes to Servers tab, and disconnects and reconnects. There needs to a way refresh or just latest data sources when this wizard is invoked. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues November 2017