Hi Shammon, Unfortunately it’s a data stream job. I’ve been exploring a few options but haven’t found anything I’ve decided on yet. I’m currently looking at seeing if I can leverage some type of partial serialization to bind to the properties that I know the job will use and retain the rest as a JSON blob. I’ve also consider trying to store the fields as a large map of string-object pairs and translating thay into a string prior to writing to the sinks. Still accepting any/all ideas that I come across to see if I can handle this in an efficient, reasonable way. Thanks, Rion On Mar 20, 2023, at 8:40 PM, Shammon FY <zjur...@gmail.com> wrote:
|
- Handling JSON Serialization without Kryo Rion Williams
- Handling JSON Serialization without Kryo Rion Williams
- Re: Handling JSON Serialization without Kryo Shammon FY
- Re: Handling JSON Serialization without Kryo Rion Williams
- Re: Handling JSON Serialization without Kry... Ken Krugler
- Re: Handling JSON Serialization withou... Rion Williams
- Re: Handling JSON Serialization wi... Andrew Otto