March 2016 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2775) Provide automated way to convert a old functional model into relational model

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2775?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2775. ---------------------------------- > Provide automated way to convert a old functional model into relational model > ----------------------------------------------------------------------------- > > Key: TEIIDDES-2775 > URL: https://issues.jboss.org/browse/TEIIDDES-2775 > Project: Teiid Designer > Issue Type: Feature Request > Components: Migration, Modeling, Patch Release, Usability > Affects Versions: 9.0.3 > Reporter: Van Halbert > Assignee: Barry LaFond > Priority: Blocker > Labels: release_notes, verified_jbdsis-9.0.0.Beta > Fix For: 9.0.6, 10.0.1 > > Attachments: convert-functions-to-procedures-action.png, convert-functions-to-procedures-dialog.png, converted-functions-to-procedures-diagram.png > > > The primary stipulation is that it will no longer be supported from a design time perspective the ability to create the function model. Consider offering option of an automated utility of some kind for this migration. There is a manual workaround, but for the user and usability, we should do this for them. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2775) Provide automated way to convert a old functional model into relational model

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2775?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2775: ----------------------------------- Labels: release_notes verified_jbdsis-9.0.0.Beta (was: ) > Provide automated way to convert a old functional model into relational model > ----------------------------------------------------------------------------- > > Key: TEIIDDES-2775 > URL: https://issues.jboss.org/browse/TEIIDDES-2775 > Project: Teiid Designer > Issue Type: Feature Request > Components: Migration, Modeling, Patch Release, Usability > Affects Versions: 9.0.3 > Reporter: Van Halbert > Assignee: Barry LaFond > Priority: Blocker > Labels: release_notes, verified_jbdsis-9.0.0.Beta > Fix For: 9.0.6, 10.0.1 > > Attachments: convert-functions-to-procedures-action.png, convert-functions-to-procedures-dialog.png, converted-functions-to-procedures-diagram.png > > > The primary stipulation is that it will no longer be supported from a design time perspective the ability to create the function model. Consider offering option of an automated utility of some kind for this migration. There is a manual workaround, but for the user and usability, we should do this for them. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2389) Add ui support for whole texttable no trim

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2389?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2389. ---------------------------------- I verified that there is an option to include NO TRIM in TEXTTABLE() function options. > Add ui support for whole texttable no trim > ------------------------------------------ > > Key: TEIIDDES-2389 > URL: https://issues.jboss.org/browse/TEIIDDES-2389 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release, Teiid Integration, Transformations > Environment: Teiid 8.8.0 Final > Reporter: Shiveeta Mattoo > Assignee: Barry LaFond > Labels: File-connector, TEXTTABLE, TRIM, release_notes, verified_jbdsis-9.0.0.Beta > Fix For: 10.0.1, 9.2.1 > > > TEIID-3167 allows for NO TRIM to be specified against the whole texttable regardless of whether it is fixed width or delimited. If delimited, then unqualified entries will not be trimmed. For example: > a , "b" > would be parsed as > a ,b - such that the space is preserved after a, but the qualified entry is unaffected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2389) Add ui support for whole texttable no trim

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2389?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2389: ----------------------------------- Labels: File-connector TEXTTABLE TRIM release_notes verified_jbdsis-9.0.0.Beta (was: File-connector TEXTTABLE TRIM) > Add ui support for whole texttable no trim > ------------------------------------------ > > Key: TEIIDDES-2389 > URL: https://issues.jboss.org/browse/TEIIDDES-2389 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release, Teiid Integration, Transformations > Environment: Teiid 8.8.0 Final > Reporter: Shiveeta Mattoo > Assignee: Barry LaFond > Labels: File-connector, TEXTTABLE, TRIM, release_notes, verified_jbdsis-9.0.0.Beta > Fix For: 10.0.1, 9.2.1 > > > TEIID-3167 allows for NO TRIM to be specified against the whole texttable regardless of whether it is fixed width or delimited. If delimited, then unqualified entries will not be trimmed. For example: > a , "b" > would be parsed as > a ,b - such that the space is preserved after a, but the qualified entry is unaffected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2570) RelationalTable contains methods for single UniqueConstraint and collection of UniqueConstraints

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2570?page=com.atlassian.jira.plu... ] Matus Makovy commented on TEIIDDES-2570: ---------------------------------------- Here is the video: https://dl.dropboxusercontent.com/u/21733588/bug2570.mov Is this unique constraint definition relevant only in Source model ? I am asking because when you try to create new table and new unique constraint in View model, there is still the old dialog page for unique constraints. > RelationalTable contains methods for single UniqueConstraint and collection of UniqueConstraints > ------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-2570 > URL: https://issues.jboss.org/browse/TEIIDDES-2570 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release > Affects Versions: 9.0.1 > Reporter: Paul Richardson > Assignee: Barry LaFond > Fix For: 10.0.1, 9.2.1 > > Attachments: edit-unique-constraint-dialog.png, unique-constraint-tab.png > > > While round tripping DDL import and export, the RelationalTable is used to store table unique constraint. The DDL Importer stores the new constraints in the uniqueConstraints collection. However, when saving the model to the BasicTableImpl instance, it actually only looks at the single uniqueConstraint so values are lost. > Dynamic Vdb work has united these fields but retained the getUniqueConstraint() and setUniqueConstraint() methods for backward compatibility with the RelationalTableEditorPanel and ViewTableEditorPanel. These methods are deprecated and the panels should be fixed to support entering multiple unique constraints. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2570) RelationalTable contains methods for single UniqueConstraint and collection of UniqueConstraints

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2570?page=com.atlassian.jira.plu... ] Matus Makovy reopened TEIIDDES-2570: ------------------------------------ I came across a couple of issues with this dialogue. When you define a unique constraint and you don't select any columns, the dialogue displays an error message that there are no columns selected, but you can still hit OK (button is not disabled). Another one is that when you edit the constraint and then hit OK, the Edit button is disabled and it never gets enabled again. I will add a link to video. > RelationalTable contains methods for single UniqueConstraint and collection of UniqueConstraints > ------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-2570 > URL: https://issues.jboss.org/browse/TEIIDDES-2570 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release > Affects Versions: 9.0.1 > Reporter: Paul Richardson > Assignee: Barry LaFond > Fix For: 10.0.1, 9.2.1 > > Attachments: edit-unique-constraint-dialog.png, unique-constraint-tab.png > > > While round tripping DDL import and export, the RelationalTable is used to store table unique constraint. The DDL Importer stores the new constraints in the uniqueConstraints collection. However, when saving the model to the BasicTableImpl instance, it actually only looks at the single uniqueConstraint so values are lost. > Dynamic Vdb work has united these fields but retained the getUniqueConstraint() and setUniqueConstraint() methods for backward compatibility with the RelationalTableEditorPanel and ViewTableEditorPanel. These methods are deprecated and the panels should be fixed to support entering multiple unique constraints. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2600) DDL Importer does not yet support GLOBAL or LOCAL TEMP TABLE

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2600?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2600: ----------------------------------- Labels: release_notes verified_jbdsis-9.0.0.Beta (was: ) > DDL Importer does not yet support GLOBAL or LOCAL TEMP TABLE > ------------------------------------------------------------ > > Key: TEIIDDES-2600 > URL: https://issues.jboss.org/browse/TEIIDDES-2600 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, ModeShape Integration, Patch Release > Reporter: Barry LaFond > Assignee: Barry LaFond > Labels: release_notes, verified_jbdsis-9.0.0.Beta > Fix For: 10.0.1, 9.2.1 > > > Trying to import the following DDL into a View model (see: TEIIDDES-1794) the resulting Table has the Global Temp Table value set to *false*. > I don't think the TeiidDdlImporter is handling these particular cases. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2600) DDL Importer does not yet support GLOBAL or LOCAL TEMP TABLE

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2600?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2600. ---------------------------------- > DDL Importer does not yet support GLOBAL or LOCAL TEMP TABLE > ------------------------------------------------------------ > > Key: TEIIDDES-2600 > URL: https://issues.jboss.org/browse/TEIIDDES-2600 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, ModeShape Integration, Patch Release > Reporter: Barry LaFond > Assignee: Barry LaFond > Labels: release_notes, verified_jbdsis-9.0.0.Beta > Fix For: 10.0.1, 9.2.1 > > > Trying to import the following DDL into a View model (see: TEIIDDES-1794) the resulting Table has the Global Temp Table value set to *false*. > I don't think the TeiidDdlImporter is handling these particular cases. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2622) DDL importer does not properly set Materialized table options

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2622?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2622. ------------------------------------ Resolution: Done master: https://github.com/Teiid-Designer/teiid-designer/commit/31d1c61550d0aee10... > DDL importer does not properly set Materialized table options > ------------------------------------------------------------- > > Key: TEIIDDES-2622 > URL: https://issues.jboss.org/browse/TEIIDDES-2622 > Project: Teiid Designer > Issue Type: Bug > Components: Extension Framework, Import/Export, ModeShape Integration, Patch Release > Affects Versions: 9.0.1, 9.1 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Fix For: 10.0.1, 9.2.1 > > Attachments: TestVDB-vdb.xml > > > Importing a DDL similar to the one [here|https://docs.jboss.org/author/display/teiid810final/External+Materia...], the Materialized property of the view table is set, but the Materialized Table property is not. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2622) DDL importer does not properly set Materialized table options

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2622?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2622: ----------------------------------- Attachment: TestVDB-vdb.xml > DDL importer does not properly set Materialized table options > ------------------------------------------------------------- > > Key: TEIIDDES-2622 > URL: https://issues.jboss.org/browse/TEIIDDES-2622 > Project: Teiid Designer > Issue Type: Bug > Components: Extension Framework, Import/Export, ModeShape Integration, Patch Release > Affects Versions: 9.0.1, 9.1 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Fix For: 10.0.1, 9.2.1 > > Attachments: TestVDB-vdb.xml > > > Importing a DDL similar to the one [here|https://docs.jboss.org/author/display/teiid810final/External+Materia...], the Materialized property of the view table is set, but the Materialized Table property is not. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues March 2016