April 2012 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-344) Transformation editor in Designer should support comments and preserve user formatting

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-344?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-344: ---------------------------------- Fix Version/s: 8.0 Assignee: Barry LaFond > Transformation editor in Designer should support comments and preserve user formatting > -------------------------------------------------------------------------------------- > > Key: TEIIDDES-344 > URL: https://issues.jboss.org/browse/TEIIDDES-344 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Marc Shirley > Assignee: Barry LaFond > Fix For: 8.0 > > > We should support the ability to put comments into transformation code. This is especially useful for virtual procedures, which can get complicated, and could benefit from comments. It also comes up when bringing in SQL code from another environment (e.g. a view from Oracle) -- it would be nice to be able to preserve the comments from the original environment. > It would be nice to support comments prefixed by "--", such as in Oracle. I believe this is standard SQL-92, so we should support it as well. > ------------------- > Fix the designer transformation window, so that it actually saves what the user types (keep formatting, allow comments, etc.). This should really be one of the standard Eclipse text editing windows - MM specific stuff (other than syntax highlighting) should be decoupled from the edit window - there are a couple of requests from ING on this. > ------------------- > As Designer is treated like any other development environment and may have multiple developers working on the same project set, it is very important that comments be supported within the transformations. Although it might be helpful, it is not necessary that these comments get pushed out to source. These comments would be primarily used for developer references. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-343) Inclusion of Data Flows

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-343?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-343. ----------------------------------- Resolution: Rejected Outdated. WOn't be modeling data flows > Inclusion of Data Flows > ----------------------- > > Key: TEIIDDES-343 > URL: https://issues.jboss.org/browse/TEIIDDES-343 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Marc Shirley > > case 4879 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-320) Input Sets on Staging tables for XML documents

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-320?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-320: ---------------------------------- Fix Version/s: 8.0 > Input Sets on Staging tables for XML documents > ---------------------------------------------- > > Key: TEIIDDES-320 > URL: https://issues.jboss.org/browse/TEIIDDES-320 > Project: Teiid Designer > Issue Type: Bug > Components: Documentation > Affects Versions: 7.1 > Reporter: Debbie Steigner > Assignee: Mark Drilling > Fix For: 8.0 > > > In the MetaMatrix Enterprise Designer Users Guide on page 219 it states: > Using Input Sets with Staging Tables > You can use Input Sets withing your staging table transformations as well. When you create a staging table beneath a mapping class, the transformation diagram has an Input Set. > This is not correct, please correct. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-320) Input Sets on Staging tables for XML documents

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-320?page=com.atlassian.jira.plug... ] Barry LaFond reassigned TEIIDDES-320: ------------------------------------- Assignee: Mark Drilling > Input Sets on Staging tables for XML documents > ---------------------------------------------- > > Key: TEIIDDES-320 > URL: https://issues.jboss.org/browse/TEIIDDES-320 > Project: Teiid Designer > Issue Type: Bug > Components: Documentation > Affects Versions: 7.1 > Reporter: Debbie Steigner > Assignee: Mark Drilling > Fix For: 8.0 > > > In the MetaMatrix Enterprise Designer Users Guide on page 219 it states: > Using Input Sets with Staging Tables > You can use Input Sets withing your staging table transformations as well. When you create a staging table beneath a mapping class, the transformation diagram has an Input Set. > This is not correct, please correct. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-307) Request ability to import Metadata via CWMI format

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-307?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-307: ---------------------------------- Fix Version/s: 8.0 > Request ability to import Metadata via CWMI format > -------------------------------------------------- > > Key: TEIIDDES-307 > URL: https://issues.jboss.org/browse/TEIIDDES-307 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 8.0 > > > Per request for CWMI import capability into our repository. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-305) Create an importer for the LDAP Connector

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-305?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-305: ---------------------------------- Fix Version/s: 8.0 Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=780846 (was: https://bugzilla.redhat.com/show_bug.cgi?id=780846) Assignee: Paul Richardson > Create an importer for the LDAP Connector > ----------------------------------------- > > Key: TEIIDDES-305 > URL: https://issues.jboss.org/browse/TEIIDDES-305 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: Future > Reporter: Michael Walker > Assignee: Paul Richardson > Fix For: 8.0 > > > Designer should be able to import LDAP metadata and auto-generate a relational model. This would remove the manual effort of creating models, which is error-prone. > The importer should support the ability to gather cost statistics, as it greatly enhances overall query performance, and is always recommended for use with LDAP data source connections. > The importer could also create normalized tables to represent multi-valued attributes of a given DN. See linked issue for more info on this request. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-278) Designer Enhancement - Add a Join Builder

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-278?page=com.atlassian.jira.plug... ] Barry LaFond reassigned TEIIDDES-278: ------------------------------------- Assignee: Mark Drilling (was: Barry LaFond) > Designer Enhancement - Add a Join Builder > ----------------------------------------- > > Key: TEIIDDES-278 > URL: https://issues.jboss.org/browse/TEIIDDES-278 > Project: Teiid Designer > Issue Type: Feature Request > Affects Versions: Future > Reporter: Debbie Steigner > Assignee: Mark Drilling > > Add a Join Builder to the Designer, similiar to the Criteria Builder, for creating inner, outer and ansi joins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-270) Importer interface should be opened up (published API)

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-270?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-270: ---------------------------------- Fix Version/s: Future > Importer interface should be opened up (published API) > ------------------------------------------------------- > > Key: TEIIDDES-270 > URL: https://issues.jboss.org/browse/TEIIDDES-270 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Marc Shirley > Assignee: Barry LaFond > Fix For: Future > > > with an API for the importer interface we can field build importers to go with custom connectors -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-270) Importer interface should be opened up (published API)

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-270?page=com.atlassian.jira.plug... ] Barry LaFond reassigned TEIIDDES-270: ------------------------------------- Assignee: Barry LaFond > Importer interface should be opened up (published API) > ------------------------------------------------------- > > Key: TEIIDDES-270 > URL: https://issues.jboss.org/browse/TEIIDDES-270 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Marc Shirley > Assignee: Barry LaFond > Fix For: Future > > > with an API for the importer interface we can field build importers to go with custom connectors -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-83) Refactor > Move then UNDO getting Unable to execute Command : SetCommand

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-83?page=com.atlassian.jira.plugi... ] Paul Richardson resolved TEIIDDES-83. ------------------------------------- Release Notes Text: Works for revision 2455 Resolution: Out of Date > Refactor > Move then UNDO getting Unable to execute Command : SetCommand > ------------------------------------------------------------------------ > > Key: TEIIDDES-83 > URL: https://issues.jboss.org/browse/TEIIDDES-83 > Project: Teiid Designer > Issue Type: Task > Components: Modeling > Affects Versions: 6.0.0 > Environment: Linux > Reporter: Paul Nittel > Assignee: Paul Richardson > Fix For: 7.8 > > Attachments: SetCommandError_MPS.zip, UglyError.txt > > > I created a simple project with one source model and a view model. I'm doing Refactor > Move of the source model to ensure the view model remains viable. While doing this I'm getting hideous errors in the Message Log. Here's the top of the exception--the rest is attached, along with a Model Project Set. > Error 2008-04-30 14:26:51.321 Unable to execute Command : SetCommand (label: Set) (description: Set the value to the feature of the owner) (isPrepared: true) (isExecutable: false) (domain: com.metamatrix.modeler.internal.core.container.ContainerEditingDomain@165d9bd) (overrideCommand: null) (owner: com.metamatrix.metamodels.transformation.impl.SqlTransformationMappingRootImpl@1e3e4c5(inputs: [com.metamatrix.metamodels.relational.impl.BaseTableImpl@30c68b (eProxyURI: file:/home/pnittel/mmx/553d080430/des/workspace/RefactorFolderFiles/F1/Parts_Supplier_Sybase_12_5.xmi#mmuuid/31e7e641-5e1e-10c9-a439-94c90911f2fb)], outputs: [com.metamatrix.metamodels.relational.impl.BaseTableImpl@19b8858 (name: SUPPLIER_PARTS, nameInSource: SUPPLIER_PARTS) (system: false, cardinality: 227, supportsUpdate: false, materialized: false)]) (outputReadOnly: false, topToBottom: false, commandStack: null)) (feature: org.eclipse.emf.ecore.impl.EReferenceImpl@cbffde (name: target) (ordered: true, unique: true, lowerBound: 0, upperBound: 1) (changeable: true, volatile: false, transient: false, defaultValueLiteral: null, unsettable: false, derived: false) (containment: false, resolveProxies: true)) (value: [/RefactorFolderFiles/F1/F11/Parts_Supplier_Sybase_12_5.xmi]) (oldValue: com.metamatrix.metamodels.relational.impl.BaseTableImpl@19b8858 (name: SUPPLIER_PARTS, nameInSource: SUPPLIER_PARTS) (system: false, cardinality: 227, supportsUpdate: false, materialized: false)) > Modeler Core Exception: Status ERROR: com.metamatrix.core code=0 Unable to execute Command : SetCommand (label: Set) (description: Set the value to the feature of the owner) (isPrepared: true) (isExecutable: false) (domain: com.metamatrix.modeler.internal.core.container.ContainerEditingDomain@165d9bd) (overrideCommand: null) (owner: com.metamatrix.metamodels.transformation.impl.SqlTransformationMappingRootImpl@1e3e4c5(inputs: [com.metamatrix.metamodels.relational.impl.BaseTableImpl@30c68b (eProxyURI: file:/home/pnittel/mmx/553d080430/des/workspace/RefactorFolderFiles/F1/Parts_Supplier_Sybase_12_5.xmi#mmuuid/31e7e641-5e1e-10c9-a439-94c90911f2fb)], outputs: [com.metamatrix.metamodels.relational.impl.BaseTableImpl@19b8858 (name: SUPPLIER_PARTS, nameInSource: SUPPLIER_PARTS) (system: false, cardinality: 227, supportsUpdate: false, materialized: false)]) (outputReadOnly: false, topToBottom: false, commandStack: null)) (feature: org.eclipse.emf.ecore.impl.EReferenceImpl@cbffde (name: target) (ordered: true, unique: true, lowerBound: 0, upperBound: 1) (changeable: true, volatile: false, transient: false, defaultValueLiteral: null, unsettable: false, derived: false) (containment: false, resolveProxies: true)) (value: [/RefactorFolderFiles/F1/F11/Parts_Supplier_Sybase_12_5.xmi]) (oldValue: com.metamatrix.metamodels.relational.impl.BaseTableImpl@19b8858 (name: SUPPLIER_PARTS, nameInSource: SUPPLIER_PARTS) (system: false, cardinality: 227, supportsUpdate: false, materialized: false)) null > at com.metamatrix.modeler.internal.core.ModelEditorImpl.executeCommandInTransaction(ModelEditorImpl.java:1699) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

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 April 2012