February 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-168) Designer fails to delete project.

by John Doyle (JIRA)

Designer fails to delete project. --------------------------------- Key: TEIIDDES-168 URL: https://jira.jboss.org/jira/browse/TEIIDDES-168 Project: Teiid Designer Issue Type: Bug Affects Versions: 6.0.0 Environment: Designer 4-27 snapshot build on Fedora 10. Reporter: John Doyle I have two projects that models of the same name. When I try to delete the project in the Model Explorer, I am prompted that I am trying to delete a model when a model in another project depends upon it. As far as I can tell this is not true, and I'm surmising it's getting confused by the name. In any event, when I tell the designer to delete anyway, the delete does not happen. -- 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, 7 months

2
5
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-384) Merge Designer IDE towards JBoss Dev Studio

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-384?page=com.atlassian.jira.p... ] Barry LaFond updated TEIIDDES-384: ---------------------------------- Fix Version/s: 7.0 (was: 6.0.0) Affects Version/s: 7.0 > Merge Designer IDE towards JBoss Dev Studio > ------------------------------------------- > > Key: TEIIDDES-384 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-384 > Project: Teiid Designer > Issue Type: Feature Request > Components: Eclipse Integration > Affects Versions: 7.0 > Reporter: Marc Shirley > Fix For: 7.0 > > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-400) Virtual Procedure transformation editor does not properly assign data length of output parameters

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-400?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-1197 to TEIIDDES-400: ---------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-400 (was: JBEDSP-1197) Component/s: (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5) > Virtual Procedure transformation editor does not properly assign data length of output parameters > -------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-400 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-400 > Project: Teiid Designer > Issue Type: Bug > Reporter: Michael Walker > Assignee: Barry LaFond > > VPs do not properly assign data length of output parameters. It should be based on known length properties within the transformation, which can be derived from the models that are sourced, or logic defined in the transformation. > For example, a virtual procedure does a "select firstName from mytable", and mytable has "firstName:string(255)". The output parameter for the stored procedure will be "firstName:String(10)". It should be 255 characters in length. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-399) Connector Binding Automatically Assigned dialog should have a "Do not show this message again" check-box option

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-399?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-1196 to TEIIDDES-399: ---------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-399 (was: JBEDSP-1196) Component/s: (was: Designer) Affects Version/s: (was: 5.5.3) > Connector Binding Automatically Assigned dialog should have a "Do not show this message again" check-box option > --------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-399 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-399 > Project: Teiid Designer > Issue Type: Feature Request > Environment: Designer 5.5.3 > Windows XP > Reporter: Larry O'Leary > Assignee: Barry LaFond > > I have added source models to a VDB which were created from a JDBC metadata import. Because connection properties are associated with the models the 'add model to VDB' feature automatically creates the connector binding for the added model(s). Upon completion ot adding the models a dialog is displayed indication that the connector(s) were automatically created and added as well. > "One or more connector bindings have been automatically assigned to match the input source properties. The VDB editor must be saved to accept the connector binding change." > As this is an informational message I would imagine that it should have an option to prevent the dialog from being displayed on future model additions to the VDB. For example, a "Do not show this message again" check-box on the dialog that the user can check if they want this message suppressed in the future. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-398) Improve the transformation editor and present a smarter, more Eclipse-like development environment

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-398?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-1195 to TEIIDDES-398: ---------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-398 (was: JBEDSP-1195) Component/s: (was: Designer) Affects Version/s: (was: 5.5) > Improve the transformation editor and present a smarter, more Eclipse-like development environment > -------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-398 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-398 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Michael Walker > > We're in Eclipse, so we could try to present an Eclipse-like development environment: > i. Color highlighting of keywords > ii. Auto-complete > iii. Real-time compilation to highlight and identify syntax errors, etc > iv. Hover-over looks up documentation -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-397) Virtual Procedures validator will not correctly validate whether access patterns are satisfied, resulting in run-time errors

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-397?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-1194 to TEIIDDES-397: ---------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-397 (was: JBEDSP-1194) Component/s: (was: Designer) Affects Version/s: (was: 5.5) > Virtual Procedures validator will not correctly validate whether access patterns are satisfied, resulting in run-time errors > ---------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-397 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-397 > Project: Teiid Designer > Issue Type: Bug > Reporter: Michael Walker > Attachments: novalidation.JPG > > > Create a table that has an access pattern. Then create a virtual procedure that selects data from the table, but does not satisfy the access pattern. Validate the procedure -- it will validate successfully. > This is a bug. We should catch access pattern errors during validation. Instead, this results in run-time errors. > See attached screenshot for an example. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-396) Move location for temporary VDB execution state from system temp directory to somewhere under designer workspace

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-396?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-1016 to TEIIDDES-396: ---------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-396 (was: JBEDSP-1016) Component/s: (was: Designer) Affects Version/s: (was: 5.5.3) > Move location for temporary VDB execution state from system temp directory to somewhere under designer workspace > ---------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-396 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-396 > Project: Teiid Designer > Issue Type: Feature Request > Environment: 5.5SP3 0012 > Reporter: Greg Haber > Assignee: Barry LaFond > Priority: Minor > Attachments: JBEDSP1016Exception.txt > > > When you execute a VDB in Designer, it puts some temporary files in the system temp directory (on Linux /tmp), like the VDB indexes. Then it expects those files to be there during the user's execution session. > Normally, this is OK, but system temp is not a completely stable place - it is common (on both Windows and Linux) for administrators to periodically clean out this directory. > At one time, this cleaning job happened between when the VDB was executed and when the user went to run a query against the VDB, they hit an exception(full text is attached): > Caused by: com.metamatrix.api.exception.MetaMatrixComponentException[0]: > com.metamatrix.modeler.core.ModelerCoreException[0]: > java.io.FileNotFoundException: > /tmp/1237418435308_6014702366987474810/runtime-inf/TABLES.INDEX (No > such file or directory) > at java.io.RandomAccessFile.open(Native Method) > at java.io.RandomAccessFile.<init>(RandomAccessFile.java:212) > at com.metamatrix.internal.core.index.SafeRandomAccessFile.<init>(SafeRandomAccessFile.java:23) > at com.metamatrix.internal.core.index.BlocksIndexInput.open(BlocksIndexInput.java:216) > Now, it would be better to write these files to a private temp space for the user. In fact we do this for Server by changing the java.io.tmp system property to $MM_TMP_DIR. > For Designer 5.5.x we can do the same (change java.io.tmpdir to a directory under the user's workspace, where we know they can read/write), but looking forward to future releases where Designer will run under existing Eclipse installations, changing java.io.tmpdir for all of Eclipse (or mucking with JVM params in Eclipse so this only is set for VDB execution?) may be a bad idea. > Now, I believe (but am not positive) that the location for these temp files is determined by com.metamatrix.core.io.FileUrl, where it uses http://java.sun.com/j2se/1.5.0/docs/api/java/io/File.html#createTempFile(... to get a temp file in the system temp directory. We can easily change code here to instead use http://java.sun.com/j2se/1.5.0/docs/api/java/io/File.html#createTempFile(... to have the temp file created in the directory of our choosing. We may also want to change com.metamatrix.core.io.ZipFileUrl's use of this same method while we're at it. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-395) iTunes data returned in unformatted, gibberish in SQLexplorer (RHEL 5)

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-395?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-671 to TEIIDDES-395: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-395 (was: JBEDSP-671) Component/s: Modeling (was: Designer) Affects Version/s: (was: 5.5.3) > iTunes data returned in unformatted, gibberish in SQLexplorer (RHEL 5) > ---------------------------------------------------------------------- > > Key: TEIIDDES-395 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-395 > Project: Teiid Designer > Issue Type: Task > Components: Modeling > Environment: RHEL 5 > Reporter: Paul Nittel > Assignee: Barry LaFond > Attachments: SqlExplorerGibberish.png > > > The attached screenshot says it all. This is hideous. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-394) Association between a model and a connector binding for use by the Preview functionality should be stored within the model

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-394?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-535 to TEIIDDES-394: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-394 (was: JBEDSP-535) Component/s: Import/Export (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5.3) > Association between a model and a connector binding for use by the Preview functionality should be stored within the model > -------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-394 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-394 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Environment: Designer 5.5.3 > Reporter: Greg Haber > Assignee: Barry LaFond > Priority: Minor > > The proposal here is that a weak association between a model and the connector binding it is associated with for design time preview functionality should be stored in the model file itself, and used to re-establish the association for preview functionality when that model is brought into Designer (such as when an import of a Model Project Set is performed). > The association would be stored in the model with a minimum of information (just the binding name), and the proposed logic is that if there is already an existing binding in Designer with name matching that in the model file, the association for Preview will be automatically established with that binding. > I have attached an e-mail thread between me and rreddy on this topic. > One wrinkle here (not explicitly discussed in the e-mail thread) is if the referenced binding in the model does not previously exist in the Designer workspace, but _is_ defined by a VDB contained in the same model project set, and feature JBEDSP-287 is implemented (so that such VDB binding definitions do get brought in during import). It would be good if the association for Preview functionality between model and binding could also be re-established in this case. This would presumably require that the import of a model project set first import any VDBs before it imported design time models. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-393) Add reconciler capabilities to Virtual Procedure transformation editor

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-393?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-1192 to TEIIDDES-393: ---------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-393 (was: JBEDSP-1192) Component/s: Modeling (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5) > Add reconciler capabilities to Virtual Procedure transformation editor > ---------------------------------------------------------------------- > > Key: TEIIDDES-393 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-393 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Reporter: Michael Walker > Assignee: Barry LaFond > Priority: Minor > > If a user creates a virtual procedure that validates but hits a reconciliation issue, they will receive the error: > the transformation is valid but NOT fully reconciled > Most users attempt to use our reconciler, since they are used to using it to resolve these issues when editing view transformations. However, we don't have a reconciler option for virtual procedures. > We should add this functionality to virtual procedures, especially considering the fact that VPs are difficult to write and debug to begin with, and could use helpful tools wherever possible. -- 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, 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 February 2010