Incorrect difference when comparing varchar key between Oracle and RDS Postgres

[skmanchala]

Giving inaccurate differnce when comparing the varchar key value between a table in Oracle and RDS Postgres.

[skmanchala]

Orgin difference shows correct , destination difference just dumps the whole key list even though they exist

[chandu-chai]

The same issue I found between Postgres and BigQuery. More details are here.

[github-actions]

This issue has been marked as stale because it has been open for 60 days with no activity. If you would like the issue to remain open, please comment on the issue and it will be added to the triage queue. Otherwise, it will be closed in 7 days.

[github-actions]

Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment and it will be reopened for triage.

[skmanchala]

No Worries, i have found a alternate way of finding the differences without the data-diff. The package will be of no use if it cannot follow some basic rules when comparing..

[dlawin]

relates to #550

[dlawin]

No Worries, i have found a alternate way of finding the differences without the data-diff. The package will be of no use if it cannot follow some basic rules when comparing..

Hey @skmanchala can you add some detail?

This is not enough to be actionable on its own:

Giving inaccurate differnce when comparing the varchar key value between a table in Oracle and RDS Postgres.
Orgin difference shows correct , destination difference just dumps the whole key list even though they exist

However this scenario may become apparent in the resolution of #550

[skmanchala]

We have a Varchar primary key in both RDS Postgrest and Oracle which i am using to compare the data, as mentioned previously , the record in source not in target shows up correcly but after that it shows all the records in destination not present in source

[glebmezh]

Hi @skmanchala,

I'm sorry for the delay in following up on this. Thank you for taking the time to raise this issue!

We made a hard decision to sunset the data-diff package and won't provide further development or support.

If that's of interest, over the past few months, we have rewritten the diffing engine in Datafold Cloud and solved many issues that existed in this package's diffing algorithm.

-Gleb