-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use .equals() to compare schemas #711
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
Have you previously signed CLA? If not, mind sending an email address where Snwoflake can send a CLA document to push PRs on public repos? Thanks
I have not, you can send it on: [email protected] |
Thanks for signing the CLA. This is good to merge. @sfc-gh-japatel @sfc-gh-rcheng |
@sfc-gh-japatel any thoughts on this? I've seen this issue popping up a multiple times where a schema closed in SMT doesn't have the same hash as original schema and this equality check fails even when the schema is structurally identical. Using |
@sfc-gh-mbobowski and team to also help review any implications. |
@cchandurkar Can you provide an update for this issue? A lot of checks are failing. |
If SMT clones the schema of the object for any reason, it does not have the same "hash" as original schema but structurally it's the same. Using
!.equals()
instead of!=
will allow SMTs to properly clone the schemas.