July 2011 - teiid-designer-issues

[JBoss JIRA] Resolved: (TEIIDDES-294) Query Plan Viewer in Designer does not fully display source queries in the bottom panel if it is long

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-294?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-294. ----------------------------------- Resolution: Won't Fix Designer's SQL Explorer, SQL Results view and Query Plan views are no longer part of Designer. Replaced by Data Tools functionality > Query Plan Viewer in Designer does not fully display source queries in the bottom panel if it is long > ----------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-294 > URL: https://issues.jboss.org/browse/TEIIDDES-294 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Reporter: Michael Walker > Assignee: Barry LaFond > Attachments: queryplantruncation.JPG, queryplantruncation2.JPG > > > Query Plan Viewer in Designer does not fully display source queries in the bottom panel if it is long. See screenshot for example. First screenshot shows the beginning of the source query, second screenshot shows that the source query is truncated when I scroll all the way to the right. > We should show the entire query. > This problem also occurs on Access nodes on the top-half of the query planner. However, you can double-click to view the entire query. This double-click capability is not available on the bottom half for some reason. Perhaps we should add it. > There are some cases where source queries are not displayed in the top-half (query plan screen) but do appear in the bottom half only. In those cases, there's no way to view the entire source query using this editor. Workaround is to view the XML query plan. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-274) Make it easier to double-click to drill down into the transformation for a given view model

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-274?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-274. ----------------------------------- Resolution: Done Not sure when this was fixed, but double-clicking in the "dead area" opens up the transformation for editing as requested. > Make it easier to double-click to drill down into the transformation for a given view model > ------------------------------------------------------------------------------------------- > > Key: TEIIDDES-274 > URL: https://issues.jboss.org/browse/TEIIDDES-274 > Project: Teiid Designer > Issue Type: Feature Request > Components: Diagrams > Affects Versions: Future > Reporter: Michael Walker > Assignee: Barry LaFond > Attachments: deadarea.JPG > > Time Spent: 1 minute > Remaining Estimate: 0 minutes > > We have allocated a very small area of space on each view model that allows you to double-click and drill down into the transformation, but it's too difficult for new users to locate this area, and there's no visual indication of where it begins or ends. > This is very common issue among new Designer users. They want to double-click on a view, to display and/or edit its transformation. They try double-clicking on the middle of the view -- this highlights the columns and does not drill-down. They try clicking on the top of the view, on it's name -- this highlights the view name and does not drill-down. If they happen to leave the view or column highlighted, then they won't be able to drill-down, even if they do click the small area that allows for it. > They give up on double-clicking, and instead, right-click on the view and get a large menu of options. "Open" is buried about half-way down, so some of them don't have the patience to find it. Overall, the process is very frustrating for new users. We should make it much more straightforward to do common operations such as this one. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-189) Plugin details shows version, but not build number

by Paul Nittel (JIRA)

Plugin details shows version, but not build number -------------------------------------------------- Key: TEIIDDES-189 URL: https://jira.jboss.org/jira/browse/TEIIDDES-189 Project: Teiid Designer Issue Type: Bug Components: Build Affects Versions: 6.0.0 Environment: Fedora 10 Reporter: Paul Nittel Since the plugin details shows only the version (6.0.0), there is no way to determine from which build this came. We really need this ability back. -- 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

12 years, 10 months

