November 2017 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-3153) Fix various Model Extension issues with import/export DDL and vdb.xml formats

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3153?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-3153. ------------------------------------ Resolution: Done this was fixed via: https://github.com/Teiid-Designer/teiid-designer/commit/292ccf0317c654a26... > Fix various Model Extension issues with import/export DDL and vdb.xml formats > ----------------------------------------------------------------------------- > > Key: TEIIDDES-3153 > URL: https://issues.jboss.org/browse/TEIIDDES-3153 > Project: Teiid Designer > Issue Type: Bug > Components: Extension Framework, Import/Export > Affects Versions: 11.1 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 11.1.1 > > Attachments: my_custom_med.mxd > > > Current 11.1 Designer does not fully support import/export DDL and vdb.xml containing model extension properties, especially user's custom/logcal model extension definitions (*.mxd files) > Applicable actions > Model Explorer > * Select source model with table and procedure and apply custom MED via Modeling >> Manage Model Extension Definitions > ** set required properties > * In primary Model Editor tab for the source model > ** Select *Export Teiid DDL* and verify the DDL contains the OPTIONS() properties and the SET NAMESPACE statement > ** Select a table and click the generate data service (vdb.xml) toolbar button (bottom). Verify OPTIONS() and SET NAMESPACE are there > * Create a VDB containing the source model and open VDB Editor > ** Select *Save As XML* button and verify OPTIONS() and SET NAMESPACE are in the generated *.vdb.xml -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3153) Fix various Model Extension issues with import/export DDL and vdb.xml formats

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3153?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-3153: ----------------------------------- Description: Current 11.1 Designer does not fully support import/export DDL and vdb.xml containing model extension properties, especially user's custom/logcal model extension definitions (*.mxd files) Applicable actions Model Explorer * Select source model with table and procedure and apply custom MED via Modeling >> Manage Model Extension Definitions ** set required properties * In Summ was: Current 11.1 Designer does not fully support import/export DDL and vdb.xml containing model extension properties, especially user's custom/logcal model extension definitions (*.mxd files) Applicable actions Model Explorer * Select source model and apply custom MED via Manage Extension > Fix various Model Extension issues with import/export DDL and vdb.xml formats > ----------------------------------------------------------------------------- > > Key: TEIIDDES-3153 > URL: https://issues.jboss.org/browse/TEIIDDES-3153 > Project: Teiid Designer > Issue Type: Bug > Components: Extension Framework, Import/Export > Affects Versions: 11.1 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 11.1.1 > > Attachments: my_custom_med.mxd > > > Current 11.1 Designer does not fully support import/export DDL and vdb.xml containing model extension properties, especially user's custom/logcal model extension definitions (*.mxd files) > Applicable actions > Model Explorer > * Select source model with table and procedure and apply custom MED via Modeling >> Manage Model Extension Definitions > ** set required properties > * In Summ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3153) Fix various Model Extension issues with import/export DDL and vdb.xml formats

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3153?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-3153: ----------------------------------- Description: Current 11.1 Designer does not fully support import/export DDL and vdb.xml containing model extension properties, especially user's custom/logcal model extension definitions (*.mxd files) Applicable actions Model Explorer * Select source model with table and procedure and apply custom MED via Modeling >> Manage Model Extension Definitions ** set required properties * In primary Model Editor tab for the source model ** Select was: Current 11.1 Designer does not fully support import/export DDL and vdb.xml containing model extension properties, especially user's custom/logcal model extension definitions (*.mxd files) Applicable actions Model Explorer * Select source model with table and procedure and apply custom MED via Modeling >> Manage Model Extension Definitions ** set required properties * In Summ > Fix various Model Extension issues with import/export DDL and vdb.xml formats > ----------------------------------------------------------------------------- > > Key: TEIIDDES-3153 > URL: https://issues.jboss.org/browse/TEIIDDES-3153 > Project: Teiid Designer > Issue Type: Bug > Components: Extension Framework, Import/Export > Affects Versions: 11.1 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 11.1.1 > > Attachments: my_custom_med.mxd > > > Current 11.1 Designer does not fully support import/export DDL and vdb.xml containing model extension properties, especially user's custom/logcal model extension definitions (*.mxd files) > Applicable actions > Model Explorer > * Select source model with table and procedure and apply custom MED via Modeling >> Manage Model Extension Definitions > ** set required properties > * In primary Model Editor tab for the source model > ** Select -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3153) Fix various Model Extension issues with import/export DDL and vdb.xml formats

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3153?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-3153: ----------------------------------- Description: Current 11.1 Designer does not fully support import/export DDL and vdb.xml containing model extension properties, especially user's custom/logcal model extension definitions (*.mxd files) Applicable actions Model Explorer * Select source model and apply custom MED via Manage Extension was:Current 11.1 Designer does not fully support import/export DDL and vdb.xml containing model extension properties, especially user's custom/logcal model extension definitions (*.mxd files) > Fix various Model Extension issues with import/export DDL and vdb.xml formats > ----------------------------------------------------------------------------- > > Key: TEIIDDES-3153 > URL: https://issues.jboss.org/browse/TEIIDDES-3153 > Project: Teiid Designer > Issue Type: Bug > Components: Extension Framework, Import/Export > Affects Versions: 11.1 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 11.1.1 > > Attachments: my_custom_med.mxd > > > Current 11.1 Designer does not fully support import/export DDL and vdb.xml containing model extension properties, especially user's custom/logcal model extension definitions (*.mxd files) > Applicable actions > Model Explorer > * Select source model and apply custom MED via Manage Extension -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3153) Fix various Model Extension issues with import/export DDL and vdb.xml formats

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3153?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-3153: -------------------------------------- Assignee: Barry LaFond > Fix various Model Extension issues with import/export DDL and vdb.xml formats > ----------------------------------------------------------------------------- > > Key: TEIIDDES-3153 > URL: https://issues.jboss.org/browse/TEIIDDES-3153 > Project: Teiid Designer > Issue Type: Bug > Components: Extension Framework, Import/Export > Affects Versions: 11.1 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 11.1.1 > > Attachments: my_custom_med.mxd > > > Current 11.1 Designer does not fully support import/export DDL and vdb.xml containing model extension properties, especially user's custom/logcal model extension definitions (*.mxd files) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3153) Fix various Model Extension issues with import/export DDL and vdb.xml formats

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3153?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-3153: ----------------------------------- Attachment: my_custom_med.mxd > Fix various Model Extension issues with import/export DDL and vdb.xml formats > ----------------------------------------------------------------------------- > > Key: TEIIDDES-3153 > URL: https://issues.jboss.org/browse/TEIIDDES-3153 > Project: Teiid Designer > Issue Type: Bug > Components: Extension Framework, Import/Export > Affects Versions: 11.1 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 11.1.1 > > Attachments: my_custom_med.mxd > > > Current 11.1 Designer does not fully support import/export DDL and vdb.xml containing model extension properties, especially user's custom/logcal model extension definitions (*.mxd files) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3153) Fix various Model Extension issues with import/export DDL and vdb.xml formats

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-3153: -------------------------------------- Summary: Fix various Model Extension issues with import/export DDL and vdb.xml formats Key: TEIIDDES-3153 URL: https://issues.jboss.org/browse/TEIIDDES-3153 Project: Teiid Designer Issue Type: Bug Components: Extension Framework, Import/Export Affects Versions: 11.1 Reporter: Barry LaFond Fix For: 11.1.1 Current 11.1 Designer does not fully support import/export DDL and vdb.xml containing model extension properties, especially user's custom/logcal model extension definitions (*.mxd files) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[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 commented on TEIIDDES-3151: ---------------------------------------- attached a sample file: my_custom_med.mxd Can be used to verify: * register/unregister a MED * Apply the custom MED to a source model * Export source model DDL to verify it adds SET NAMESPACE ..... statement and "my_custom_med:xxxxx" properties in OPTIONS() statement * Add source model to VDB and verify Save As XML adds same DDL as above * Add VDB to new project and Generate VDB Archive and Models and verify that source model contains custom MED and same property values. > 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: my_custom_med.mxd, 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)

6 years, 5 months

1
0
0 / 0

[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: ----------------------------------- Attachment: my_custom_med.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 > Assignee: Barry LaFond > Priority: Blocker > Fix For: 11.1.1 > > Attachments: my_custom_med.mxd, 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)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3116) Dependecy diagram options gone

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3116?page=com.atlassian.jira.plu... ] Barry LaFond edited comment on TEIIDDES-3116 at 11/30/17 2:44 PM: ------------------------------------------------------------------ [~virtualdatabase] That action should show up in that menu when you select a virtual table. We've never implemented the "opposite" path.... if you select a source table. Select/Right-click a view or virtual procedure *Modeling...* menu should contain * Generate Dependency Report * Show Dependency Diagram was (Author: blafond): [~virtualdatabase] That action should show up in that menu when you select a virtual table. We've never implemented the "opposite" path.... if you select a source table. > Dependecy diagram options gone > ------------------------------ > > Key: TEIIDDES-3116 > URL: https://issues.jboss.org/browse/TEIIDDES-3116 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 11.0.1 > Reporter: Tom Johnston > > Modeling-->Dependency Diagram options(?) not there -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues November 2017