February 2010 - teiid-designer-issues

[JBoss JIRA] Moved: (TEIIDDES-312) Modeler Help appears to not be "wired up"

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-312?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-871 to TEIIDDES-312: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-312 (was: JBEDSP-871) Component/s: (was: Designer) Affects Version/s: 7.1 (was: Westport) > Modeler Help appears to not be "wired up" > ----------------------------------------- > > Key: TEIIDDES-312 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-312 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Environment: fedora 10 through Eclipse IDE > Reporter: Paul Nittel > Assignee: Barry LaFond > > Clicking on the various Help menu items provides little to no help. > Help > Search for "Transformation" brings up a possible list of topics (what does "[MMHeader]" mean?). Clicking on them brings up a dialog proclaiming the connection was refused when it tried to connect to 127.0.0.1. > Help > Help Contents has no visible effect. Not even an exception. > Help > Dynamic Help, like Contents, appears to work until you click the link and can't connect to 127.0.0.1. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-311) The exported DDL for MySQL does not work when trying to run it agains the database

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-311?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-223 to TEIIDDES-311: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-311 (was: JBEDSP-223) Component/s: Import/Export (was: Designer) Affects Version/s: Future (was: 5.5.2) > The exported DDL for MySQL does not work when trying to run it agains the database > ---------------------------------------------------------------------------------- > > Key: TEIIDDES-311 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-311 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: Future > Reporter: Van Halbert > > The exported DDL for mysql did not work in either MySql versions 4 or 5. What trying to create the BQT tables. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-310) Query Plan Viewer "expand" button should expand all nodes by default

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-310?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-382 to TEIIDDES-310: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-310 (was: JBEDSP-382) Component/s: Modeling (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5.3) > Query Plan Viewer "expand" button should expand all nodes by default > -------------------------------------------------------------------- > > Key: TEIIDDES-310 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-310 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Reporter: Michael Walker > Priority: Optional > > When viewing a deep query tree, it is tedious to individually click each node to expand it, before finally getting to the access nodes. Perhaps we should default to expanding the entire tree. This is an optional usability improvement. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-309) Designer: Improve the XML Viewer

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-309?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-558 to TEIIDDES-309: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-309 (was: JBEDSP-558) Component/s: Modeling (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5.3) > Designer: Improve the XML Viewer > -------------------------------- > > Key: TEIIDDES-309 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-309 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Reporter: Mark Drilling > Assignee: Dan Florian > Priority: Minor > > Request to improve the XML results view in Designer to have collapsible elements like a browser view. Also, buttons to expand all / collapse all nodes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-308) Addition of ordinal positions for columns within tables/views/resultsets (as well as a means to "MOVE") columns around.

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-308?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-131 to TEIIDDES-308: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-308 (was: JBEDSP-131) Component/s: Modeling (was: Designer) Fix Version/s: (was: PostWestport) > Addition of ordinal positions for columns within tables/views/resultsets (as well as a means to "MOVE") columns around. > ----------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-308 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-308 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Reporter: Marc Shirley > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
0
0 / 0

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

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-307?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-1165 to TEIIDDES-307: ---------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-307 (was: JBEDSP-1165) Component/s: Import/Export (was: Designer) (was: Server) Fix Version/s: (was: PostWestport) > Request ability to import Metadata via CWMI format > -------------------------------------------------- > > Key: TEIIDDES-307 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-307 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Reporter: Debbie Steigner > Assignee: Barry LaFond > > Per request for CWMI import capability into our repository. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-306) xsi:type attributes not being created in XML document instances when required

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-306?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-297 to TEIIDDES-306: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-306 (was: JBEDSP-297) Component/s: Modeling (was: Designer) (was: Query) Fix Version/s: (was: PostWestport) Affects Version/s: (was: 5.5.2) (was: 5.5.3) > xsi:type attributes not being created in XML document instances when required > ----------------------------------------------------------------------------- > > Key: TEIIDDES-306 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-306 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Reporter: Johnny Verhaeg > Priority: Minor > > When an XSD element or its type is marked as abstract, the concrete elements used in the instance document to represent the abstract element must contain an xsi:type attribute with a concrete type as a value. It seems the best way to handle this in the future would be to add a new "type criteria" property and editor to transformations that would behave somewhat like the choice criteria editor. The editor would prompt the user specify one or more concrete types along with criteria used by the server to determine which type to use for a given set of data. This defect is a carryover from defect 20067 in Defect Tracker. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
0
0 / 0

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

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-305?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-330 to TEIIDDES-305: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-305 (was: JBEDSP-330) Component/s: Import/Export (was: Connectors) (was: Designer) Fix Version/s: (was: PostWestport) Affects Version/s: Future (was: 5.5.3) > Create an importer for the LDAP Connector > ----------------------------------------- > > Key: TEIIDDES-305 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-305 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: Future > Reporter: Michael Walker > Priority: Minor > > 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 contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-303) Materialization can fail when MMX passes back data that exceeds the maximum length, as defined in the materialized model.

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-303?page=com.atlassian.jira.p... ] Steven Hawkins moved TEIID-975 to TEIIDDES-303: ----------------------------------------------- Project: Teiid Designer (was: Teiid) Key: TEIIDDES-303 (was: TEIID-975) Component/s: (was: Query Engine) Affects Version/s: 7.1 (was: 7.1) > Materialization can fail when MMX passes back data that exceeds the maximum length, as defined in the materialized model. > ------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-303 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-303 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Environment: Windows 2003 Server, 5.5 + patch 62 > Reporter: Michael Walker > > When querying data from a source model, MMX allows data to exceed the model's length restrictions. For example, a SalesForce model might have a column called "biography:string(200)". Querying data from this column can sometimes result in a string that exceeds 200 characters, and MMX does not truncate the data. > This causes problems when you attempt to materialize the model. Since the create table scripts are based on the model definition, the mat view table will not accommodate data that exceeds the length restrictions. Following the previous example, this means that the biography data will raise a "inserted length too large for column" error, causing the rest of the materialization to fail. > The new materialization process will need to account for this issue, or perhaps MMX should truncate data that exceeds the defined length found within the model. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-302) Address invalid model extension when importing 5.5.X and older SOAP-Relational models

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-302?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-885 to TEIIDDES-302: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-302 (was: JBEDSP-885) Component/s: Documentation (was: Designer) Fix Version/s: (was: Westport) Affects Version/s: 7.1 (was: Westport) > Address invalid model extension when importing 5.5.X and older SOAP-Relational models > ------------------------------------------------------------------------------------- > > Key: TEIIDDES-302 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-302 > Project: Teiid Designer > Issue Type: Task > Components: Documentation > Affects Versions: 7.1 > Reporter: John Doyle > Assignee: John Doyle > > See FEDTOOLS-21 for s description of this defect. Projects created in 5.5.3 and older will contain the invalid extension properties. There are a couple of ways to address this. > A Task that updates the model extension and the models. > Instructions on making the changes manually. > Also, need to updated the doc references for the ResponseIn and ResponseOut properties. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

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 February 2010