Skip to main content
Archived

The ability to automatically remove all attributes from the reader that are not

Related products:FME Form
siennaatsafe
redgeographics
danilo_fme
tcrossman
stalknecht
+8
  • siennaatsafe
    siennaatsafe
  • redgeographics
    redgeographics
  • danilo_fme
    danilo_fme
  • tcrossman
    tcrossman
  • stalknecht
    stalknecht
  • connecter
    connecter
  • jackyd
    jackyd
  • r5
    r5
  • cfvonner
    cfvonner
  • gavinpark
    gavinpark
  • geoportalcartog
    geoportalcartog
  • amitkulz
  • pavelh

stalknecht
Contributor

***Note from Migration:***

Original Title was: The ability to automatically remove all attributes from the reader that are not used inside the workspace


After authoring a workspace I would like to have the ability to automatically remove all attributes from the readers that are not used by transformers and/or writers inside the workspace. Removing these attributes will have a positive effect on performance. It’s sometimes a hassle to do this manually in large workspaces.

This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, 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.

6 replies

fmelizard
Safer
Forum|alt.badge.img+18
  • Safer
  • January 21, 2019

Excellent idea.


redgeographics
Celebrity
Forum|alt.badge.img+49

Yes, but... I would argue that this should be a function of the AttributeRemover rather than the reader. With the long-term maintenance of the workspace in mind I suspect that if this is done on the reader people will forget in the long run that those attributes exist (I know I will...). If a colleague has to maintain the workspace, or it is sent in to Safe or a partner for tech support, this becomes an even bigger issue. If a transformer is used you see that it's happening.


stalknecht
Contributor
Forum|alt.badge.img+19
  • Author
  • Contributor
  • January 21, 2019

Currently it's also possible to not expose attributes on the reader. So the problem you describe is allready there. But I agree Implementing this on AttributeManager or AttributeKeeeper for all downstream attributes will be a nice implementation too. My suggestion will be to implement it both on the reader and the transformers so you can make your own decision.


  • January 29, 2019

Yes please!


  • January 29, 2019

Yes please!


connecter
Forum|alt.badge.img+4
  • October 16, 2021

It will be great if the AttributeRemover have an option to delete all empty, missing, or NULL columns.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings