Skip to main content
Question

Why are FeatureJoiner and FeatureMerger joining on UUIDs differently?

  • April 14, 2018
  • 4 replies
  • 25 views
jt
Contributor
Forum|alt.badge.img+3
  • jtContributor
  • Contributor
  • 8 replies

I have two uniqueidentifiers:

4F23402A-BBCD-498E-9136-C0C06F20AB57

4DE5DCD8-5D50-4272-B9DC-6D3997CC2F47

When both are set to UTF-8 encoding and run through a FeatureJoiner on Automatic comparison mode, they do not join - as they shouldn't.

However, when both UUIDs are set to UTF-16LE (which is how they appear in FME if they were read in from SQL Server) and run through a FeatureJoiner on Automatic comparison mode, they DO join. The same behavior occurs when set to Numeric mode. When set to String mode, obviously they do not join.

This behavior appears to be inconsistent with the FeatureMerger. With the FeatureMerger, these two UUIDs never join, regardless of comparison mode and UTF-8/UTF-16LE encoding.

So my questions: Is this the intended behavior of the FeatureJoiner? Why does FeatureJoiner's attempt to convert (UTF-16LE) UUIDs into a number appear to have a different result than when the FeatureMerger attempts to convert the same (UTF-16LE) UUIDs into a number? Perhaps I just don't understand the finer points of character encoding...

The attached workspace tests various combinations.

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.

4 replies

takashi
Celebrity
  • takashiCelebrity
  • 7843 replies
  • April 15, 2018
It seems to be a bug. I would recommend you to report it to Safe support.
Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
fmelizard
Safer
Forum|alt.badge.img+20
  • fmelizardSafer
  • Safer
  • 3719 replies
  • April 15, 2018

Yep, its a bug alright. Already confirmed by development. We'll get it into a 2018.0 update as soon as we can. Sorry about this.

jt
Contributor
Forum|alt.badge.img+3
  • jtContributor
  • Author
  • Contributor
  • 8 replies
  • April 15, 2018

Yep, its a bug alright. Already confirmed by development. We'll get it into a 2018.0 update as soon as we can. Sorry about this.

Sounds good, thank you!

 

 

brianatsafe
Safer
Forum|alt.badge.img+13
  • brianatsafeSafer
  • Safer
  • 92 replies
  • May 11, 2018

Hi everyone! I am happy to report this has been fixed in the latest release of FME (https://www.safe.com/support/support-resources/fme-downloads/). The behavior of the FeatureJoiner is now consistent with the FeatureMerger.

Community Stats

32,086
Posts
121,847
Replies
39,729
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility 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.