Skip to main content
  • EN

I ran a rather lengthy fmw using feature caching...open in one window.

I opened another fmw and decided I didn't need feature caching for that fmw so i disabled feature caching and ran my workspace.

When I returned to my completed fmw window the caching indicators were removed since no caching data existed anymore.

I think this is an obvious issue. Running or not running with Feature Caching enabled should not be globally reflected just workspace specific. Either that or a previously run fmw should not be altered.

Anyone else experience this?

Thanks,

Pete

P.S. About details:

FME Information

Edition: FME Database Edition (node locked-crc)

 

Version: FME(R) 2019.1.0.0 (20190704 - Build 19604 - WIN64)

 

Locale: en_US

 

Codepage: 1252 (ANSI - Latin I)

 

Registration Key: 1-542-353-546

 

Serial Number: 0

 

Customer Number:

 

Home Folder: C:\\Program Files\\FME\\Beta\\

 

Operating System: Microsoft Windows 10 64-bit (Build 17763)

 

I experience and agree with you that enabling and dissabling feature caching should be workspace specific instead of globaly. I suggest you post an Idea for improvement. You will have my vote!

Indeed, I can confirm that this is a known issue.

Be sure to vote for this idea:

https://knowledge.safe.com/content/idea/68833/new-workspace-parameter-always-disable-featurecach.html

 

Reply


Community Stats

30,159
Posts
114,480
Replies
37,806
Members
Terms & ConditionsCookie settings
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.