We actually have a spout that emits just 1 JSON string per tuple. Wondering what should be down downstream after we have the JSON string
On Sat, Mar 29, 2014 at 12:20 PM, Andrew Neilson <[email protected]> wrote: > my team's project has successfully used Jackson > (https://github.com/FasterXML/jackson) to deserialize a spout of JSON arrays > into tuples, and I can recommend it. Though I'll warn you that it takes a > little bit of work beyond the most basic usage (i.e. mapper.readValue(json, > List.class)) to avoid dealing with type ambiguity. > > > On Sat, Mar 29, 2014 at 12:06 PM, Software Dev <[email protected]> > wrote: >> >> Say we are receiving tuples of JSON from a spout. Should we just keep >> passing around the JSON string and deserialize it in each bolt or Is >> it best to break apart the JSON object into a bunch of fields that can >> be passed around. >> >> I'm thinking in terms of performance the latter may be "better" >> although it will slightly make the rest of the topology more complex. >> >> Also, what is a good JSON library to work with? >> >> Thanks > >
