Skip to content
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

JDBC native source produces non-null values for null values at the source #501

Closed
yruslan opened this issue Oct 18, 2024 · 0 comments · Fixed by #502
Closed

JDBC native source produces non-null values for null values at the source #501

yruslan opened this issue Oct 18, 2024 · 0 comments · Fixed by #502
Labels
bug Something isn't working

Comments

@yruslan
Copy link
Collaborator

yruslan commented Oct 18, 2024

Describe the bug

When an input schema has columns that map to Java primitive types (short, int, long), and JDBC Native is on, the resulting data contains default values (0) instead of nulls for nullable columns.

Code and/or configuration snippet that caused the issue

pramen.sources = [
  {
    name = "jdbc_source"
    factory.class = "za.co.absa.pramen.core.source.JdbcSource"

    jdbc = {
       ...
    }
    use.jdbc.native = true
  }
]

Expected behavior

Nullable fields should retain 'null' value when loaded via JDBC Native.

Context

  • Pramen/pramen-py version: 1.9.9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant