Skip to main content
Open

ChangeDetector match all attributes should exclude multi_reader attributes

Related products:Transformers
  • June 11, 2019
  • 4 replies
  • 112 views

jdh
Contributor
Forum|alt.badge.img+40

It would be nice if the ChangeDetector match all attributes could exclude unexposed workspace level attributes like multi_reader_id, multi_reader_full_id, multi_reader_keyword, multi_reader_type.

As it is, I need to either use match selected attributes and select them all (not possible in dynamic scenarios) or expose the multi_ attributes prior to the ChangeDetector so that match all except can be used.

4 replies

ebygomm
Influencer
Forum|alt.badge.img+47
  • Influencer
  • June 12, 2019

I thought i had a similar suggestion for the matcher which also considered unexposed attributes if match all was selected (can't find the idea now) I


jdh
Contributor
Forum|alt.badge.img+40
  • Author
  • Contributor
  • June 12, 2019

I don't like the idea of ignoring all unexposed attributes (for dynamic scenarios), but an additional parameter to "Consider unexposed format attributes: Yes|No" would be very interesting. Replace format with whatever word covers the multi_*, fme_*, csv_skipped_line, etc attributes.

 

 

That way if you don't know/care about format/reader specific attributes, you don't need to deal with them, but if fme_feature_type was important, you can expose it on the reader.

lucky
Contributor
Forum|alt.badge.img+1
  • Contributor
  • June 19, 2019

It is really necessary to exclude the Reader-Attributes!

I don't know any example where the Change-detector will be used with the same reader/table Name.

Using the same table from the same Reader will never Show any changes!


andreaatsafe
Safer
Forum|alt.badge.img+15

Hi all,

We’re hoping to address this idea and want to validate our approach and make sure it’s addressing the needs here.

If the ChangeDetector had a Yes/No parameter to exclude format attributes (similar to the “Include Format Attributes” in the SchemaScanner) from 'Match All', would that solve your problem?

The format attributes would be: multi_reader_*, fme_* and any format prefixed attributes that are determined dynamically from multi_reader_* (eg if it detects csv, then csv_* attributes would be excluded). By going with this approach this would allow for your user attributes that are read as unexposed to still be used to check for changes.