Skip to content

Handle invalid numeric values in JDBC source - #1588

Merged
Sherif A. Nada (sherifnada) merged 14 commits into
masterfrom
sherif/chickenscratch
Jan 13, 2021
Merged

Sherif A. Nada (sherifnada) merged 14 commits into
masterfrom
sherif/chickenscratch

Conversation

@sherifnada

@sherifnada Sherif A. Nada (sherifnada) commented Jan 8, 2021 •

Copy link
Copy Markdown
Contributor

What

NaN and infinity are not supported in JSON schema, but are allowed values in various Postgres numeric types . So we force them into null at the DB level.

Releasing this now to fix a bug that a user is having. But we'll want to have tests like this for every data type's edge cases. This is coming in a later PR.

@michel-tricot

Copy link
Copy Markdown
Contributor

I am afraid that this is adding transformation logic to the source. What would be another option?

@jrhizor Jared Rhizor (jrhizor) left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's unfortunate that NaN/null/infinity will look the same on the destination, but I can't think of a better way right now.

This behavior should be added to our data types documentation.

@sherifnada
Sherif A. Nada (sherifnada) deleted the sherif/chickenscratch branch January 13, 2021 21:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants