teiid-designer-issues June 2010

teiid-designer-issues@lists.jboss.org

1 participants
154 discussions

[JBoss JIRA] Resolved: (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/browse/TEIIDDES-396?page=com.atlassian.jira.plugin... ] Barry LaFond resolved TEIIDDES-396. ----------------------------------- Resolution: Done This old methodology is being replaced with new VDB editing framework which utilizes the user's workspace ".metadata" location instead. Done > Move location for temporary VDB execution state from system temp directory to somewhere under designer workspace > ---------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-396 > URL: https://jira.jboss.org/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/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-261) The Designer Eclipse Feature Should Be Separated Into A Design-Time Feature And A Runtime-Time Feature

by Dan Florian (JIRA)

The Designer Eclipse Feature Should Be Separated Into A Design-Time Feature And A Runtime-Time Feature ------------------------------------------------------------------------------------------------------ Key: TEIIDDES-261 URL: https://jira.jboss.org/jira/browse/TEIIDDES-261 Project: Teiid Designer Issue Type: Task Affects Versions: 7.0 Reporter: Dan Florian Fix For: 7.0 A version of Teiid Designer should be available that does not include the ability to perform data preview, connection management, and VDB execution. This design-time Designer would be suited to users that are strictly data modelers. A "design-time only" Designer would have a reduced footprint over the current Designer. Another Designer that is more suited to users that test models and VDBs would then be needed. We would build this Designer by adding on the data preview, connection management, and VDB execution capabilities to the "design-time only" Designer. Eclipse features are the way that different builds of the Designer can be accomplished. We have done a pretty good job of isolating the data preview, connection management, and VDB execution code into their own Eclipse plugins. The Eclipse plugins that were designed to handle these capabilities are the dqp, dqp.ui, and sqlexplorer plugins. However, there are a few cases of code found in "design-time only" plugins that depend on these data preview, connection management, and VDB execution plugins. These cases will have to be addressed in order to complete this task. Separate JIRAs should be written for these cases as they are found and tied to this JIRA. -- 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

15 years, 5 months

3
4
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-460) Convert Legacy Web Services to CXF

by Ted Jones (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-460?page=com.atlassian.jira.plugin... ] Ted Jones moved TEIID-1034 to TEIIDDES-460: ------------------------------------------- Project: Teiid Designer (was: Teiid) Key: TEIIDDES-460 (was: TEIID-1034) Affects Version/s: 6.2.0 (was: 6.2.0) Component/s: (was: SOAP Services) Fix Version/s: 7.0 (was: 7.0) > Convert Legacy Web Services to CXF > ---------------------------------- > > Key: TEIIDDES-460 > URL: https://jira.jboss.org/browse/TEIIDDES-460 > Project: Teiid Designer > Issue Type: Task > Affects Versions: 6.2.0 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 7.0 > > > Need to create a web services solution using CXF utilizing the web service models created in Designer. This is replacement functionality for the old MMSoap that used Axis2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-459) Designer's 'Create XML View Documents' feature does not enforce sequence order in some circumstances

by Jerry Helbling (JIRA)

Designer's 'Create XML View Documents' feature does not enforce sequence order in some circumstances ---------------------------------------------------------------------------------------------------- Key: TEIIDDES-459 URL: https://jira.jboss.org/browse/TEIIDDES-459 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 6.3 Reporter: Jerry Helbling Assignee: John Verhaeg Priority: Minor promote fix from JBEDSP-1229 to Teiid. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

2
1
0 / 0

← Newer
1
...
13
14
15
16
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues June 2010