2
3
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-97) Confusing behavior of Preview Data action on diagram toolbar

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-97?page=com.atlassian.jira.plugi... ] Barry LaFond resolved TEIIDDES-97. ---------------------------------- Resolution: Duplicate Issue This is really the same as TEIIDDES-330 which has been fixed by removing the action from the toolbar. > Confusing behavior of Preview Data action on diagram toolbar > ------------------------------------------------------------ > > Key: TEIIDDES-97 > URL: https://issues.jboss.org/browse/TEIIDDES-97 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview > Affects Versions: 6.0.0 > Reporter: Mark Drilling > Priority: Minor > Fix For: Future > > > The behavior of the previewData action on the diagram toolbar is sometimes confusing. This is occurring because the action enablement is driven by workspace selection, but when you click the diagram toolbar action the first thing that happens is that focus is driven to the diagram - which may not have a selected table. This results in no data being returned. > 1) Open a package diagram. In my case the package diagram was at the level of a schema and nothing selected. > 2) Select a table in model explorer. both the model explorer and diagram toolbar preview buttons enable. > 3) click the model explorer preview button. Data is returned. > 4) click the diagram toolbar preview button. No data returned. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-95) Allow Drag and drop of models and files into VDB Editor panels

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-95?page=com.atlassian.jira.plugi... ] Barry LaFond updated TEIIDDES-95: --------------------------------- Summary: Allow Drag and drop of models and files into VDB Editor panels (was: Designer: UserFiles tab in VDB Editor - allow "Add from Workspace" and DragnDrop) Fix Version/s: 8.0 (was: Future) > Allow Drag and drop of models and files into VDB Editor panels > -------------------------------------------------------------- > > Key: TEIIDDES-95 > URL: https://issues.jboss.org/browse/TEIIDDES-95 > Project: Teiid Designer > Issue Type: Feature Request > Components: Editors > Affects Versions: 6.0.0 > Reporter: Mark Drilling > Priority: Minor > Fix For: 8.0 > > > Allow user to more easily add files from their workspace via button or drag n drop. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIIDDES-998) Requesting more seamlessness in the Teiid Designer "Import Metadata from Text files on file system"

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-998?page=com.atlassian.jira.plug... ] Barry LaFond commented on TEIIDDES-998: --------------------------------------- ALso tested with my JBDS 4.0 + Designer 7.1.1 patch/update No problems > Requesting more seamlessness in the Teiid Designer "Import Metadata from Text files on file system" > --------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-998 > URL: https://issues.jboss.org/browse/TEIIDDES-998 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 7.1.1 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Attachments: TEIIDDES-998-MPS.zip > > > Requesting more seamlessness in the Teiid Designer "Import Metadata from Text files on file system" > When importing virtual procedure definitions it appears that its dependencies are not resolved. Given a file that contains: VProc1, "CREATE VIRTUAL PROCEDURE BEGIN SELECT * FROM ABC.DEF.MJA; END", "Some other description" They're treated as if the dependency doesn't exist, so one gets errors such as: Group does not exist: ABD.DEF.MJA The Base Table must reference 1 or more columns; there are none Cleaning the project doesn't appear to fix the problem. > Currently to resolve the above problem, you must "Validate Transformations", then "Build Imports", Save and Build All to have the errors resolved. The importer should do all of this, the customer should not have to perform these other manual steps -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIIDDES-998) Requesting more seamlessness in the Teiid Designer "Import Metadata from Text files on file system"

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-998?page=com.atlassian.jira.plug... ] Barry LaFond commented on TEIIDDES-998: --------------------------------------- Tested with current 7.5 Trunk Designer in IDE. Could not reproduce. Attached a Model Project Set containing Products Source model, ABC source model, input text file: product_virt_procedures.txt containing: VProc1, "CREATE VIRTUAL PROCEDURE BEGIN SELECT * FROM ABC.DEF.MJA; END", "Some other description" PRODUCT_VPROC, "CREATE VIRTUAL PROCEDURE BEGIN SELECT PRODUCTID, PRODUCTNAME, PRODUCTTYPE FROM PRODUCTS.PRODUCTDATA; END", "Some other description" EXCHANGE_VPROC, "CREATE VIRTUAL PROCEDURE BEGIN SELECT ISSUER, EXCHANGE FROM PRODUCTS.PRODUCTDATA; END", "Some other description" JUST_BUSINESS_VPROC, "CREATE VIRTUAL PROCEDURE BEGIN SELECT PRIMARYBUSINESS FROM PRODUCTS.PRODUCTDATA; END", "Some other description" > Requesting more seamlessness in the Teiid Designer "Import Metadata from Text files on file system" > --------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-998 > URL: https://issues.jboss.org/browse/TEIIDDES-998 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 7.1.1 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Attachments: TEIIDDES-998-MPS.zip > > > Requesting more seamlessness in the Teiid Designer "Import Metadata from Text files on file system" > When importing virtual procedure definitions it appears that its dependencies are not resolved. Given a file that contains: VProc1, "CREATE VIRTUAL PROCEDURE BEGIN SELECT * FROM ABC.DEF.MJA; END", "Some other description" They're treated as if the dependency doesn't exist, so one gets errors such as: Group does not exist: ABD.DEF.MJA The Base Table must reference 1 or more columns; there are none Cleaning the project doesn't appear to fix the problem. > Currently to resolve the above problem, you must "Validate Transformations", then "Build Imports", Save and Build All to have the errors resolved. The importer should do all of this, the customer should not have to perform these other manual steps -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-998) Requesting more seamlessness in the Teiid Designer "Import Metadata from Text files on file system"

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-998?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-998: ---------------------------------- Attachment: TEIIDDES-998-MPS.zip > Requesting more seamlessness in the Teiid Designer "Import Metadata from Text files on file system" > --------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-998 > URL: https://issues.jboss.org/browse/TEIIDDES-998 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 7.1.1 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Attachments: TEIIDDES-998-MPS.zip > > > Requesting more seamlessness in the Teiid Designer "Import Metadata from Text files on file system" > When importing virtual procedure definitions it appears that its dependencies are not resolved. Given a file that contains: VProc1, "CREATE VIRTUAL PROCEDURE BEGIN SELECT * FROM ABC.DEF.MJA; END", "Some other description" They're treated as if the dependency doesn't exist, so one gets errors such as: Group does not exist: ABD.DEF.MJA The Base Table must reference 1 or more columns; there are none Cleaning the project doesn't appear to fix the problem. > Currently to resolve the above problem, you must "Validate Transformations", then "Build Imports", Save and Build All to have the errors resolved. The importer should do all of this, the customer should not have to perform these other manual steps -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1000) Re-importing Relational Model with changed CASE option does not notify diagram to refresh column names

