RunState enums serialization differs between json4s and jackson.databind
Closed this issue · 0 comments
dk1844 commented
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
- provide the model with
fasterxml.jackson.databind
annotations so that it can be leveraged when imported (e.g. in Enceladus, case in point.)