March 2010 - teiid-designer-issues

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

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-312?page=com.atlassian.jira.p... ] Barry LaFond updated TEIIDDES-312: ---------------------------------- Fix Version/s: 7.0 > 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 > Fix For: 7.0 > > > 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

14 years, 2 months

1
0
0 / 0

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

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-396?page=com.atlassian.jira.p... ] Barry LaFond updated TEIIDDES-396: ---------------------------------- Fix Version/s: 7.0 > 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 > Fix For: 7.0 > > 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, 2 months

1
0
0 / 0

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

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-394?page=com.atlassian.jira.p... ] Barry LaFond updated TEIIDDES-394: ---------------------------------- Fix Version/s: No Future > 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 > Fix For: No Future > > > 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-390) Make com.metamatrix.modeler.dqp plugin and helper classes more testable

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-390?page=com.atlassian.jira.p... ] Barry LaFond updated TEIIDDES-390: ---------------------------------- Fix Version/s: 7.0 > Make com.metamatrix.modeler.dqp plugin and helper classes more testable > ----------------------------------------------------------------------- > > Key: TEIIDDES-390 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-390 > Project: Teiid Designer > Issue Type: Bug > Components: Housekeeping > Reporter: Barry LaFond > Priority: Minor > Fix For: 7.0 > > > com.metamatrix.modeler.dqp contains unnecessary nested helper classes and methods that make it difficult to unit test. Spending some time to redesign and refactor makes a lot of sense. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-383) Connector Binding/Connector Type property name display is inconsistent.

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-383?page=com.atlassian.jira.p... ] Barry LaFond updated TEIIDDES-383: ---------------------------------- Fix Version/s: 7.0 > Connector Binding/Connector Type property name display is inconsistent. > ----------------------------------------------------------------------- > > Key: TEIIDDES-383 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-383 > Project: Teiid Designer > Issue Type: Bug > Environment: Designer on Linux, Windows > Reporter: John Doyle > Assignee: Barry LaFond > Priority: Minor > Fix For: 7.0 > > > The display of binding property names in the Properties window is inconsistent. The name of the property is correct derived from the connector type property DisplayName when a binding is selected in the Connectors view. The name of the property is incorrectly derived from the connector types property Name when a connector type is selected in the Connectors view. > eg, Clicking on the SalesforceConnector type, shows a 'username' property in the Properties view. Clicking on an active Salesforce binding, shows a 'User Name' property. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-367) Allow SQLExplorer to connect to live servers and issue queries

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-367?page=com.atlassian.jira.p... ] Barry LaFond updated TEIIDDES-367: ---------------------------------- Fix Version/s: No Future > Allow SQLExplorer to connect to live servers and issue queries > -------------------------------------------------------------- > > Key: TEIIDDES-367 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-367 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Michael Walker > Priority: Minor > Fix For: No Future > > > SQLExplorer is a better, more user-friendly, more full-featured test client than QueryBuilder. > The MMX server sometimes has access to things that client does not. > Connecting directly to servers does not require VDB execution overhead, and allows a more lightweight test client approach. > This might allow depreciation of QB. -- 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, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues March 2010