by Barry LaFond (JIRA)

Re-importing Relational Model with changed CASE option does not notify diagram to refresh column names ------------------------------------------------------------------------------------------------------ Key: TEIIDDES-1000 URL: https://issues.jboss.org/browse/TEIIDDES-1000 Project: Teiid Designer Issue Type: Bug Components: Diagrams, Import/Export Affects Versions: 7.4 Reporter: Barry LaFond Assignee: Barry LaFond Fix For: 7.5 1) Import Relational model and choose to set all names to UPPER CASE 2) Package Diagram is displayed 3) RE-import that model and change to use all LOWER CASE names 4) After import, table names are updated, but not columns Force refresh of diagram displays correct names DiagramEditor and Package Diagram frameworks need to handle this -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
1
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-340) Update Incorrect When Changing Model Name On Last Page Of JDBC Wizard

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-340?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-340. ----------------------------------- Resolution: Cannot Reproduce Bug Updates to the JDBC Importer's last page and the migration to using DTP connection profiles have fixed the problem. Can't reproduce > Update Incorrect When Changing Model Name On Last Page Of JDBC Wizard > --------------------------------------------------------------------- > > Key: TEIIDDES-340 > URL: https://issues.jboss.org/browse/TEIIDDES-340 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Environment: Fedora 8 > Reporter: Dan Florian > Assignee: Barry LaFond > Fix For: 7.5 > > > If you change step 3.3.2.1 of the E2E XML Book Set Mixed Test Script to select the project in the tree not the model, the model deltas are not calculated. Proceed as the test script says until the last page. Change the model name to match the update model and check "update." Now hit "Next >" to go to the last page and notice there are no differences when there should be since the foreign keys are being added. If you click "Finish" nothing is updated. This is because if go back in the wizard after changing the model name, the "Foreign Keys" and "Indexes" checkboxes are now unselected. I did not have this problem when running the same kit under MS Windows. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues July 2011