Skip to main content
Archived

Allow setting multiple paths to FME_TEMP variable

  • May 19, 2020
  • 3 replies
  • 70 views
takashi
Celebrity

The performance of USB 3 connected external SSD seems to be much better than internal HDD, so I'd like to use a directory in the external SSD drive as FME temporary directory. It's of course possible by setting the SSD directory to the FME_TEMP variable.

However, the external SSD is not always connected. When SSD is not connected, I don't want to use system temporary directory as FME_TEMP since sometimes FME doesn't clean up temp files completely and therefore I would like to manage the remnant temporary files separately from other files.

In my observation, this setting (use D:FME_TEMP if an external drive D is available, C:FME_TEMP otherwise) doesn't seem to be available. It's troublesome to modify FME_TEMP whenever connecting/disconnecting the SSD.

D:FME_TEMP;C:FME_TEMP

It would be nice if FME could configure the temporary directory path from multiple paths set in the FME_TEMP variable.

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

3 replies

A
Forum|alt.badge.img+6

Hi @takashi!

 

While I don't have a specific update for you regarding this idea I do have some good news: In 2020.1 we have introduced improved temp file cleanup for workbench. I'd be curious to know if you notice a difference in your scenarios described above!

 

Best,

Annabelle

takashi
Celebrity
  • takashiCelebrity
  • Author
  • May 23, 2020

Thanks for your comment, @annabelleatsafe. It's a good news that the function for cleaning up temp files will be improved in FME 2020.1.

The issue in my scenario could be worked around if it could be guaranteed that temporary files would be removed completely with the improvement in FME 2020.1. But could it be guaranteed always including a case where the translation stopped with a fatal error?

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
A
Forum|alt.badge.img+6

Hi @takashi,

Yes, temp files will automatically purge after a fatal error during translation but not necessarily if the workbench application crashes (and assuming you are talking about running workspaces only within Workbench!).

 

BUT, if you start up Workbench after it crashes and choose "Purge Temporary Files" from the Tools menu, it should clean up the old files left behind by the crashed Workbench.

 

If there is anything else I can clarify or feedback I can pass on to the team please let me know!

 

Best,

Annabelle

 

Community Stats

32,661
Posts
123,949
Replies
41,076
Members
Terms & ConditionsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.