February 2010 - teiid-designer-issues

[JBoss JIRA] Moved: (TEIIDDES-381) New Operations and Inputs must be renamed in the Web Service model.

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-381?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-736 to TEIIDDES-381: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-381 (was: JBEDSP-736) Component/s: (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5.3) > New Operations and Inputs must be renamed in the Web Service model. > ------------------------------------------------------------------- > > Key: TEIIDDES-381 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-381 > Project: Teiid Designer > Issue Type: Bug > Environment: 553 RC1 > Reporter: John Doyle > Assignee: Barry LaFond > Priority: Minor > > When you create a new Operation, or a new Input in a Web Service model, they are provided a default name. In order to provide a new name, you have to use the rename menu item. In contrast, when you create a new Table or Column in a Relational model, the new item is given focus in the model explorer and an edti box is opened to allow you the provide a name right away. We should be consistent. -- 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

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-382) Clicking on almost any model property results in incorrect description being displayed

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-382?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-377 to TEIIDDES-382: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-382 (was: JBEDSP-377) Component/s: (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5) > Clicking on almost any model property results in incorrect description being displayed > -------------------------------------------------------------------------------------- > > Key: TEIIDDES-382 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-382 > Project: Teiid Designer > Issue Type: Bug > Reporter: Michael Walker > Assignee: Barry LaFond > Priority: Minor > > Click on a property of a column. Below, you will see: > i. NameInSource of Entity > This is likely to be the description of the "NameInSource" property. We incorrectly assign the same description to every other property. This is not helpful. > Each property should have an accurate description that informs the user what the property represents. They should not have to do to the PDF documentation every time to look this information up - it's too tedious. -- 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

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-379) ERROR Previewing data for nested mapping class in XML Document model

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-379?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-590 to TEIIDDES-379: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-379 (was: JBEDSP-590) Component/s: (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5.3) > ERROR Previewing data for nested mapping class in XML Document model > -------------------------------------------------------------------- > > Key: TEIIDDES-379 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-379 > Project: Teiid Designer > Issue Type: Bug > Reporter: Barry LaFond > Assignee: Barry LaFond > > During testing of Books XML tried to query nested mapping class. Received SQL Server error which was masking the real problem with unresolved/unindexed Input Set objects in criteria. > Suggest we disable previewing Mapping Classes (Staging tables would be OK) until we can find a solution, which may be treating a mapping class like an access pattern. Ramesh suggested we "Swipe" the SQL for a mapping class, present to user a list of "Input Set Parameters" (similar to procedures & access patterns), and inject the user-supplied values into the SQL. The actual SQL called will NOT be Select * FROM XXXXX, but the modified Mapping Class's SQL. > NOTE that the Preview data will be success for the "TOP" mapping class because it doesn't utilize an Input Set. -- 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

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-380) Really annoying focus issues

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-380?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-92 to TEIIDDES-380: -------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-380 (was: JBEDSP-92) Component/s: (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5.2) > Really annoying focus issues > ---------------------------- > > Key: TEIIDDES-380 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-380 > Project: Teiid Designer > Issue Type: Bug > Environment: Linux, executing E2E Yahoo UDF Test Script, step 8. > Reporter: Johnny Verhaeg > Priority: Minor > > While working with a diagram editor (the function definitions editor in this case), every time I need to click on a different application (like the test script) or right-click to display a context menu, the properties view would lose it's context and go back to showing the resource's properties. This is really annoying. We need to do a better job of maintaining the synchronization between the properties view context and the current *appropriate* selection, recognizing when focus changes due to a user selection or just an automatic focus gain (by the resource in this case) due to a temporary focus loss (by the diagram object). -- 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

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-378) NegativeArraySize Exception in Designer Editing Transformation

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-378?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-748 to TEIIDDES-378: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-378 (was: JBEDSP-748) Component/s: (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5.3) > NegativeArraySize Exception in Designer Editing Transformation > -------------------------------------------------------------- > > Key: TEIIDDES-378 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-378 > Project: Teiid Designer > Issue Type: Bug > Environment: Linux > Reporter: Ted Jones > Assignee: Barry LaFond > Attachments: error.log > > > Encountered a NegativeArraySizeException editing a transformation for a virtual table. > To reproduce: > 1. Import 2 BQT sources > 2. Add a virtual model > 3. Add a base table to the virtual model > 4. Add smalla as transformation sources to the virtual table > 5. Highlight and delete all columns in the SQL (all values between SELECT and FROM) > 6. The NegativeArraySizeException is caused -- 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

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-377) Description fields for UDF Model objects are limited to 128 characters

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-377?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-714 to TEIIDDES-377: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-377 (was: JBEDSP-714) Component/s: (was: Designer) Fix Version/s: 7.1 (was: Future Versions) Affects Version/s: (was: 5.5.2) (was: 5.5.1) (was: 5.5) > Description fields for UDF Model objects are limited to 128 characters > ---------------------------------------------------------------------- > > Key: TEIIDDES-377 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-377 > Project: Teiid Designer > Issue Type: Bug > Reporter: Barry LaFond > Fix For: 7.1 > > > While setting descriptions for the SalesForce UDF functions, I received validation errors stating that: "Description exceeds maximum length of: 128" > The com.metamatrix.query.function.metadata.FunctionMetadataValidator class has a hard-coded limit of 128. Noone seems to know why?? -- 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

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-375) Clone Project clones everything except VDBs

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-375?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-645 to TEIIDDES-375: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-375 (was: JBEDSP-645) Issue Type: Bug (was: Task) Component/s: (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5.3) > Clone Project clones everything except VDBs > ------------------------------------------- > > Key: TEIIDDES-375 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-375 > Project: Teiid Designer > Issue Type: Bug > Environment: RHEL & Fedora 7 > Reporter: Paul Nittel > Assignee: Barry LaFond > > I right-clicked on an open project (that contained a VDB, in addition to the other models) and selected Clone Project. When finished, the cloned project was identical, except it had no VDB. > I looked at the requirements for "Clone Project" and didn't see anything about not cloning VDBs. -- 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

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-376) Preview Data Error Dialog - when connection fails - could use improvement.

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-376?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-749 to TEIIDDES-376: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-376 (was: JBEDSP-749) Component/s: (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5.3) > Preview Data Error Dialog - when connection fails - could use improvement. > -------------------------------------------------------------------------- > > Key: TEIIDDES-376 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-376 > Project: Teiid Designer > Issue Type: Bug > Reporter: Mark Drilling > Assignee: Barry LaFond > Priority: Minor > Attachments: exception.txt, ImportErrorDialog.bmp, PreviewErrorDialog.bmp > > > I attempted to preview data - apparently the datasource is unavailable. > The connection failure takes a long time (we may want to improve the progress dialog). If you wait long enough, preview fails but the error dialog doesnt give much information. I compared with the importer error dialog which is much better. > Attaching screen shots of both error dialogs and the stacktrace from preview. -- 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

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-374) Allow copying SQL executed by the Designer's preview functionality, and even "run in SQL Explorer"

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-374?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-585 to TEIIDDES-374: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-374 (was: JBEDSP-585) Component/s: (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5.3) > Allow copying SQL executed by the Designer's preview functionality, and even "run in SQL Explorer" > -------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-374 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-374 > Project: Teiid Designer > Issue Type: Feature Request > Environment: Linux (Fedora 8) > Reporter: Randall Hauch > Assignee: Barry LaFond > Priority: Minor > > The Designer's preview functionality allows me to select a model object (e.g., table, procedure, etc.) and quickly see a preview. Because the results are limited and/or because I have no control over exactly what SQL is executed, I'd like to select a previewed object (from the "History" list in the "Preview" view) and copy the executed SQL into the clipboard. (I can then go to the SQL Explorer view and paste the SQL and then modify it as desired.) Taking this further, I'd like to select a previewed object and choose to "Rerun in SQL Explorer" (although this may have ramifications about choosing which VDB should be executed). -- 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

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-373) Designer: Allow table sorting by column in the Preview Results View.

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-373?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-560 to TEIIDDES-373: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-373 (was: JBEDSP-560) Component/s: (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5.3) > Designer: Allow table sorting by column in the Preview Results View. > -------------------------------------------------------------------- > > Key: TEIIDDES-373 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-373 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Mark Drilling > Assignee: Barry LaFond > Priority: Minor > > Allow the user to sort the preview results table by column. -- 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

14 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues February 2010