Skip to main content
Solved

Unexpected behaviour of the ChangeDetector


pkno
Contributor
Forum|alt.badge.img+5
  • Contributor

Hello everyone,

I am trying to use the change detector to compare changes from the current input data compared with previous runs to filter out Features that have not changed in order to save some processing time. 
 

In order to do that I create a hash using the CRCCalculator and save that away. With each new run those hashes are compared agains the previously saved hashes. The ChangeDetector gives me pause though.

For some tables the ChangeDetector identifies changes where there are none. Whats more is, when I rerun the ChangeDetector, second time around the results are as expected without changing anything in the workspace. Maybe anyone has some insight into what could be going on here?

1st time running identifies updated features that arent updated at all

2nd time running without changing anything: different (this time correct) results

 

Best answer by ebygomm

If you’re using the CRCCalculator for change detection that would normally be instead of a changedetector not as well as, e.g.

 

https://support.safe.com/hc/article_attachments/25408169779341

View original
Did this help you find an answer to your question?

2 replies

ebygomm
Influencer
Forum|alt.badge.img+31
  • Influencer
  • Best Answer
  • January 15, 2025

If you’re using the CRCCalculator for change detection that would normally be instead of a changedetector not as well as, e.g.

 

https://support.safe.com/hc/article_attachments/25408169779341


pkno
Contributor
Forum|alt.badge.img+5
  • Author
  • Contributor
  • January 15, 2025

I don’t quite get why it wouldn’t work tbh but that seems to be the correct workflow. Thanks!


Reply


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