Versioning of Readers and Writers
+22- Safer
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.
+5- Contributor
+1000 The ability to update Transformers in FME 2016 is awesome. Same thing for readers & writers would be fantastic.
For now we can just know wich version of FME has been used to add a reader or a writer (GENERATE_FME_BUILD_NUM). A true version number like for Transformers and "upgreadable readers and writers" in Workbench navigator would be great.
+22- Contributor
...in particular the ability to identify which parameters are new or have changed, in the same way as the new transformer upgrade approach has been implemented.
A project I worked on recently involved a workspace with very old Geodatabase readers and writers, man were the new versions different when it came to available parameters. This is issue is just not obvious enough...
+20- Contributor
This would be really helpful! I just had an issue that I reported where the answer was just this: upgrade the writer.
+14- Enthusiast
Was just running across this issue. If there is a change/improvement in behavior and you don't necessarily know about it, when loading older workspaces into newer versions, it is imperative to know when to rebuild some parts to get the updated functionality.
+40- Contributor
This would be very useful with the performance enhancements to certain readers in 2017. ex csv, where the only way to take advantage of it is to replace the reader.
+22- Safer
Well, a *form* of this is in the FME 2017.1 beta. That said, it is still not quite where we want to be -- for example, if we retire a format like CSV and replace it with CSV2....we don't do the "upgrade" to CSV2 (yet). And we also aren't tracking or notifying if there are things that have changed. Give us some time though -- we're planning to hit this for FME2018....
+22- Safer
+22- Contributor
@daleatsafe thanks for yours and the teams work on this so far. To be honest I'd settle for exposure of issue at this stage by allowing the reader\\writer version to be turned on and shown, like you can do for transformers. That way someone at least knows that if they compare two readers side by side, they can easily see one is of a higher version than the other and it might be worth considering an upgrade. Actually doing an upgrade is no great shakes if you know it's a possibility. Likewise, when transformer versionning was introduced we only ever knew the current version, not that there was a more recent version available. That was a handy starting point and would be great for readers\\writers to begin with. I do however realise that this is complicated by FeatureReaders and FeatureWriters... Thanks, Dave
Login to the community
No account yet? Create an account
An FME Account is required to contribute
LoginEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.