Skip to content

RunState enums serialization differs between json4s and jackson.databind #83

@dk1844

Description

@dk1844

Problem definition

When Json4s serialization is used on enum within Atum, their toString representation is used (JSON looks like enums were strings), e.g.:

    "runState": "allSucceeded",

On the other hand, when this model is used as-is for serialization with fasterxml.jackson.databind, the following JSON is yielded:

  "runState": {
    "enumClass": "za.co.absa.atum.model.RunState", 
    "value": "allSucceeded"
},

It may be worth finding a way to unify the JSON results.

Solution suggestions

  1. provide the model with fasterxml.jackson.databind annotations so that it can be leveraged when imported (e.g. in Enceladus, case in point.)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions